[Intel-gfx] [PATCH 12/26] drm/atomic-helper: Massage swap_state signature somewhat

On Tue, May 31, 2016 at 10:43:56AM +0200, Maarten Lankhorst wrote: > Op 30-05-16 om 17:09 schreef Daniel Vetter: > > On Mon, May 30, 2016 at 03:08:39PM +0200, Maarten Lankhorst wrote: > >> Op 29-05-16 om 20:35 schreef Daniel Vetter: > >>> - dev is redundant, we have state->atomic > >>> - add stall

[Intel-gfx] [PATCH v5] vga_switcheroo: Add helper for deferred probing

On Mon, May 23, 2016 at 09:23:14AM +0200, Daniel Vetter wrote: > On Sat, May 21, 2016 at 03:59:16PM +0100, Lukas Wunner wrote: [snip] > > /** > > + * vga_switcheroo_client_probe_defer() - whether to defer probing a given > > client > > + * @pdev: client pci device > > + * > > + * Determine

[PATCH 0/5] virtio-gpu: atomic fixes

Hi, Here is my current collection of virtio-gpu patches. First is included here for completeness, it's already in drm-misc. Seconds adds a driver-specific atomic_commit function to avoid crtcs being disabled temporarly. Last three patches switch the cursor handling over to atomic interfaces.

[PATCH 1/5] virtio-gpu: fix output lookup

Needed for multihead setups where we can have disabled outputs and therefore plane->crtc can be NULL. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_plane.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c

[PATCH 2/5] virtio-gpu: add atomic_commit function

Do modesets first, then call drm_atomic_helper_commit_planes with active_only = true. That way the outputs doesn't get disabled temporarly on atomic commits. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_display.c | 22 +-

[PATCH 3/5] virtio-gpu: switch to atomic cursor interfaces

Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_display.c | 102 -- drivers/gpu/drm/virtio/virtgpu_drv.h | 1 + drivers/gpu/drm/virtio/virtgpu_plane.c | 105 --- 3 files changed, 109 insertions(+), 99 deletions(-)

[PATCH 5/5] virtio-gpu: pick up hotspot from framebuffer

Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_plane.c | 20 +--- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c b/drivers/gpu/drm/virtio/virtgpu_plane.c index 4780354..b7778a7 100644 ---

[PATCH 4/5] add cursor hotspot to drm_framebuffer

Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/drm_crtc.c | 2 ++ include/drm/drm_crtc.h | 2 ++ 2 files changed, 4 insertions(+) diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c index d2a6d95..ce5a280 100644 --- a/drivers/gpu/drm/drm_crtc.c +++

[PATCH 3/4] drm: make drm_atomic_set_mode_prop_for_crtc() more reliable

On Tue, May 31, 2016 at 12:17:22PM +0300, Tomi Valkeinen wrote: > drm_atomic_set_mode_prop_for_crtc() has a few issues: > > - it doesn't clear the state->mode, so old data may be left there when a > new mode is set. > - if an error happens, state->mode is left in a partially updated state. > >

[PATCH 4/4] drm: fix fb refcount issue with atomic modesetting

On Tue, May 31, 2016 at 12:17:23PM +0300, Tomi Valkeinen wrote: > After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop > handling framebuffer special") extra fb refs are left around when doing > atomic modesetting. > > The problem is that the new drm_property_change_valid_get()

[PATCH 4/5] add cursor hotspot to drm_framebuffer

On Tue, May 31, 2016 at 12:53:12PM +0200, Gerd Hoffmann wrote: > Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter And feel free to include in a virtio pull to Dave with my ack. -Daniel > --- > drivers/gpu/drm/drm_crtc.c | 2 ++ > include/drm/drm_crtc.h | 2 ++ > 2 files changed, 4

[PATCH 4/4] drm: fix fb refcount issue with atomic modesetting

On Tue, May 31, 2016 at 12:56:23PM +0200, Daniel Vetter wrote: > On Tue, May 31, 2016 at 12:17:23PM +0300, Tomi Valkeinen wrote: > > After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop > > handling framebuffer special") extra fb refs are left around when doing > > atomic

[PATCH 16/26] drm/hdlcd: Use helper support for nonblocking commits

On Sun, May 29, 2016 at 08:35:13PM +0200, Daniel Vetter wrote: > Again, just doing them as blocking commits isn't cool. > > From a cursory check hdlcd does seem to at least try to handle > drm_pending_vblank_event, so hopefully this works. > > Cc: Liviu Dudau > Signed-off-by: Daniel Vetter

[PATCH] drm: hdlcd: Replace the mode config's atomic_commit with the proper implementation.

The HDLCD atomic_commit code was mis-using the drm_atomic_helper_commit() function to implement the non-blocking code. Replace that with the correct implementation that does the async queue-ing of commits. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/hdlcd_crtc.c | 64

[Bug 96271] TF2: GPU lockup on HD 7950

attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/5d3fbd39/attachment-0001.html>

[PATCH v2 09/10] drm/imx: atomic phase 3 step 4: Use generic atomic page flip

On Tue, May 31, 2016 at 05:24:30PM +0800, Liu Ying wrote: > To support generic atomic page flip, this patch customizes ->atomic_commit > for nonblock commits. > > Signed-off-by: Liu Ying > --- > v1->v2: > * s/async/nonblock/ on this patch to address Daniel Vetter's comment. > * Wait for pending

[PATCH 16/26] drm/hdlcd: Use helper support for nonblocking commits

On Tue, May 31, 2016 at 12:02:23PM +0100, Liviu Dudau wrote: > On Sun, May 29, 2016 at 08:35:13PM +0200, Daniel Vetter wrote: > > Again, just doing them as blocking commits isn't cool. > > > > From a cursory check hdlcd does seem to at least try to handle > > drm_pending_vblank_event, so

[PATCH v6 2/2] vga_switcheroo: Support deferred probing of audio clients

On Tue, May 31, 2016 at 11:13:27AM +0200, Lukas Wunner wrote: > Daniel Vetter pointed out that vga_switcheroo_client_probe_defer() could > be needed by audio clients as well. To avoid mistakes when someone adds > conditions for these in the future, constrain the single existing > condition to VGA

[PATCH] drm: hdlcd: Replace the mode config's atomic_commit with the proper implementation.

On Tue, May 31, 2016 at 12:03:04PM +0100, Liviu Dudau wrote: > The HDLCD atomic_commit code was mis-using the drm_atomic_helper_commit() > function to implement the non-blocking code. Replace that with the correct > implementation that does the async queue-ing of commits. > > Signed-off-by: Liviu

[Nouveau] [PATCH 1/9] drm/nouveau: Don't leak runtime pm ref on driver unload

On Mon, May 30, 2016 at 07:03:46PM +0200, Peter Wu wrote: > On Sun, May 29, 2016 at 05:50:06PM +0200, Lukas Wunner wrote: > > How exactly did you reach the situation where the root port didn't wake > > up when you tried to load nouveau again? (IRC conversation this week.) > > Ensure that the

[PATCHv2 0/4] drm: fix two atomic modesetting issues on v4.7-rc1

These fix two atomic modesetting issues on v4.7-rc1. The last one is a bit of an RFC. Changes to v1: - drop unnecessary cleanups from "drm: make drm_atomic_set_mode_prop_for_crtc() more reliable". - Cc stable where appropriate - Add "Fixes:" to "drm: fix fb refcount issue with atomic

[PATCHv2 1/4] drm: add missing drm_mode_set_crtcinfo call

When setting mode via MODE_ID property, drm_atomic_set_mode_prop_for_crtc() does not call drm_mode_set_crtcinfo() which possibly causes: "[drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 32: Can't calculate constants, dotclock = 0!" Whether the error is seen depends on the previous data

[PATCHv2 2/4] drm/sti: remove extra mode fixup

Commit 652353e6e561c2aeeac62df183f721f6f9b5b45f ("drm/sti: set CRTC modesetting parameters") added a hack to avoid warnings related to setting mode with atomic API. With the previous patch, the hack should no longer be necessary. Signed-off-by: Tomi Valkeinen Cc: Benjamin Gaignard Cc: Vincent

[PATCHv2 3/4] drm: make drm_atomic_set_mode_prop_for_crtc() more reliable

drm_atomic_set_mode_prop_for_crtc() does not clear the state->mode, so old data may be left there when a new mode is set, possibly causing odd issues. This patch improves the situation by always clearing the state->mode first. Signed-off-by: Tomi Valkeinen Cc: stable at vger.kernel.org ---

[PATCHv2 4/4] drm: fix fb refcount issue with atomic modesetting

After commit 027b3f8ba9277410c3191d72d1ed2c6146d8a668 ("drm/modes: stop handling framebuffer special") extra fb refs are left around when doing atomic modesetting. The problem is that the new drm_property_change_valid_get() does not return anything in the '**ref' parameter, which causes

[Nouveau] [PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM

On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > Do you have any suggestions for the case where the pcieport driver > refuses to put the bridge in D3 (because the BIOS is too old)? In that > case the nouveau driver needs to fallback to the DSM method (but not > when runtime PM is

[PATCH 07/26] drm/exynos: Use for_each_crtc_in_state

2016-05-30 3:35 GMT+09:00 Daniel Vetter : > We want to hide drm_atomic_state internals better. > Acked-by: Inki Dae > Cc: Inki Dae > Signed-off-by: Daniel Vetter > --- > drivers/gpu/drm/exynos/exynos_drm_drv.c | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git

[Intel-gfx] [PATCH 12/26] drm/atomic-helper: Massage swap_state signature somewhat

Op 31-05-16 om 12:46 schreef Daniel Vetter: > On Tue, May 31, 2016 at 10:43:56AM +0200, Maarten Lankhorst wrote: >> Op 30-05-16 om 17:09 schreef Daniel Vetter: >>> On Mon, May 30, 2016 at 03:08:39PM +0200, Maarten Lankhorst wrote: Op 29-05-16 om 20:35 schreef Daniel Vetter: > - dev is

[GIT PULL] omapdrm fixes for 4.7

A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/3cc648f7/attachment.sig>

[PATCH 4/5] add cursor hotspot to drm_framebuffer

On Tue, May 31, 2016 at 12:53:12PM +0200, Gerd Hoffmann wrote: > Signed-off-by: Gerd Hoffmann > --- > drivers/gpu/drm/drm_crtc.c | 2 ++ > include/drm/drm_crtc.h | 2 ++ > 2 files changed, 4 insertions(+) > > diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c > index

[PATCH] virtio-gpu: use src not crtc

Pick up the correct source rectangle from framebuffer. Without this multihead setups are not working correctly. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_plane.c | 31 ++- 1 file changed, 18 insertions(+), 13 deletions(-) diff --git

[RFC 00/21] Renesas r8a7795/Salvator-X HDMI output prototype

On Mon, May 30, 2016 at 5:59 PM, Ulrich Hecht wrote: > Hi! > > This is a prototype of HDMI output support for the Renesas r8a7795 SoC and > Salvator-X board. It is based on the renesas-devel-20160516-v4.6 tree and Actually, it is based on

[PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM

On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > Do you have any suggestions for the case where the pcieport driver > refuses to put the bridge in D3 (because the BIOS is too old)? In that > case the nouveau driver needs to fallback to the DSM method (but not > when runtime PM is

[Nouveau] [PATCH 1/9] drm/nouveau: Don't leak runtime pm ref on driver unload

On Tue, May 31, 2016 at 01:34:43PM +0200, Lukas Wunner wrote: > On Mon, May 30, 2016 at 07:03:46PM +0200, Peter Wu wrote: > > On Sun, May 29, 2016 at 05:50:06PM +0200, Lukas Wunner wrote: > > > How exactly did you reach the situation where the root port didn't wake > > > up when you tried to load

[PATCH 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM

On Tue, May 31, 2016 at 11:43:56AM +0300, Mika Westerberg wrote: > On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > > Do you have any suggestions for the case where the pcieport driver > > refuses to put the bridge in D3 (because the BIOS is too old)? In that > > case the nouveau driver

did the drm patch to support Iris(TM) Graphics P555 fell through the cracks? (Was: Re: [Intel-gfx] RFC: libdrm: Support Iris Graphics 540 & 550 (Skylake GT3e))

CCing danvet Thorsten Leemhuis wrote on 28.04.2016 10:37: > Kenneth Graunke wrote on 28.04.2016 03:05: >> On Wednesday, April 27, 2016 9:37:07 AM PDT Thorsten Leemhuis wrote: >>> Thorsten Leemhuis wrote on 26.04.2016 13:41: >>> Forget that patch -- a way better one was submitted weeks ago my

[PATCHv2 3/4] drm: make drm_atomic_set_mode_prop_for_crtc() more reliable

On Tue, May 31, 2016 at 03:03:17PM +0300, Tomi Valkeinen wrote: > drm_atomic_set_mode_prop_for_crtc() does not clear the state->mode, so > old data may be left there when a new mode is set, possibly causing odd > issues. > > This patch improves the situation by always clearing the state->mode >

[PATCH 01/10] drm: Initialize a linear gamma table by default

Op 30-03-16 om 11:51 schreef Daniel Vetter: > Code stolen from gma500. It would be useful to mention why this is done. :) But even with this patch it seems the legacy gamma in gamma_get is not very reliable. A failed call to gamma_set could leave wrong values in crtc->gamma_store either by

[PATCH 4/5] add cursor hotspot to drm_framebuffer

On Di, 2016-05-31 at 15:36 +0300, Ville Syrjälä wrote: > Why store it in the fb and not eg. the plane state? Well, drm_plane_state is allocated by drm_atomic_helper_update_plane. When sticking the hotspot into the the plane state we have to add hot_x and hot_y parameters to

[PATCH 02/10] drm/fb-helper: Remove dead code in setcolreg

Op 30-03-16 om 11:51 schreef Daniel Vetter: > DRM fbdev emulation only supports pallete_color with depth == 8, and > truecolor with depth > 8. Handling depth == 16 for palettes is hence > dead code, let's remove it. Hooray, less chance for failure! Reviewed-by: Maarten Lankhorst

[PATCH 05/10] drm/cirrus: Drop redundnant gamma size check

Op 30-03-16 om 11:51 schreef Daniel Vetter: > The core does this for us already. Unfortunately some other drivers do the same. :( various variations of end = min_t(start + size, 256); I'll kill the rest off when killing start parameter and returning int. Reviewed-by: Maarten Lankhorst

[PATCH 16/26] drm/hdlcd: Use helper support for nonblocking commits

On Tue, May 31, 2016 at 01:07:15PM +0200, Daniel Vetter wrote: > On Tue, May 31, 2016 at 12:02:23PM +0100, Liviu Dudau wrote: > > On Sun, May 29, 2016 at 08:35:13PM +0200, Daniel Vetter wrote: > > > Again, just doing them as blocking commits isn't cool. > > > > > > From a cursory check hdlcd does

[PATCH 06/10] drm/msm: Nuke dummy gamma_set/get functions

Op 30-03-16 om 11:51 schreef Daniel Vetter: > Again the fbdev emulation gamma_set/get functions are only needed for > drivers that try to also use 8bpp paletted mode. Which msm doesn't, so > this is dead code. Let's rip it out. > > Cc: Rob Clark > Signed-off-by: Daniel Vetter Reviewed-by:

[PATCH 09/10] drm/qxl: Don't set a gamma table size

Op 30-03-16 om 11:51 schreef Daniel Vetter: > qxl doesn't have any functions for setting the gamma table, so this is > completely defunct. > > Not nice to lie to userspace, so let's stop! Reviewed-by: Maarten Lankhorst

[PATCH 16/27] drm/vgem: Use lockless gem BO free callback

On Mon, May 30, 2016 at 1:53 PM, Daniel Vetter wrote: > No dev->struct_mutex anywhere to be seen. > > Cc: seanpaul at chromium.org > Signed-off-by: Daniel Vetter Reviewed-by: Sean Paul > --- > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff

[PATCH 01/10] drm: Initialize a linear gamma table by default

On Tue, May 31, 2016 at 03:05:32PM +0200, Maarten Lankhorst wrote: > Op 30-03-16 om 11:51 schreef Daniel Vetter: > > Code stolen from gma500. > It would be useful to mention why this is done. :) > > But even with this patch it seems the legacy gamma in gamma_get is not very > reliable. > A

[PATCH 02/10] drm/fb-helper: Remove dead code in setcolreg

On Tue, May 31, 2016 at 03:09:42PM +0200, Maarten Lankhorst wrote: > Op 30-03-16 om 11:51 schreef Daniel Vetter: > > DRM fbdev emulation only supports pallete_color with depth == 8, and > > truecolor with depth > 8. Handling depth == 16 for palettes is hence > > dead code, let's remove it. >

[PATCH 09/10] drm/qxl: Don't set a gamma table size

On Tue, May 31, 2016 at 03:17:57PM +0200, Maarten Lankhorst wrote: > Op 30-03-16 om 11:51 schreef Daniel Vetter: > > qxl doesn't have any functions for setting the gamma table, so this is > > completely defunct. > > > > Not nice to lie to userspace, so let's stop! > Reviewed-by: Maarten Lankhorst

[PATCH 16/27] drm/vgem: Use lockless gem BO free callback

On Tue, May 31, 2016 at 09:20:07AM -0400, Sean Paul wrote: > On Mon, May 30, 2016 at 1:53 PM, Daniel Vetter > wrote: > > No dev->struct_mutex anywhere to be seen. > > > > Cc: seanpaul at chromium.org > > Signed-off-by: Daniel Vetter > > Reviewed-by: Sean Paul Applied to drm-misc, thanks for

[PATCH 01/10] drm: Initialize a linear gamma table by default

Op 31-05-16 om 15:24 schreef Daniel Vetter: > On Tue, May 31, 2016 at 03:05:32PM +0200, Maarten Lankhorst wrote: >> Op 30-03-16 om 11:51 schreef Daniel Vetter: >>> Code stolen from gma500. >> It would be useful to mention why this is done. :) >> >> But even with this patch it seems the legacy

[PATCH 00/27] locklesss gem BO free driver patches

Hi Daniel! On 30 May 2016 at 23:22, Daniel Vetter wrote: > HI all, > > Here's the pile of lockless gem BO free conversion patches. Assuming I didn't > botch it these are all the ones that didn't yet get an ack. Since this is all > pretty boring stuff I'll just send a pull request to Dave later

Bad flicker on skylake HQD due to code in the 4.7 merge window

On Tue, 2016-05-31 at 10:51 +0300, Jani Nikula wrote: > On Mon, 30 May 2016, James Bottomley < > James.Bottomley at HansenPartnership.com> wrote: > > I've tested a pristine 4.6.0 system, so it's definitely something > > that > > went in during the merge window. The flicker isn't continuous, > >

[PATCH] drm/omap: rename panel/encoder Kconfig names

omapdrm is using much too generic Kconfig names for its panels and encoders. Rename them to have "DRM_OMAP" in the name. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/displays/Kconfig | 28 ++-- drivers/gpu/drm/omapdrm/displays/Makefile | 28

[RFC PATCH v1 0/2]

The full name of PSR is Panel Self Refresh, panel device could refresh itself with the hardware framebuffer in panel, this would make a lots of sense to save the power consumption. For example, when desktop haven't change the context for a long time, then we could refresh the data to the hardware

[RFC PATCH v1 1/2] drm/rockchip: add a notify event about vblank enable/disable

EDP PSR function is interesting in vblank enable or disable event, so it would be great introduce a way to notify encoder about this event. Signed-off-by: Yakir Yang --- drivers/gpu/drm/rockchip/Makefile | 2 +- drivers/gpu/drm/rockchip/rockchip_drm_notify.c | 66

[RFC PATCH v1 2/2] drm/rockchip: analogix: add eDP PSR function

The full name of PSR is Panel Self Refresh, panel device could refresh itself with the hardware framebuffer in panel, this would make a lots of sense to save the power consumption. For example, when desktop haven't change the context for a long time, then we could refresh the data to the hardware

[Bug 94860] [radeonsi/amdgpu][DCC] screen is corrupted when logging out of kde

<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/0feccc41/attachment.html>

[PATCH 4/5] add cursor hotspot to drm_framebuffer

On Tue, May 31, 2016 at 03:09:13PM +0200, Gerd Hoffmann wrote: > On Di, 2016-05-31 at 15:36 +0300, Ville Syrjälä wrote: > > > Why store it in the fb and not eg. the plane state? > > Well, drm_plane_state is allocated by drm_atomic_helper_update_plane. > > When sticking the hotspot into the

[Intel-gfx] [PATCH] drm/atomic-helper: nonblocking commit support

Op 30-05-16 om 10:01 schreef Daniel Vetter: > Design ideas: > > - split up the actual commit into different phases, and have > completions for each of them. This will be useful for the future > when we want to interleave phases much more aggressively, for e.g. > queue depth > 1. For not it's

[PATCH 1/2] MAINTAINERS: add entry for the Sync File Framework

From: Gustavo Padovan Add Gustavo as maintainer for the Sync File Framework. Sumit is co-maintainer as he maintains drivers/dma-buf/. It also uses Sumit's tree as base. Signed-off-by: Gustavo Padovan Acked-by: Sumit Semwal Acked-by: Maarten Lankhorst ---

[PATCH 2/2] dma-buf/sync_file: improve Kconfig description for Sync Files

From: Gustavo Padovan We've got a complaint saying that the description was quite obtuse and indeed it was. This patch tries to improve it. Cc: Dave Jones Signed-off-by: Gustavo Padovan --- drivers/dma-buf/Kconfig | 15 --- 1 file changed, 12

[Intel-gfx] [PATCH] drm/atomic-helper: nonblocking commit support

On Tue, May 31, 2016 at 04:22:57PM +0200, Maarten Lankhorst wrote: > Op 30-05-16 om 10:01 schreef Daniel Vetter: > > Design ideas: > > > > - split up the actual commit into different phases, and have > > completions for each of them. This will be useful for the future > > when we want to

[RFC PATCH v1 1/2] drm/rockchip: add a notify event about vblank enable/disable

On Tue, May 31, 2016 at 09:39:19PM +0800, Yakir Yang wrote: > EDP PSR function is interesting in vblank enable or disable event, > so it would be great introduce a way to notify encoder about this > event. > > Signed-off-by: Yakir Yang notifiers considered evil, especially if you add a global

[RFC PATCH v1 0/2]

On Tue, May 31, 2016 at 09:37:36PM +0800, Yakir Yang wrote: > The full name of PSR is Panel Self Refresh, panel device could refresh > itself with the hardware framebuffer in panel, this would make a lots > of sense to save the power consumption. > > For example, when desktop haven't change the

[PATCH] drm: hdlcd: Cleanup the atomic operations

Dispatch DRM pending events from crtc_atomic_flush() and not from the IRQ handler. Don't disable the vsync interrupt, as the hardware lacks hardware counters for vsync time stamping. Signed-off-by: Liviu Dudau --- This replaces the previous patch "drm: hdlcd: Replace the mode config's

[Bug 94860] [radeonsi/amdgpu][DCC] screen is corrupted when logging out of kde

ail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/ea213ff5/attachment-0001.html>

[PATCH 0/6] drm/i915: Remaining PSR fixes

From: Ville Syrjälä Here's a repost of my PSR fixes, and one straggler from Daniel. One interesting thing I noticed is that my SKL actually hits the PSR setup time vs. vblank length check, so after these patches that machine won't actually use PSR. The panel

[PATCH v2 1/6] drm/dp: Add drm_dp_psr_setup_time()

From: Ville Syrjälä Add a small helper to parse the PSR setup time from the DPCD PSR capabilities and return the value in microseconds. v2: Don't waste so many bytes on the psr_setup_time_us[] table Cc: Daniel Vetter Reviewed-by: Daniel Vetter Signed-off-by:

[PATCH v2 2/6] drm/dp: Add drm_dp_psr_need_train_on_exit()

From: Ville Syrjälä Add a small helper to parse from the DPCD whether link training is required when exiting PSR main-link off mode. v2: Rebased Cc: Daniel Vetter Reviewed-by: Daniel Vetter Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/drm_dp_helper.c

[PATCH 3/6] drm/i915: Check PSR setup time vs. vblank length

From: Ville Syrjälä Bspec says: "Restriction : SRD must not be enabled when the PSR Setup time from DPCD 00071h is greater than the time for vertical blank minus one line." Let's check for that and disallow PSR if we exceed the limit. Cc: Daniel Vetter

[PATCH 4/6] drm/i915/psr: Skip aux handeshake if the vbt tells us to

From: Daniel Vetter Not sure we can trust VBT on this one, but let's try. Cc: Rodrigo Vivi Cc: Sonika Jindal Cc: Durgadoss R Signed-off-by: Daniel Vetter Reviewed-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_psr.c | 3 +++ 1 file changed, 3 insertions(+)

[PATCH 5/6] drm/i915: Ask the sink whether training is required when exiting PSR main-link off mode

From: Ville Syrjälä The sink can tell us if link training needs to be performed when exiting PSR main-link off mode. Currently we get that information from the VBT, but at least on my HSW the VBT says one thing, the sink another. And in practice the sink doesn't

[PATCH 6/6] drm/i915: Move psr.link_standby setup to intel_psr_match_conditions()

From: Ville Syrjälä Determine the value of psr.link_standby at runtime rather than at init time. This helps in testing since you can change between link-off and link-standby at runtime. Reviewed-by: Daniel Vetter Signed-off-by: Ville Syrjälä ---

[Bug 94860] [radeonsi/amdgpu][DCC] screen is corrupted when logging out of kde

was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/943c9c1a/attachment-0001.html>

[Bug 94860] [radeonsi/amdgpu][DCC] screen is corrupted when logging out of kde

was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/91ce6f0c/attachment.html>

[Bug 93216] Artifacts with DCC when render target also texture

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/19e4e1a8/attachment.html>

[PATCH 2/4] drm/fb_helper: Fix references to dev->mode_config.num_connector

commit 255f0e7c418ad95a4baeda017ae6182ba9b3c423 upstream. During boot, MST hotplugs are generally expected (even if no physical hotplugging occurs) and result in DRM's connector topology changing. This means that using num_connector from the current mode configuration can lead to the number of

[PATCH 4/4] drm/atomic: Verify connector->funcs != NULL when clearing states

Unfortunately since we don't have Dave's connector refcounting patch here yet, it's very possible that drm_atomic_state_default_clear() could get called by intel_display_resume() when intel_dp_mst_destroy_connector() isn't completely finished destroying an mst connector, but has already finished

[RFC v2] dma-mapping: Use unsigned long for dma_attrs

On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote: > The dma-mapping core and the implementations do not change the > DMA attributes passed by pointer. Thus the pointer can point to const > data. However the attributes do not have to be a bitfield. Instead > unsigned long will

[PATCH 15/27] drm/vc4: Use lockless gem BO free callback

<https://lists.freedesktop.org/archives/dri-devel/attachments/20160531/9d569ec0/attachment.sig>

[RFT v3] drm: use late_initcall() for amdkfd and radeon

On Tue, May 31, 2016 at 8:15 PM, Luis R. Rodriguez wrote: > On Sun, May 29, 2016 at 05:49:17PM +0300, Oded Gabbay wrote: >> On Fri, May 27, 2016 at 4:18 AM, Luis R. Rodriguez >> wrote: >> > diff --git a/drivers/gpu/drm/radeon/radeon_drv.c >> > b/drivers/gpu/drm/radeon/radeon_drv.c >> > index

[RFC v2] dma-mapping: Use unsigned long for dma_attrs

On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote: > The dma-mapping core and the implementations do not change the > DMA attributes passed by pointer. Thus the pointer can point to const > data. However the attributes do not have to be a bitfield. Instead > unsigned long will

[Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch

tps://lists.freedesktop.org/archives/dri-devel/attachments/20160531/a6bb9a80/attachment.html>

[Bug 93217] [tonga] [powerplay] Radon M395X isn't initialised with the powerplay branch

org/archives/dri-devel/attachments/20160531/54493392/attachment.html>

[RFT v3] drm: use late_initcall() for amdkfd and radeon

On Tue, May 31, 2016 at 06:58:34PM +0200, Luis R. Rodriguez wrote: > On Sun, May 29, 2016 at 08:27:07PM +0200, Daniel Vetter wrote: > > On Fri, May 27, 2016 at 3:18 AM, Luis R. Rodriguez > > wrote: > > > To get KFD support in radeon we need the following > > > initialization to happen in this

[PATCH 0/6] drm/i915: Remaining PSR fixes

On Tue, May 31, 2016 at 06:50:24PM +0300, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > Here's a repost of my PSR fixes, and one straggler from Daniel. > > One interesting thing I noticed is that my SKL actually hits the PSR setup > time vs. vblank length check, so after

[PATCH 15/27] drm/vc4: Use lockless gem BO free callback

On Tue, May 31, 2016 at 10:23:32AM -0700, Eric Anholt wrote: > Daniel Vetter writes: > > > No dev->struct_mutex anywhere to be seen. > > The vc4 patches are: > > Reviewed-by: Eric Anholt Thanks for the review, both applied to drm-misc. -Daniel -- Daniel Vetter Software Engineer, Intel

[PATCH 0/6] drm/i915: Remaining PSR fixes

On Tue, May 31, 2016 at 09:07:49PM +0200, Daniel Vetter wrote: > On Tue, May 31, 2016 at 06:50:24PM +0300, ville.syrjala at linux.intel.com > wrote: > > From: Ville Syrjälä > > > > Here's a repost of my PSR fixes, and one straggler from Daniel. > > > > One interesting thing I noticed is that

[PATCH 00/18] staging/android: clean up SW_SYNC

From: Gustavo Padovan Hi, The following patches do a clean up on the sw_sync inteface. It starts by removing struct sync_timeline_ops, which was creating unecessary wrappers in the code and the start to organize the sync_timeline and sw_sync code better.

[PATCH 01/18] staging/android: store last signaled value on sync timeline

From: Gustavo Padovan Now fence timeline is aware of the last signaled fence, as it receives the increment to the current value in sync_timeline_signal(). That allow us to remove .has_signaled() from timeline_ops as we can directly compare using timeline->value

[PATCH 02/18] staging/android: remove .{fence, timeline}_value_str() from timeline_ops

From: Gustavo Padovan Now that the value of fence and the timeline are not stored by sw_sync anymore we can remove this extra abstraction to retrieve this data. This patch changes both fence_ops (.fence_value_str and .timeline_value_str) to return the str

[PATCH 04/18] staging/android: remove sw_sync_timeline and sw_sync_pt

From: Gustavo Padovan As we moved value storage to sync_timeline and fence those two structs became useless and can be removed now. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c| 24 +++-

[PATCH 03/18] staging/android: remove struct sync_timeline_ops

From: Gustavo Padovan Move drv_name, the last field of sync_timeline_ops, to sync_timeline and remove sync_timeline_ops. struct sync_timeline_ops was just an extra abstraction on top of fence_ops, and in the last few commits we removed all it ops in favor of

[PATCH 05/18] staging/android: remove sw_sync.[ch] files

From: Gustavo Padovan We can glue the sw_sync file operations directly on the sync framework without the need to pass through sw_sync wrappers. It only builds sw_sync debugfs file support if CONFIG_SW_SYNC is enabled. Signed-off-by: Gustavo Padovan ---

[PATCH 06/18] staging/android: rename android_fence to timeline_fence

From: Gustavo Padovan We are moving out of staging/android so rename it to a name that is not related to android anymore. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 36 ++-- 1 file changed, 18

[PATCH 07/18] staging/android: remove unnecessary check for fence

From: Gustavo Padovan When we call sync_print_fence() fence is always valid. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync_debug.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/staging/android/sync_debug.c

[PATCH 08/18] staging/android: remove size arg of sync_timeline_create()

From: Gustavo Padovan After we removed sw_sync_timeline this arg has not been really used by anyone, all its users pass the size of struct sync_timeline there. So simplify this function but not requiring the size anymore. Signed-off-by: Gustavo Padovan ---

[PATCH 09/18] staging/android: bring struct sync_pt back

From: Gustavo Padovan Move the list_head members from sync_pt to struct fence was a mistake, they will not be used by struct fence as planned before, so here we create sync_pt again to bring the list heads back. Signed-off-by: Gustavo Padovan ---

[PATCH v2 0/10] Add RK3399 eDP support and fix some bugs to analogix_dp driver.

Hello Yakir, On 05/27/2016 02:16 AM, Yakir Yang wrote: > Hi Javier, > > On 05/26/2016 08:48 PM, Javier Martinez Canillas wrote: >> Hello Yakir, >> >> On 05/26/2016 05:34 AM, Yakir Yang wrote: >>> Hi Javier, >>> >>> On 05/24/2016 01:01 PM, Yakir Yang wrote: Hi all, This series have

[PATCH 14/18] staging/android: remove 'destroyed' member from struct sync_timeline

From: Gustavo Padovan 'destroyed' was set but not used ny anyone. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c | 5 - drivers/staging/android/sync.h| 5 + 2 files changed, 1 insertion(+), 9 deletions(-) diff --git

  1   2   >