Re: [PATCH 2/2] drm/rockchip: vop: add rk3126 vop support

On 2017年11月14日 19:27, Sandy Huang wrote: RK3126 vop register layout is similar with rk3036, so some feature can reuse with rk3036. RK3126 support two overlay plane and one hwc plane, max output resolution is 1080p. it support IOMMU, and its IOMMU same as rk3288's Signed-off-by: Sandy Huang

Re: [PATCH 2/2] drm/rockchip: vop: add rk3126 vop support

On 2017年11月14日 19:27, Sandy Huang wrote: RK3126 vop register layout is similar with rk3036, so some feature can reuse with rk3036. RK3126 support two overlay plane and one hwc plane, max output resolution is 1080p. it support IOMMU, and its IOMMU same as rk3288's Signed-off-by: Sandy Huang

Re: [PATCH libdrm] amdgpu: Disable deadlock test suite for Vega 10

Pushed to master branch of git.freedesktop.org/git/mesa/drm, do I also need to push to our local tree ? Thanks, Andrey On 2017-11-15 04:31 AM, Christian König wrote: Am 14.11.2017 um 15:07 schrieb Andrey Grodzovsky: The suite stalls the CP, until RCA is done the suite is disabled to not

Re: [git pull] drm for v4.15

On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote: > > There is some code touched on sound/soc, but I think the sound tree > should have the same commits from the same base,so this may luck different > if you pulled it as I generated my pull request a couple of days ago. >

Re: [PATCH v2 1/3] dt-bindings: display/ti: Add optional property to set memory bandwidth limit

On Tue, Nov 14, 2017 at 02:47:53PM +0200, Peter Ujfalusi wrote: > max-memory-bandwidth can be used to specify the maximum bandwidth dispc > can use when reading display data from main memory. > > In some SoC (am437x for example) we have memory bandwidth limitation > which causes underflow in the

Re: [PATCH 1/2] dt-bindings: add document for rk3126-vop

On Tue, Nov 14, 2017 at 07:27:34PM +0800, Sandy Huang wrote: > Signed-off-by: Sandy Huang > --- > Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt | 1 + > 1 file changed, 1 insertion(+) Acked-by: Rob Herring

RE: [PATCH 1/2] drm/ttm: fix ttm_mem_evict_first once more

Reviewed-by: Roger He Thanks Roger(Hongbo.He) -Original Message- From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of Christian K?nig Sent: Wednesday, November 15, 2017 8:32 PM To: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org

Re: [GIT PULL] exynos-drm-next

Hi Daniel, 2017년 11월 15일 19:27에 Daniel Stone 이(가) 쓴 글: > Hi Inki, > > On 15 November 2017 at 01:26, Inki Dae wrote: >> 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: >>> On 26 October 2017 at 11:37, Inki Dae wrote: Ps. we are reviewing IPP v2

Re: [PATCH] drm: mali-dp: Disable planes when their CRTC gets disabled.

On Wed, Nov 15, 2017 at 05:25:02PM -0200, Gustavo Padovan wrote: > Hi Liviu, Hi Gustavo, > > 2017-11-01 Liviu Dudau : > > > Make sure only the planes on the active CRTCs get committed and > > that all planes on the disabled CRTCs get turned off. > > > > Reviewed-by: Brian

RE: [PATCH] drm/vgem: Fix vgem_init to get drm device avaliable.

-Original Message- From: Emil Velikov [mailto:emil.l.veli...@gmail.com] Sent: Friday, November 10, 2017 5:11 AM To: Sharma, Deepak Cc: ML dri-devel ; Deucher, Alexander ; Stéphane Marchesin

[Bug 103175] R9285 Unreal tournament perf regression with agd5f 4.15-wip kernels possibly CPU related

https://bugs.freedesktop.org/show_bug.cgi?id=103175 --- Comment #7 from Andy Furniss --- This is OK now with amd-staging-drm-next, I'll close when 4.15s get updated assuming they get whatever fixed it as well. -- You are receiving this mail because: You are the assignee

[Bug 103486] Tonga DC vblank_mode=0 not working as expected fullscreen

https://bugs.freedesktop.org/show_bug.cgi?id=103486 Andy Furniss changed: What|Removed |Added Status|NEW |RESOLVED

-EPROBE_DEFER and failed DSI panel probe

I'm happy to have the DSI panel finally working on VC4 (just waiting on https://lists.freedesktop.org/archives/dri-devel/2017-October/156407.html), but now I've got another problem to solve. It would be great if I could include the DSI panel in our upstream DT, so that it automatically worked

[pull] amdgpu dc drm-next-4.15-dc

Hi Dave, Various fixes for DC for 4.15. It doesn't look like you pulled the smatch fixes for DC that I sent out last week. Those are also on this branch. The following changes since commit f368d3bfde225199eef2216b03e0ba4944a3434a: amd/display: Fix potential null dereference in dce_calcs.c

Re: [PATCH 2/2] dma-buf: try to replace a signaled fence in reservation_object_add_shared_inplace

Quoting Christian König (2017-11-15 18:56:43) > Am 15.11.2017 um 18:43 schrieb Chris Wilson: > > Quoting Christian König (2017-11-15 17:34:07) > >> Am 15.11.2017 um 17:55 schrieb Chris Wilson: > >>> Quoting Chris Wilson (2017-11-14 14:34:05) > Quoting Christian König (2017-11-14 14:24:44) >

[pull] amdgpu drm-next-4.15

Hi Dave, Misc fixes for 4.15. The following changes since commit a9386bb051931778436db3dd6e3a163f7db92b56: Merge tag 'drm-misc-next-fixes-2017-11-08' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2017-11-09 11:59:30 +1000) are available in the git repository at:

Re: [PATCH] drm: mali-dp: Disable planes when their CRTC gets disabled.

Hi Liviu, 2017-11-01 Liviu Dudau : > Make sure only the planes on the active CRTCs get committed and > that all planes on the disabled CRTCs get turned off. > > Reviewed-by: Brian Starkey > Signed-off-by: Liviu Dudau > --- >

Re: [PATCH] drm: mali-dp: Separate static internal data into a read-only structure.

Hi Liviu, 2017-11-01 Liviu Dudau : > The malidp_hw_device structure that the driver uses to handle the > differences between versions of the IP contains both non-changeable > data and fields that get updated at probe time. Previously we were > copying the read-only part into

Re: [PATCH 2/2] dma-buf: try to replace a signaled fence in reservation_object_add_shared_inplace

Am 15.11.2017 um 18:43 schrieb Chris Wilson: Quoting Christian König (2017-11-15 17:34:07) Am 15.11.2017 um 17:55 schrieb Chris Wilson: Quoting Chris Wilson (2017-11-14 14:34:05) Quoting Christian König (2017-11-14 14:24:44) Am 06.11.2017 um 17:22 schrieb Chris Wilson: Quoting Christian

[PATCH v2] drm/atomic: Use DRM_DEBUG_KMS instead of DRM_DEBUG_ATOMIC in error paths

From: Ville Syrjälä DRM_DEBUG_ATOMIC generates a lot of noise that no one normally cares about. However error paths everyone cares about, so hiding thea error debugs under DRM_DEBUG_ATOMIC is a bad idea. Let's use DRM_DEBUG_KMS for those instead. v2: Rebase and

[Bug 103736] Sudden system freezes, GPU fault detected

https://bugs.freedesktop.org/show_bug.cgi?id=103736 Shiverly changed: What|Removed |Added Summary|Sudden system freezes, |Sudden system freezes,

[Bug 103736] Sudden system freezes, dmesg errors

https://bugs.freedesktop.org/show_bug.cgi?id=103736 --- Comment #4 from Shiverly --- I got some logs. Maybe they are related (found them in journalctl) Nov 15 20:09:06 tibu-pc kernel: gmc_v8_0_process_interrupt: 626 callbacks suppressed Nov 15 20:08:20 tibu-pc kernel:

Re: [PATCH 04/10] drm/uapi: Deprecate DRM_MODE_FLAG_BCAST

On 14-11-2017 18:32, Ville Syrjala wrote: > From: Ville Syrjälä > > Reject any mode with DRM_MODE_FLAG_BCAST. We have no code that even > checks for this flag hence it can't possibly do any good. > > I think this maybe originated from fbdev where it was supposed

[Bug 103769] Unity based games do not start

https://bugs.freedesktop.org/show_bug.cgi?id=103769 --- Comment #2 from bartos.p...@gmail.com --- Created attachment 135501 --> https://bugs.freedesktop.org/attachment.cgi?id=135501=edit Crash of Rochard -- You are receiving this mail because: You are the assignee for the

[Bug 103769] Unity based games do not start

https://bugs.freedesktop.org/show_bug.cgi?id=103769 --- Comment #1 from bartos.p...@gmail.com --- Created attachment 135500 --> https://bugs.freedesktop.org/attachment.cgi?id=135500=edit Crash of Oddworld -- You are receiving this mail because: You are the assignee for the

[Bug 103769] Unity based games do not start

https://bugs.freedesktop.org/show_bug.cgi?id=103769 Bug ID: 103769 Summary: Unity based games do not start Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major

Re: [PATCH 03/10] drm/uapi: Deprecate DRM_MODE_FLAG_PIXMUX

On 14-11-2017 18:32, Ville Syrjala wrote: > From: Ville Syrjälä > > Reject any mode with DRM_MODE_FLAG_PIXMUX. We have no code that even > checks for this flag hence it can't possibly do any good. > > Looks like this flag had something to do the the

Re: [PATCH v2 08/10] drm/uapi: Deprecate nonsense kms mode types

On 15-11-2017 15:45, Ville Syrjala wrote: > From: Ville Syrjälä > > BUILTIN, CRTC_C, CLOCK_C, and DEFULT mode types are unused. Let's > refuse to generate them or accept them from userspace either. A > cursory check didn't reveal any userspace code that would

Re: [PATCH v2 02/10] drm/uapi: Validate the mode flags/type

Hi Ville, On 15-11-2017 15:49, Ville Syrjala wrote: > > +#define DRM_MODE_FLAG_ALL (DRM_MODE_FLAG_PHSYNC | \ > + DRM_MODE_FLAG_NHSYNC | \ > + DRM_MODE_FLAG_PVSYNC | \ > +

Re: etnaviv: PHYS_OFFSET usage

Am Mittwoch, den 15.11.2017, 17:36 + schrieb Alexey Brodkin: > Hi Lucas, > > On Wed, 2017-11-15 at 17:44 +0100, Lucas Stach wrote: > > Hi Alexey, > > > > Am Mittwoch, den 15.11.2017, 16:24 + schrieb Alexey Brodkin: > > > > > > Hi Lucas, > > > > > > As we discussed on ELCE last month in

[Bug 103736] Sudden system freezes, dmesg errors

https://bugs.freedesktop.org/show_bug.cgi?id=103736 --- Comment #3 from Shiverly --- (In reply to Andres Rodriguez from comment #2) > > FWIW, Andres Rodriguez reported similar symptoms with a Ryzen system on IRC, > > and raising voltages / disabling Cool'n'Quiet / disabling

Re: [PATCH 2/2] dma-buf: try to replace a signaled fence in reservation_object_add_shared_inplace

Quoting Christian König (2017-11-15 17:34:07) > Am 15.11.2017 um 17:55 schrieb Chris Wilson: > > Quoting Chris Wilson (2017-11-14 14:34:05) > >> Quoting Christian König (2017-11-14 14:24:44) > >>> Am 06.11.2017 um 17:22 schrieb Chris Wilson: > Quoting Christian König (2017-10-30 14:59:04) >

Re: [PATCH v2 02/10] drm/uapi: Validate the mode flags/type

On Wed, Nov 15, 2017 at 10:49 AM, Ville Syrjala wrote: > From: Ville Syrjälä > > Currently userspace is allowed to feed in any king of garbage in the > high bits of the mode flags/type, as are drivers when probing modes. > Reject any

Re: [PATCH 2/2] dma-buf: try to replace a signaled fence in reservation_object_add_shared_inplace

Am 15.11.2017 um 17:55 schrieb Chris Wilson: Quoting Chris Wilson (2017-11-14 14:34:05) Quoting Christian König (2017-11-14 14:24:44) Am 06.11.2017 um 17:22 schrieb Chris Wilson: Quoting Christian König (2017-10-30 14:59:04) @@ -126,17 +127,28 @@ reservation_object_add_shared_inplace(struct

A virtual DRM/KMS device

Hi all, I'm working on GPU virtualization on the Renesas rcar-du embedded platform. My setup consists of - a primary Linux instance which controls all DUs (display units) and the GPU (3D engine) and - secondary Linux instances which have virtual access to the GPU and to selected DUs. I

Re: [PATCH 2/2] dma-buf: try to replace a signaled fence in reservation_object_add_shared_inplace

Quoting Chris Wilson (2017-11-14 14:34:05) > Quoting Christian König (2017-11-14 14:24:44) > > Am 06.11.2017 um 17:22 schrieb Chris Wilson: > > > Quoting Christian König (2017-10-30 14:59:04) > > >> @@ -126,17 +127,28 @@ reservation_object_add_shared_inplace(struct > > >> reservation_object *obj,

Re: etnaviv: PHYS_OFFSET usage

Hi Alexey, Am Mittwoch, den 15.11.2017, 16:24 + schrieb Alexey Brodkin: > Hi Lucas, > > As we discussed on ELCE last month in Prague we have Vivante GPU > built-in our new ARC HSDK development board. > > And even though [thanks to your suggestions] I got Etnaviv driver > working perfectly

[PATCH v2 02/10] drm/uapi: Validate the mode flags/type

From: Ville Syrjälä Currently userspace is allowed to feed in any king of garbage in the high bits of the mode flags/type, as are drivers when probing modes. Reject any mode with bogus flags/type. Hopefully this won't break any current userspace... v2: Split the

[PATCH] drm/amd/display: remove unnecessary cast and use kcalloc instead of kzalloc

From: Colin Ian King Use kcalloc instead of kzalloc and the cast on the return from kzalloc is unnecessary and can be removed. Signed-off-by: Colin Ian King --- drivers/gpu/drm/amd/display/dc/basics/logger.c | 5 ++--- 1 file changed, 2

Re: [PATCH] drm/edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks

On Tue, Nov 14, 2017 at 06:38:11PM -0500, neil k wrote: > I tested the patch from Ville Syrjälä's email and it works fine on top of > 4.14 for me. Thanks for confirming. Patch pushed to drm-misc-fixes. > > Thanks, > Neil > > On Thu, Nov 9, 2017 at 1:16 PM, Eric Anholt wrote:

Re: [PATCH 2/2] drm/ttm: completely rework ttm_bo_delayed_delete

On 15/11/17 01:31 PM, Christian König wrote: > There is no guarantee that the next entry on the ddelete list stays on > the list when we drop the locks. > > Completely rework this mess by moving processed entries on a temporary > list. > > Signed-off-by: Christian König

Re: [PATCH v2 12/22] drm/sti: Use drm_fb_cma_fbdev_init/fini()

2017-11-15 15:19 GMT+01:00 Noralf Trønnes : > Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on > the fact that drm_device holds a pointer to the drm_fb_helper structure. > This means that the driver doesn't have to keep track of that. > Also use the

[PATCH] drm/tegra: sor: Reimplement pad clock

From: Thierry Reding The current implementation of the pad clock isn't quite correct. This has the side-effect of being incompatible with the implementation for Tegra186 (provided by the BPMP) and therefore would require a massive change to the driver to cope with the

Re: [PATCH v2] drm: gem_cma_helper.c: Allow importing of contiguous scatterlists with nents > 1

On Wed, Nov 15, 2017 at 03:24:41PM +0100, Noralf Trønnes wrote: > > Den 15.11.2017 14.04, skrev Liviu Dudau: > > Hi, > > > > On Sat, Nov 11, 2017 at 02:47:35PM +0200, Laurent Pinchart wrote: > > > Hi Liviu, > > > > > > Thank you for the patch. > > > > > > On Friday, 10 November 2017 15:33:10

[PATCH v2 16/22] drm/tve200: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Linus Walleij

Re: [PATCH 1/3] backlight: as3711_bl: fix device-tree node lookup

On Wed, 15 Nov 2017, Johan Hovold wrote: > On Tue, Nov 14, 2017 at 07:48:09PM +, Daniel Thompson wrote: > > On 14/11/17 18:05, Johan Hovold wrote: > > > On Mon, Nov 13, 2017 at 02:16:09PM +, Daniel Thompson wrote: > > >> On 13/11/17 10:20, Johan Hovold wrote: > > >>> Fix child-node lookup

[PATCH v2 22/22] drm/cma-helper: Remove drm_fbdev_cma* functions

Remove the unused struct drm_fbdev_cma functions. Cc: Laurent Pinchart Signed-off-by: Noralf Trønnes Acked-by: Daniel Vetter --- drivers/gpu/drm/drm_fb_cma_helper.c | 158

[PATCH v2 18/22] drm/zte: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Shawn Guo

[PATCH v2 17/22] drm/vc4: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Eric Anholt

[PATCH v2 19/22] drm/arm/mali: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Liviu Dudau Cc:

[PATCH v2 11/22] drm/rcar-du: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Laurent Pinchart

[PATCH v2 10/22] drm/pl111: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Eric Anholt

[PATCH v2 21/22] drm/tinydrm: Use drm_fb_cma_fbdev_init_with_funcs/fini()

Use drm_fb_cma_fbdev_init_with_funcs() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Remove todo entry. Cc: David

[PATCH v2 20/22] drm/fsl-dcu: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Stefan Agner Cc:

Re: [PATCH v2] drm: gem_cma_helper.c: Allow importing of contiguous scatterlists with nents > 1

Den 15.11.2017 14.04, skrev Liviu Dudau: Hi, On Sat, Nov 11, 2017 at 02:47:35PM +0200, Laurent Pinchart wrote: Hi Liviu, Thank you for the patch. On Friday, 10 November 2017 15:33:10 EET Liviu Dudau wrote: drm_gem_cma_prime_import_sg_table() will fail if the number of entries in the

[PATCH v2 15/22] drm/tilcdc: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Jyri Sarha Cc: Tomi

[PATCH v2 14/22] drm/sun4i: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Maxime Ripard

[PATCH v2 13/22] drm/stm: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Remove duplicate ldev assignment. Cc:

[PATCH v2 05/22] drm/atmel-hlcdc: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Boris Brezillon

[PATCH v2 08/22] drm/meson: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Neil Armstrong

[PATCH v2 01/22] drm/gem-fb-helper: drm_gem_fbdev_fb_create() make funcs optional

Make the drm_framebuffer_funcs argument optional for drivers that don't need to set the dirty callback. Signed-off-by: Noralf Trønnes Reviewed-by: Daniel Vetter --- drivers/gpu/drm/drm_gem_framebuffer_helper.c | 6 +- 1 file changed, 5

[PATCH v2 12/22] drm/sti: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Benjamin Gaignard

[PATCH v2 09/22] drm/mxsfb: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Marek Vasut

[PATCH v2 07/22] drm/imx: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Philipp Zabel

[PATCH v2 02/22] drm/cma-helper: Add drm_fb_cma_fbdev_init/fini()

Add functions drm_fb_cma_fbdev_init(), drm_fb_cma_fbdev_fini() and drm_fb_cma_fbdev_init_with_funcs(). These functions relies on the fact that the drm_fb_helper struct is stored in dev->drm_fb_helper_private so drivers don't need to store it. Cc: Laurent Pinchart

[PATCH v2 06/22] drm/hisilicon/kirin: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Xinliang Liu

[PATCH v2 04/22] drm/arm/hdlcd: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Cc: Liviu Dudau Cc:

[PATCH v2 00/22] drm/cma-helper: Remove drm_fbdev_cma* functions

This patchset adds drm_fb_cma_fbdev_init/fini() functions that replaces drm_fbdev_cma_init/fini(). The reason for doing so is to get rid of struct drm_fbdev_cma and it's wrapper functions. The final piece will happen when tinydrm moves away from the cma helper and we can remove the struct. Note:

[PATCH v2 03/22] drm/arc: Use drm_fb_cma_fbdev_init/fini()

Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on the fact that drm_device holds a pointer to the drm_fb_helper structure. This means that the driver doesn't have to keep track of that. Also use the drm_fb_helper functions directly. Remove unused function prototype

Re: [PATCH] dma-buf/fence: Fix lock inversion within dma-fence-array

Quoting Chris Wilson (2017-11-14 16:27:19) > Ages ago Rob Clark noted, > > "Currently with fence-array, we have a potential deadlock situation. If > we fence_add_callback() on an array-fence, the array-fence's lock is > acquired first, and in it's ->enable_signaling() callback, it will install >

Re: [PATCH v2] drm: gem_cma_helper.c: Allow importing of contiguous scatterlists with nents > 1

Hi, On Sat, Nov 11, 2017 at 02:47:35PM +0200, Laurent Pinchart wrote: > Hi Liviu, > > Thank you for the patch. > > On Friday, 10 November 2017 15:33:10 EET Liviu Dudau wrote: > > drm_gem_cma_prime_import_sg_table() will fail if the number of entries > > in the sg_table > 1. However, you can

Re: [PATCH] [RFT] drm: adv7511/33: fix adv7511_cec_init() failure handling

On 15/11/17 13:37, Arnd Bergmann wrote: > An otherwise correct cleanup patch from Dan Carpenter turned a broken > failure handling from a feature patch by Hans Verkuil into a kernel > Oops, so bisection points to commit 7af35b0addbc ("drm/kirin: Checking > for IS_ERR() instead of NULL") rather

[PATCH] [RFT] drm: adv7511/33: fix adv7511_cec_init() failure handling

An otherwise correct cleanup patch from Dan Carpenter turned a broken failure handling from a feature patch by Hans Verkuil into a kernel Oops, so bisection points to commit 7af35b0addbc ("drm/kirin: Checking for IS_ERR() instead of NULL") rather than 3b1b975003e4 ("drm: adv7511/33: add HDMI CEC

[PATCH 2/2] drm/ttm: completely rework ttm_bo_delayed_delete

There is no guarantee that the next entry on the ddelete list stays on the list when we drop the locks. Completely rework this mess by moving processed entries on a temporary list. Signed-off-by: Christian König --- drivers/gpu/drm/ttm/ttm_bo.c | 77

[PATCH 1/2] drm/ttm: fix ttm_mem_evict_first once more

The code path isn't hit at the moment, but we need to take the lock to add the BO back to the LRU. Signed-off-by: Christian König --- drivers/gpu/drm/ttm/ttm_bo.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/ttm/ttm_bo.c

Re: [PATCH 1/2] drm/atomic-helper: always track connector commits, too

Op 10-11-17 om 11:53 schreef Daniel Vetter: > It's useful for syncing async connector work like link retraining. > > v2: Make it work (Manasi) > > Cc: Manasi Navare > Cc: Maarten Lankhorst > Cc: Ville Syrjälä

[Bug 103443] [CI] igt@ - success - WARN - no modes for connector 76

https://bugs.freedesktop.org/show_bug.cgi?id=103443 Marta Löfstedt changed: What|Removed |Added Summary|[CI]|[CI] igt@ -

[Bug 103443] [CI] igt@kms_setmode@[clone-exclusive-crtc | invalid-clone-exclusive-crtc] - warn - no modes for connector 76

https://bugs.freedesktop.org/show_bug.cgi?id=103443 Marta Löfstedt changed: What|Removed |Added Depends on||103369

Re: [GIT PULL] exynos-drm-next

Hi Inki, On 15 November 2017 at 01:26, Inki Dae wrote: > 2017년 11월 14일 13:22에 Dave Airlie 이(가) 쓴 글: >> On 26 October 2017 at 11:37, Inki Dae wrote: >>>Ps. we are reviewing IPP v2 driver[1] which controls post processor >>> devices >>>such

Re: 4.1 EOL

On Tue, 14 Nov 2017, Tuncer Ayaz wrote: > On 11/14/17, Jani Nikula wrote: >> >> Tuncer, where's your bug report? Can't find one. Please file your >> bug at the fdo bugzilla. > > I'm sorry if this wasn't clear. > > I didn't file a bug report

Re: [PATCH] drm/bridge: Fix lvds-encoder since the panel_bridge rework.

Hi, On Tue, 14 Nov 2017 11:16:47 -0800 Eric Anholt wrote: > The panel_bridge bridge attaches to the panel's OF node, not the > lvds-encoder's node. Put in a little no-op bridge of our own so that > our consumers can still find a bridge where they expect. > > This also fixes an unintended

Re: [PATCH libdrm] amdgpu: Disable deadlock test suite for Vega 10

Am 14.11.2017 um 15:07 schrieb Andrey Grodzovsky: The suite stalls the CP, until RCA is done the suite is disabled to not disrupt regression testing. Signed-off-by: Andrey Grodzovsky Reviewed-by: Christian König Since you now have commit

[Bug 103751] Very slow display on Legacy mode, but it's normal on UEFI mode

https://bugs.freedesktop.org/show_bug.cgi?id=103751 Bug ID: 103751 Summary: Very slow display on Legacy mode, but it's normal on UEFI mode Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: All

Re: [PATCH] drm/edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks

I tested the patch from Ville Syrjälä's email and it works fine on top of 4.14 for me. Thanks, Neil On Thu, Nov 9, 2017 at 1:16 PM, Eric Anholt wrote: > Daniel Vetter writes: > > > On Wed, Nov 08, 2017 at 02:21:08PM -0800, Eric Anholt wrote: > >> Ville

[PATCH 7/8] clk: mediatek: mt8173-mm: switch to mfd device

As the new mfd device is in place, switch probing for the MMSYS to support invocation from the mfd device. Signed-off-by: Matthias Brugger --- drivers/clk/mediatek/clk-mt8173.c | 21 +++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git

Re: [PATCH 1/3] backlight: as3711_bl: fix device-tree node lookup

On Mon, Nov 13, 2017 at 02:16:09PM +, Daniel Thompson wrote: > On 13/11/17 10:20, Johan Hovold wrote: > > Fix child-node lookup during probe, which ended up searching the whole > > device tree depth-first starting at the parent rather than just matching > > on its children. > > > > To make

[PATCH 4/8] clk: mediatek: mt2701-mm: switch to mfd device

As the new mfd device is in place, switch probing for the MMSYS to support invocation from the mfd device. Signed-off-by: Matthias Brugger --- drivers/clk/mediatek/clk-mt2701-mm.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git

[PATCH 1/1] drm/rockchip: dw-mipi-dsi: fix possible un-balanced runtime PM enable

In the case of the the binds gets defered we would end up with a un-balanced runtime PM enable call. Fix this by simply moving the pm_runtime_enable call to the end of the bind function when all paths have succeeded. Signed-off-by: Mirza Krak ---

[PATCH 2/2] drm/i915: Call uncore_suspend before platform suspend handlers

Quoting Ville: "the forcewake timer might still be active until the uncore suspend, and having active forcewakes while we've already told the GT wake stuff to stop acting normally doesn't seem quite right to me." Reported-by: Ville Syrjälä Suggested-by: Imre Deak

[PATCH 0/2] drm/i915: Misc. PMIC bus access notifier fixes

Hi, This is a resend of patch 2 and 3 of my 3 patch "drm/i915: Misc. PMIC bus access notifier fixes" series for some reason I'm not having any luck with the CI with this series (I believe I'm just hitting glitches) so I've splitted it up patch 1 passed CI, now lets see if these 2 also pass.

[PATCH 6/8] drm/mediatek: Add mfd support for mt8173

Use the MFD device for SoC mt8173. Probing via devicetree is no longer needed for any SoC, so delete it. Signed-off-by: Matthias Brugger --- drivers/gpu/drm/mediatek/mtk_drm_drv.c | 28 +++- 1 file changed, 7 insertions(+), 21 deletions(-) diff --git

[PATCH 8/8] MAINTAINERS: update Mediatek Soc entry

Mediatek SoCs include several soc specific drivers as well as a mfd device. Add these to the maintainers file. Signed-off-by: Matthias Brugger --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 2811a211632c..586797908865

[PATCH 2/8] mfd: mtk-mmsys: Add mmsys driver

The MMSYS subsystem includes clocks and drm components. This patch adds a MFD device to probe both drivers from the same device tree compatible. Signed-off-by: Matthias Brugger --- drivers/mfd/Kconfig | 9 + drivers/mfd/Makefile | 2 ++

[PATCH 5/8] mfd: mtk-mmsys: Add mt8173 nodes

Add devices for the mt8173 SoC. Signed-off-by: Matthias Brugger --- drivers/mfd/mtk-mmsys.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/drivers/mfd/mtk-mmsys.c b/drivers/mfd/mtk-mmsys.c index 102b491aa28f..45973dfc6010 100644 ---

[PATCH 1/2] drm/i915: Re-register PMIC bus access notifier on runtime resume

intel_uncore_suspend() unregisters the uncore code's PMIC bus access notifier and gets called on both normal and runtime suspend. intel_uncore_resume_early() re-registers the notifier, but only on normal resume. Add a new intel_uncore_runtime_resume() function which only re-registers the notifier

[PATCH 0/8] arm/arm64: mediatek: Fix mmsys device probing

MMSYS in Mediatek SoCs has some registers to control clock gates (which is used in the clk driver) and some registers to set the routing and enable the differnet blocks of the display subsystem. Up to now both drivers, clock and drm are probed with the same device tree compatible. But only the

Re: 4.1 EOL

On 11/14/17, Jani Nikula wrote: > > Tuncer, where's your bug report? Can't find one. Please file your > bug at the fdo bugzilla. I'm sorry if this wasn't clear. I didn't file a bug report since others have already done so, reporting the same symptoms. I did sign up

[PATCH 1/8] drm/mediatek: Use regmap for register access

The mmsys memory space is shared between the drm and the clk driver. Use regmap to access it. Signed-off-by: Matthias Brugger --- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 4 ++-- drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 30 +-

[PATCH 3/8] drm/mediatek: mt2701: switch to mfd probing.

With the mtk-mmsys MFD device in place, we switch the probing for mt2701 from device-tree to mfd. Signed-off-by: Matthias Brugger --- drivers/gpu/drm/mediatek/mtk_drm_drv.c | 32 +--- 1 file changed, 25 insertions(+), 7 deletions(-) diff --git

Re: [PATCH 2/3] drm/syncobj: Fix kerneldocs

Am 14.11.2017 um 20:10 schrieb Ville Syrjala: From: Ville Syrjälä Document the drm_syncobj_get_handle() function parameters. Cc: Marek Olšák Cc: Dave Airlie Cc: Alex Deucher Cc: Daniel Vetter

  1   2   >