https://bugzilla.kernel.org/show_bug.cgi?id=206895
--- Comment #5 from stefansp...@gmail.com ---
That depends on whether the changes to the DMA mechanics were meant to be
compatible with the old implementation, but I can't answer that as I am no AMD
developer.
--
You are receiving this mail beca
Mediatek HDMI phy driver is moved from drivers/gpu/drm/mediatek to
drivers/phy/mediatek, so add the new folder to the Mediatek DRM drivers'
information.
Signed-off-by: Chun-Kuang Hu
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 38fe2f3f7b6f..
mtk_hdmi_phy is currently placed inside mediatek drm driver, but it's
more suitable to place a phy driver into phy driver folder, so move
mtk_hdmi_phy driver into phy driver folder.
CK Hu (3):
drm/mediatek: Move tz_disabled from mtk_hdmi_phy to mtk_hdmi driver
drm/mediatek: Separate mtk_hdmi_p
From: CK Hu
mtk_hdmi_phy is a part of mtk_hdmi module, but phy driver should be an
independent module rather than be part of drm module, so separate the phy
driver to an independent module.
Signed-off-by: CK Hu
Signed-off-by: Chun-Kuang Hu
---
drivers/gpu/drm/mediatek/Kconfig| 9
From: CK Hu
mtk_hdmi_phy is currently placed inside mediatek drm driver, but it's
more suitable to place a phy driver into phy driver folder, so move
mtk_hdmi_phy driver into phy driver folder.
Signed-off-by: CK Hu
Signed-off-by: Chun-Kuang Hu
---
drivers/gpu/drm/mediatek/Kconfig
From: CK Hu
tz_disabled is used to control mtk_hdmi output signal, but this variable
is stored in mtk_hdmi_phy and mtk_hdmi_phy does not use it. So move
tz_disabled to mtk_hdmi where it's used.
Signed-off-by: CK Hu
Signed-off-by: Chun-Kuang Hu
---
drivers/gpu/drm/mediatek/mtk_hdmi.c
On Fri, 17 Jan 2020, Lyude Paul wrote:
> This reverts commit 64e62bdf04ab8529f45ed0a85122c703035dec3a.
>
> This commit ends up causing some lockdep splats due to trying to grab the
> payload lock while holding the mgr's lock:
>
> [ 54.010099]
> [ 54.011765] ==
Hi Dave,
A bit smaller this time around.. there are still a couple uabi
additions for vulkan waiting in the wings, but I punted on them this
cycle due to running low on time. (They should be easy enough to
rebase, and if it is a problem for anyone I can push a next+uabi
branch so that tu work can
https://bugzilla.kernel.org/show_bug.cgi?id=206895
--- Comment #6 from bigbeesh...@gmail.com ---
Looks like its more to do with switching from amd-iommmu to dma-iommu (see my
bisect below)
git bisect start
# good: [e87eb585d31fadb5e9e549a1de4b2da60a79bfc9] Merge branch 'pci/misc'
git bisect good
https://bugzilla.kernel.org/show_bug.cgi?id=206895
--- Comment #7 from bigbeesh...@gmail.com ---
Seems some other issues are showing against this commit
https://bugzilla.kernel.org/show_bug.cgi?id=206461
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
On Sat, 21 Mar 2020 at 08:57, Roland Scheidegger (VMware)
wrote:
>
> Dave, Daniel,
>
> vmwgfx pull for for 5.7. Needed for GL4 functionality.
> Sync up device headers, add support for new commands, code
> refactoring around surface definition.
Two things,
1.for some reason patchwork didn't proce
https://bugzilla.kernel.org/show_bug.cgi?id=206895
--- Comment #8 from bigbeesh...@gmail.com ---
After some further validation
5.6-rc6 also has this bug
Reverting be62dbf554c5b50718a54a359372c148cd9975c7 fixes the issue but overall
it seems that amdgpu is not using the new implementation of dma_
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
between commit:
eb916a5a93a6 ("drm/amd/display: Fix pageflip event race condition for DCN.")
from Linus' tree and commit:
7f2be468a855 ("drm/amdgpu: Stop using the DRIVE
CONFIG_AS_MOVNTDQA was introduced by commit 0b1de5d58e19 ("drm/i915:
Use SSE4.1 movntdqa to accelerate reads from WC memory").
We raise the minimal supported binutils version from time to time.
The last bump was commit 1fb12b35e5ff ("kbuild: Raise the minimum
required binutils version to 2.21").
https://bugzilla.kernel.org/show_bug.cgi?id=206575
--- Comment #17 from Alex Deucher (alexdeuc...@gmail.com) ---
If you could verify that 5.6 works for you, you could bisect to see what commit
fixed it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
Not an enormous fan of what you had to do in atomic_set_planes, but
OTOH I don't see a much better way to do it either.
Reviewed-by: Ilia Mirkin
On Tue, Mar 17, 2020 at 8:11 AM Rohit Visavalia
wrote:
>
> Current implementation shows error as "failed to set gamma: Function
> no implemented" if p
16 matches
Mail list logo
