[drm-intel:drm-intel-next-queued 6/11] ERROR: "__udivdi3" [drivers/gpu/drm/i915/i915.ko] undefined!

Size: 25898 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/038d9bb7/attachment-0001.gz>

[Bug 95306] Random Blank(black) screens on "Carrizo"

are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/63d1c5aa/attachment-0001.html>

[Bug 93341] Semi-random GPU lockups on radeonsi with a RadeonHD 7770 (when playing videos, running OpenGL games, WebGL apps, or after extended periods of time)

it to be the latest released at this time. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/0d6a68c2/attachment.html>

[Bug 93649] [radeonsi] Graphics lockup while playing tf2

tps://lists.freedesktop.org/archives/dri-devel/attachments/20161123/025c7e61/attachment.html>

[RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

On 11/23/2016 01:16 AM, John Stultz wrote: > On Tue, Nov 22, 2016 at 9:38 AM, Laurent Pinchart > wrote: >> Hi John, >> >> On Tuesday 22 Nov 2016 09:25:22 John Stultz wrote: >>> On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote: On Monday 21 Nov 2016 16:37:30 John Stultz wrote: >>>

[PATCH] drm/nouveau/kms/nv50: Fix atomic pageflip events.

The new atomic modesetting/pageflip code for nv50+ for Linux 4.10+ no longer uses pageflip irq's to signal flip completion. Instead it polls for flip completion from within a kthread/work queue. This creates a race between the vblank irq handler updating the vblank count and timestamp for the

[PATCH libdrm v3 0/4] etna_pipe_wait_ns(..)

Add an API to pass the timeout value (ns) from pipe->fence_finish(..) to the kernel. The current API accepts ms and special handling is needed for PIPE_TIMEOUT_INFINITE. The idea is not to break old mesa (out-of-tree) + new libdrm. It may be possible to break etnaviv's ABI as the gallium driver

[PATCH libdrm v3 1/4] etnaviv: add etna_pipe_wait_ns(..)

We need to pass through a timeout parameter to implement pipe->fence_finish() properly. The new fxn accepts a timeout in nanoseconds. Signed-off-by: Christian Gmeiner --- etnaviv/etnaviv-symbol-check | 1 + etnaviv/etnaviv_drmif.h | 1 + etnaviv/etnaviv_pipe.c | 24

[PATCH libdrm v3 3/4] etnaviv: use get_abs_timeout_ns(..) internally

Signed-off-by: Christian Gmeiner --- etnaviv/etnaviv_bo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/etnaviv/etnaviv_bo.c b/etnaviv/etnaviv_bo.c index 833f8bd..ed1f516 100644 --- a/etnaviv/etnaviv_bo.c +++ b/etnaviv/etnaviv_bo.c @@ -330,7 +330,7 @@ int

[PATCH libdrm v3 2/4] etnaviv: simplify etna_pipe_wait(..)

We can make use of etna_pipe_wait_ns(..). Signed-off-by: Christian Gmeiner --- etnaviv/etnaviv_pipe.c | 21 + 1 file changed, 1 insertion(+), 20 deletions(-) diff --git a/etnaviv/etnaviv_pipe.c b/etnaviv/etnaviv_pipe.c index f2e417f..6951362 100644 ---

[PATCH libdrm v3 4/4] etnaviv: drop get_abs_timeout(..)

It has no callers so drop it. Signed-off-by: Christian Gmeiner --- etnaviv/etnaviv_priv.h | 9 - 1 file changed, 9 deletions(-) diff --git a/etnaviv/etnaviv_priv.h b/etnaviv/etnaviv_priv.h index 30cc1bd..667bf23 100644 --- a/etnaviv/etnaviv_priv.h +++ b/etnaviv/etnaviv_priv.h @@

[Intel-gfx] [PATCH 3/5] drm/i915: Update CRTC state if connector link status property changed

On Tue, Nov 22, 2016 at 05:15:59PM -0800, Manasi Navare wrote: > On Mon, Nov 21, 2016 at 04:48:07PM +0100, Daniel Vetter wrote: > > On Mon, Nov 21, 2016 at 11:10:45AM +0100, Daniel Vetter wrote: > > > On Mon, Nov 21, 2016 at 09:42:57AM +, Chris Wilson wrote: > > > > On Mon, Nov 21, 2016 at

Enabling peer to peer device transactions for PCIe devices

On Tue, Nov 22, 2016 at 01:21:03PM -0800, Dan Williams wrote: > On Tue, Nov 22, 2016 at 1:03 PM, Daniel Vetter wrote: > > On Tue, Nov 22, 2016 at 9:35 PM, Serguei Sagalovitch > > wrote: > >> > >> On 2016-11-22 03:10 PM, Daniel Vetter wrote: > >>> > >>> On Tue, Nov 22, 2016 at 9:01 PM, Dan

[RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on

On Tue, Nov 22, 2016 at 08:23:38PM +0200, Laurent Pinchart wrote: > Hi John, > > (CC'ing Daniel) > > On Tuesday 22 Nov 2016 10:07:53 John Stultz wrote: > > On Tue, Nov 22, 2016 at 9:38 AM, John Stultz > > wrote: > > > Interestingly, without the msleep added in this patch, removing the > > >

[Intel-gfx] [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests

On Tue, Nov 22, 2016 at 01:39:26PM -0800, Manasi Navare wrote: > The intel_dp_autotest_video_pattern() function gets invoked through the > compliance test handler on a HPD short pulse if the test type is > set to DP_TEST_VIDEO_PATTERN. This performs the DPCD registers > reads to read the requested

[RFC PATCH 0/3] staging: remove fbdev drivers

Hi, Since the fbdev framework is in maintenance mode and all new display drivers should be made with the DRM framework, remove the fbdev drivers from staging. Note: the patches are created with git format-patch -D, so they can't be applied. Only for review. Tomi Tomi Valkeinen (3): staging:

[RFC PATCH 2/3] staging: remove sm750fb

Since the fbdev framework is in maintenance mode and all new display drivers should be made with the DRM framework, remove sm750fb from staging. Signed-off-by: Tomi Valkeinen --- MAINTAINERS |8 - drivers/staging/Kconfig |2 -

[RFC PATCH 3/3] staging: remove fbtft

Since the fbdev framework is in maintenance mode and all new display drivers should be made with the DRM framework, remove fbtft from staging. Signed-off-by: Tomi Valkeinen --- MAINTAINERS|6 - drivers/staging/Kconfig|2 -

[RFC PATCH 1/3] staging: remove xgifb

Since the fbdev framework is in maintenance mode and all new display drivers should be made with the DRM framework, remove xgifb from staging. Especially as xgifb has been in staging for 6 years... Signed-off-by: Tomi Valkeinen --- MAINTAINERS |5 -

[Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)

Hi, > >> +L:qemu-devel at nongnu.org > > qemu-devel list already has very high traffic - not sure whether it > makes much sense to route even more additional patches here. Maybe > rather create a separate mailing list like qemu-graphics at nongnu.org ? > So you've

[PATCH RFC] drm: Add a new connector atomic property for link status

On Tue, Nov 22, 2016 at 09:27:35PM -0500, Sean Paul wrote: > On Tue, Nov 22, 2016 at 8:30 PM, Manasi Navare > wrote: > > This is RFC patch for adding a connector link-status property > > and making it atomic by adding it to the drm_connector_state. > > This is to make sure its wired properly in

[RFC PATCH 0/3] staging: remove fbdev drivers

On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote: > Hi, > > Since the fbdev framework is in maintenance mode and all new display drivers > should be made with the DRM framework, remove the fbdev drivers from staging. > > Note: the patches are created with git format-patch -D, so

[RFC PATCH 0/3] staging: remove fbdev drivers

Hi Daniel, On Wed, Nov 23, 2016 at 9:19 AM, Daniel Vetter wrote: > On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote: >> Since the fbdev framework is in maintenance mode and all new display drivers >> should be made with the DRM framework, remove the fbdev drivers from staging. >>

[PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver

On 11/22/16 16:49, Jyri Sarha wrote: > Add very basic ti-tfp410 DVI transmitter driver. The only feature > separating this from a completely dummy bridge is the EDID read > support trough DDC I2C. Even that functionality should be in a > separate generic connector driver. However, because of

[RFC PATCH 0/3] staging: remove fbdev drivers

On Wed, Nov 23, 2016 at 9:25 AM, Geert Uytterhoeven wrote: > Hi Daniel, > > On Wed, Nov 23, 2016 at 9:19 AM, Daniel Vetter wrote: >> On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote: >>> Since the fbdev framework is in maintenance mode and all new display drivers >>> should be made

Enabling peer to peer device transactions for PCIe devices

Am 23.11.2016 um 08:49 schrieb Daniel Vetter: > On Tue, Nov 22, 2016 at 01:21:03PM -0800, Dan Williams wrote: >> On Tue, Nov 22, 2016 at 1:03 PM, Daniel Vetter wrote: >>> On Tue, Nov 22, 2016 at 9:35 PM, Serguei Sagalovitch >>> wrote: On 2016-11-22 03:10 PM, Daniel Vetter wrote: > On

[RFC PATCH 0/3] staging: remove fbdev drivers

On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote: > Hi, > > Since the fbdev framework is in maintenance mode and all new display drivers > should be made with the DRM framework, remove the fbdev drivers from staging. > > Note: the patches are created with git format-patch -D, so

[RFC PATCH 0/3] staging: remove fbdev drivers

https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/9ff4e52f/attachment.sig>

[RFC PATCH 0/3] staging: remove fbdev drivers

On Wed, Nov 23, 2016 at 11:12:32AM +0200, Tomi Valkeinen wrote: > On 23/11/16 10:52, Greg Kroah-Hartman wrote: > > On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote: > >> Hi, > >> > >> Since the fbdev framework is in maintenance mode and all new display > >> drivers > >> should be

[RFC PATCH 0/3] staging: remove fbdev drivers

GP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/df060f80/attachment.sig>

[PATCH RFC] drm: Add a new connector atomic property for link status

On Tue, Nov 22, 2016 at 05:30:21PM -0800, Manasi Navare wrote: > This is RFC patch for adding a connector link-status property > and making it atomic by adding it to the drm_connector_state. > This is to make sure its wired properly in drm_atomic_connector_set_property > and

[PATCH v2] ARM: dts: da850: add the mstpri and ddrctl nodes

2016-11-22 23:23 GMT+01:00 David Lechner : > On 11/15/2016 05:00 AM, Bartosz Golaszewski wrote: >> >> Add the nodes for the MSTPRI configuration and DDR2/mDDR memory >> controller drivers to da850.dtsi. >> >> Signed-off-by: Bartosz Golaszewski >> --- >> v1 -> v2: >> - moved the priority

[PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function.

drm_get_format_name() de-references the buf parameter without checking if the pointer was not NULL. Given that the function is EXPORT-ed, lets sanitise the parameters before proceeding. v2: Use BUG_ON() to annoy users that did not pass valid parameters to function. Fixes: b3c11ac267d461d3d5

[PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function.

On Wed, 23 Nov 2016, Liviu Dudau wrote: > drm_get_format_name() de-references the buf parameter without checking > if the pointer was not NULL. Given that the function is EXPORT-ed, lets > sanitise the parameters before proceeding. > > v2: Use BUG_ON() to annoy users that did not pass valid

[PATCH v3 0/3] da8xx: fix section mismatch in new drivers

Sekhar noticed there's a section mismatch in the da8xx-mstpri and da8xx-ddrctl drivers. This is caused by calling of_flat_dt_get_machine_name() which has an __init annotation. This series addresses this issue by open coding routines that return the machine compatible string in both drivers. Once

[PATCH v3 3/3] bus: da8xx-mstpri: fix a typo

Should have been priorities. Signed-off-by: Bartosz Golaszewski --- drivers/bus/da8xx-mstpri.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/bus/da8xx-mstpri.c b/drivers/bus/da8xx-mstpri.c index 064eeb9..b17ba97 100644 --- a/drivers/bus/da8xx-mstpri.c +++

[PATCH v3 2/3] memory: da8xx-ddrctl: drop the call to of_flat_dt_get_machine_name()

In order to avoid a section mismatch use a locally implemented routine instead of of_flat_dt_get_machine_name() when printing the error message. Signed-off-by: Bartosz Golaszewski --- drivers/memory/da8xx-ddrctl.c | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-)

[PATCH v3 1/3] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name()

In order to avoid a section mismatch use a locally implemented routine instead of of_flat_dt_get_machine_name() when printing the error message. Signed-off-by: Bartosz Golaszewski --- drivers/bus/da8xx-mstpri.c | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-) diff

[PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver

On Wed, 23 Nov 2016, Jyri Sarha wrote: > On 11/22/16 16:49, Jyri Sarha wrote: >> Add very basic ti-tfp410 DVI transmitter driver. The only feature >> separating this from a completely dummy bridge is the EDID read >> support trough DDC I2C. Even that functionality should be in a >> separate

[PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function.

On Wed, Nov 23, 2016 at 01:00:07PM +0200, Jani Nikula wrote: > On Wed, 23 Nov 2016, Liviu Dudau wrote: > > drm_get_format_name() de-references the buf parameter without checking > > if the pointer was not NULL. Given that the function is EXPORT-ed, lets > > sanitise the parameters before

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

From: Nicolai Hähnle Fix a race condition involving 4 threads and 2 ww_mutexes as indicated in the following example. Acquire context stamps are ordered like the thread numbers, i.e. thread #1 should back off when it encounters a mutex locked by thread #0 etc. Thread

[PATCH 3/4] locking/Documentation: fix a typo

From: Nicolai Hähnle Cc: Peter Zijlstra Cc: Ingo Molnar Cc: dri-devel at lists.freedesktop.org Signed-off-by: Nicolai Hähnle --- Documentation/locking/00-INDEX | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/locking/00-INDEX

[PATCH 4/4] locking/ww_mutex: Fix a comment typo

From: Nicolai Hähnle Cc: Peter Zijlstra Cc: Ingo Molnar Cc: dri-devel at lists.freedesktop.org Signed-off-by: Nicolai Hähnle --- include/linux/ww_mutex.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/ww_mutex.h

[PATCH 2/4] locking/ww_mutex: Remove redundant wakeups in ww_mutex_set_context_slowpath

From: Nicolai Hähnle When ww_mutex_set_context_slowpath runs, we are in one of two situations: 1. The current task was woken up by ww_mutex_unlock. 2. The current task is racing with ww_mutex_unlock: We entered the slow path while lock->base.count <= 0, but skipped

[PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function.

On Wed, Nov 23, 2016 at 11:23:23AM +, Liviu Dudau wrote: > On Wed, Nov 23, 2016 at 01:00:07PM +0200, Jani Nikula wrote: > > On Wed, 23 Nov 2016, Liviu Dudau wrote: > > > drm_get_format_name() de-references the buf parameter without checking > > > if the pointer was not NULL. Given that the

[PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function.

On Wed, 23 Nov 2016, Daniel Vetter wrote: > On Wed, Nov 23, 2016 at 11:23:23AM +, Liviu Dudau wrote: >> On Wed, Nov 23, 2016 at 01:00:07PM +0200, Jani Nikula wrote: >> > On Wed, 23 Nov 2016, Liviu Dudau wrote: >> > > drm_get_format_name() de-references the buf parameter without checking >> >

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 12:25:22PM +0100, Nicolai Hähnle wrote: > From: Nicolai Hähnle > > Fix a race condition involving 4 threads and 2 ww_mutexes as indicated in > the following example. Acquire context stamps are ordered like the thread > numbers, i.e. thread #1 should back off when it

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 12:25:22PM +0100, Nicolai Hähnle wrote: > From: Nicolai Hähnle > > Fix a race condition involving 4 threads and 2 ww_mutexes as indicated in > the following example. Acquire context stamps are ordered like the thread > numbers, i.e. thread #1 should back off when it

[PATCH 1/5] drm/i915: Add support for DP link training compliance

On Tue, 22 Nov 2016, Manasi Navare wrote: > This patch adds support to handle automated DP compliance > link training test requests. This patch has been tested with > Unigraf DPR-120 DP Compliance device for testing Link > Training Compliance. > After we get a short pulse Compliance test request,

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 02:00:46PM +0100, Peter Zijlstra wrote: > On Wed, Nov 23, 2016 at 12:25:22PM +0100, Nicolai Hähnle wrote: > > From: Nicolai Hähnle > > > > Fix a race condition involving 4 threads and 2 ww_mutexes as indicated in > > the following example. Acquire context stamps are

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 02:08:48PM +0100, Daniel Vetter wrote: > On Wed, Nov 23, 2016 at 02:00:46PM +0100, Peter Zijlstra wrote: > > On Wed, Nov 23, 2016 at 12:25:22PM +0100, Nicolai Hähnle wrote: > > > From: Nicolai Hähnle > > > > > > Fix a race condition involving 4 threads and 2 ww_mutexes

[PATCH 3/5] Add support for forcing 6 bpc on DP pipes.

On Tue, 22 Nov 2016, Manasi Navare wrote: > From: Jim Bride > > For DP compliance we need to be able to control the output color > type for the pipe associated with the DP port. When a specific DP > compliance test is requested with specific BPC value, we read the BPC > value from the DPCD

[PATCH v3 01/11] drm/tilcdc: Enable sync lost error and recovery handling for rev 1 LCDC

2016-11-22 17:54 GMT+01:00 Jyri Sarha : > Revision 1 LCDC support also sync lost errors and can benefit from > sync lost recovery routine. > > Signed-off-by: Jyri Sarha > --- > drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 33 + > drivers/gpu/drm/tilcdc/tilcdc_regs.h |

[PATCH 4/5] drm: Add definitions for DP compliance Video pattern tests

On Tue, 22 Nov 2016, Manasi Navare wrote: > Cc: dri-devel at lists.freedesktop.org > Cc: Jani Nikula > Cc: Daniel Vetter > Cc: Ville Syrjala > Signed-off-by: Manasi Navare > --- > include/drm/drm_dp_helper.h | 16 +++- > 1 file changed, 15 insertions(+), 1 deletion(-) > > diff

[PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests

On Tue, 22 Nov 2016, Manasi Navare wrote: > The intel_dp_autotest_video_pattern() function gets invoked through the > compliance test handler on a HPD short pulse if the test type is > set to DP_TEST_VIDEO_PATTERN. This performs the DPCD registers > reads to read the requested test pattern, video

[PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function.

On Wed, Nov 23, 2016 at 02:47:53PM +0200, Jani Nikula wrote: > On Wed, 23 Nov 2016, Daniel Vetter wrote: > > On Wed, Nov 23, 2016 at 11:23:23AM +, Liviu Dudau wrote: > >> On Wed, Nov 23, 2016 at 01:00:07PM +0200, Jani Nikula wrote: > >> > On Wed, 23 Nov 2016, Liviu Dudau wrote: > >> > >

[PATCH v4 0/2] da8xx: fix section mismatch in new drivers

Sekhar noticed there's a section mismatch in the da8xx-mstpri and da8xx-ddrctl drivers. This is caused by calling of_flat_dt_get_machine_name() which has an __init annotation. This series makes the drivers drop the call and not print the machine name in the error message. v1 -> v2: - drop patch

[PATCH v4 2/2] memory: da8xx-ddrctl: drop the call to of_flat_dt_get_machine_name()

In order to avoid a section mismatch drop the call to of_flat_dt_get_machine_name() when printing the error message. Signed-off-by: Bartosz Golaszewski --- drivers/memory/da8xx-ddrctl.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/memory/da8xx-ddrctl.c

[PATCH v4 1/2] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name()

In order to avoid a section mismatch drop the call to of_flat_dt_get_machine_name() when printing the error message. While we're at it: fix a typo. Signed-off-by: Bartosz Golaszewski --- drivers/bus/da8xx-mstpri.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests

On Wed, Nov 23, 2016 at 03:37:24PM +0200, Jani Nikula wrote: > On Tue, 22 Nov 2016, Manasi Navare wrote: > > The intel_dp_autotest_video_pattern() function gets invoked through the > > compliance test handler on a HPD short pulse if the test type is > > set to DP_TEST_VIDEO_PATTERN. This performs

[PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests

On Wed, 23 Nov 2016, Ville Syrjälä wrote: > On Wed, Nov 23, 2016 at 03:37:24PM +0200, Jani Nikula wrote: >> On Tue, 22 Nov 2016, Manasi Navare wrote: >> > The intel_dp_autotest_video_pattern() function gets invoked through the >> > compliance test handler on a HPD short pulse if the test type

[Bug 98778] 3D is not working.

tps://lists.freedesktop.org/archives/dri-devel/attachments/20161123/a6aeb622/attachment.html>

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 12:25:22PM +0100, Nicolai Hähnle wrote: > @@ -473,7 +476,14 @@ void __sched ww_mutex_unlock(struct ww_mutex *lock) >*/ > mutex_clear_owner(>base); > #endif > - __mutex_fastpath_unlock(>base.count, __mutex_unlock_slowpath); > + /* > + * A

[PATCH 1/3] drm: Hold mode_config.lock to prevent hotplug whilst setting up crtcs

The fb_helper->connector_count is modified when a new connector is constructed following a hotplug event (e.g. DP-MST). This causes trouble for drm_setup_crtcs() and friends that assume that fb_helper is constant: [ 1250.872997] BUG: KASAN: slab-out-of-bounds in drm_setup_crtcs+0x320/0xf80 at

[PATCH 2/3] drm: Pull together probe + setup for drm_fb_helper

drm_fb_helper_probe_connector_modes() is always called before drm_setup_crtcs(), so just move the call into drm_setup_crtcs for a small bit of code compaction. Signed-off-by: Chris Wilson --- drivers/gpu/drm/drm_fb_helper.c | 37 +++-- 1 file changed, 11

[PATCH 3/3] drm: Protect fb_helper list manipulation with a mutex

Though we only walk the kernel_fb_helper_list inside a panic (or single thread debugging), we still need to protect the list manipulation on creating/removing a framebuffer device in order to prevent list corruption. Signed-off-by: Chris Wilson --- drivers/gpu/drm/drm_fb_helper.c | 5 + 1

[PATCH 1/5] drm: Define drm_mm_for_each_node_in_range()

Some clients would like to iterate over every node within a certain range. Make a nice little macro for them to hide the mixing of the rbtree search and linear walk. v2: Blurb Signed-off-by: Chris Wilson Cc: Daniel Vetter Cc: dri-devel at lists.freedesktop.org Reviewed-by: Joonas Lahtinen ---

[PATCH 2/5] drm: Check against color expansion in drm_mm_reserve_node()

Use the color_adjust callback when reserving a node to check if inserting a node into this hole requires any additional space, and so if that space then conflicts with an existing allocation. Signed-off-by: Chris Wilson Cc: Daniel Vetter Cc: dri-devel at lists.freedesktop.org Reviewed-by:

[PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests

On Wed, Nov 23, 2016 at 03:58:34PM +0200, Jani Nikula wrote: > On Wed, 23 Nov 2016, Ville Syrjälä wrote: > > On Wed, Nov 23, 2016 at 03:37:24PM +0200, Jani Nikula wrote: > >> On Tue, 22 Nov 2016, Manasi Navare wrote: > >> > The intel_dp_autotest_video_pattern() function gets invoked through

[PATCH 1/3] drm: Hold mode_config.lock to prevent hotplug whilst setting up crtcs

On Wed, 23 Nov 2016, Chris Wilson wrote: > +#define drm_fb_helper_for_each_connector(fbh, i__) \ > + for (({lockdep_assert_held(&(fbh)->dev->mode_config.mutex); 1;}), \ > + i__ = 0; i__ < (fbh)->connector_count; i__++) No comments on the substance, but just curious, why is that "1;"

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 03:03:36PM +0100, Peter Zijlstra wrote: > On Wed, Nov 23, 2016 at 12:25:22PM +0100, Nicolai Hähnle wrote: > > @@ -473,7 +476,14 @@ void __sched ww_mutex_unlock(struct ww_mutex *lock) > > */ > > mutex_clear_owner(>base); > > #endif > > -

[PATCH] drm-misc: Flesh out the documentation a bit

Gustovo asked whether there's docs for drm-misc, so took the opportunity to flesh out the very sparse existing write-up. Also adjust it to reality, since we've started to take some pretty big features in through drm-misc (like explicit fencing for atomic). v2: Be more clear on scope of drm-misc

[PATCH] MAINTAINERS: Add link to drm-misc documentation

Cc: Jani Nikula Cc: Sean Paul Acked-by: Jani Nikula Acked-by: Sean Paul Signed-off-by: Daniel Vetter --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index dcd96b447a73..7621fe9b9a97 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -4026,6 +4026,7 @@

[PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

On Wed, Nov 23, 2016 at 03:25:25PM +0100, Daniel Vetter wrote: > Without thinking it through in detail this is a PI issue, except that we > replace boosting with wakeup Could we perhaps steal something > from rt mutexes to make it fair? rt_mutexes order the waiters by 'priority' and wake the top

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: > On Tue, Nov 22, 2016 at 09:27:35PM -0500, Sean Paul wrote: >> On Tue, Nov 22, 2016 at 8:30 PM, Manasi Navare >> wrote: >> > This is RFC patch for adding a connector link-status property >> > and making it atomic by adding it to the

[PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests

On Wed, Nov 23, 2016 at 03:17:53PM +0100, Daniel Vetter wrote: > On Wed, Nov 23, 2016 at 03:58:34PM +0200, Jani Nikula wrote: > > On Wed, 23 Nov 2016, Ville Syrjälä > > wrote: > > > On Wed, Nov 23, 2016 at 03:37:24PM +0200, Jani Nikula wrote: > > >> On Tue, 22 Nov 2016, Manasi Navare wrote: >

[PATCH v3 06/11] drm/tilcdc: Enable palette loading for revision 2 LCDC too

2016-11-22 17:54 GMT+01:00 Jyri Sarha : > The LCDC revision 2 documentation also mentions the mandatory palette > for true color modes. Even if the rev 2 LCDC appears to work just fine > without the palette being loaded loading it helps in testing the > feature. > > Signed-off-by: Jyri Sarha >

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, 23 Nov 2016, Sean Paul wrote: > On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: >> On Tue, Nov 22, 2016 at 09:27:35PM -0500, Sean Paul wrote: >>> On Tue, Nov 22, 2016 at 8:30 PM, Manasi Navare >>> wrote: >>> > This is RFC patch for adding a connector link-status property >>> > and

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 10:15 AM, Jani Nikula wrote: > On Wed, 23 Nov 2016, Sean Paul wrote: >> On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: >>> On Tue, Nov 22, 2016 at 09:27:35PM -0500, Sean Paul wrote: On Tue, Nov 22, 2016 at 8:30 PM, Manasi Navare wrote: > This is

[Intel-gfx] [PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 10:32:44AM -0500, Sean Paul wrote: > On Wed, Nov 23, 2016 at 10:15 AM, Jani Nikula > wrote: > > On Wed, 23 Nov 2016, Sean Paul wrote: > >> On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: > >>> On Tue, Nov 22, 2016 at 09:27:35PM -0500, Sean Paul wrote: > On

[Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state

nee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/b9c14e77/attachment.html>

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, 23 Nov 2016, Sean Paul wrote: > On Wed, Nov 23, 2016 at 10:15 AM, Jani Nikula > wrote: >> On Wed, 23 Nov 2016, Sean Paul wrote: >>> On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: On Tue, Nov 22, 2016 at 09:27:35PM -0500, Sean Paul wrote: > On Tue, Nov 22, 2016 at 8:30

[Intel-gfx] [PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 10:43 AM, Ville Syrjälä wrote: > On Wed, Nov 23, 2016 at 10:32:44AM -0500, Sean Paul wrote: >> On Wed, Nov 23, 2016 at 10:15 AM, Jani Nikula >> wrote: >> > On Wed, 23 Nov 2016, Sean Paul wrote: >> >> On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: >> >>> On Tue,

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 10:52 AM, Jani Nikula wrote: > On Wed, 23 Nov 2016, Sean Paul wrote: >> On Wed, Nov 23, 2016 at 10:15 AM, Jani Nikula >> wrote: >>> On Wed, 23 Nov 2016, Sean Paul wrote: On Wed, Nov 23, 2016 at 3:09 AM, Daniel Vetter wrote: > On Tue, Nov 22, 2016 at 09:27:35PM

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 4:52 PM, Jani Nikula wrote: >> Take the CDN DP driver in rockchip for example (posted yesterday). >> There's a worker in the driver that is responsible for handling >> hpd/extcon events from the USB-C port. Ideally, this worker should >> just be a thin shell around a kms

[Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state

TML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/44a8d443/attachment-0001.html>

[PATCH v3 11/11] drm/tilcdc: Enable frame done irq and functionality for LCDC rev 1

2016-11-22 17:54 GMT+01:00 Jyri Sarha : > We should wait for the last frame to complete before shutting things > down also on LCDC rev 1. > > Signed-off-by: Jyri Sarha > --- > drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 34 +- > drivers/gpu/drm/tilcdc/tilcdc_regs.h |

[RFC PATCH 3/3] staging: remove fbtft

Den 23.11.2016 09:03, skrev Tomi Valkeinen: > Since the fbdev framework is in maintenance mode and all new display > drivers should be made with the DRM framework, remove fbtft from > staging. > > Signed-off-by: Tomi Valkeinen FYI: I'm working on a drm version of fbtft:

[Bug 98834] Screen not refreshed after 1106b2f773ad0611c729b27f4c192a26b43ef1e7

;https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/ce9841c1/attachment-0001.html>

[Bug 98834] Screen not refreshed after 1106b2f773ad0611c729b27f4c192a26b43ef1e7

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/fe7ec713/attachment.html>

[Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state

re receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/d228c910/attachment.html>

[Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state

tps://lists.freedesktop.org/archives/dri-devel/attachments/20161123/dfe12ef7/attachment.html>

[PATCH libdrm v3 0/4] etna_pipe_wait_ns(..)

On 23 November 2016 at 07:26, Christian Gmeiner wrote: > Add an API to pass the timeout value (ns) from pipe->fence_finish(..) > to the kernel. The current API accepts ms and special handling is needed > for PIPE_TIMEOUT_INFINITE. > > The idea is not to break old mesa (out-of-tree) + new libdrm.

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 9:27 AM, Bart Van Assche wrote: > On 11/23/2016 09:13 AM, Logan Gunthorpe wrote: >> >> IMO any memory that has been registered for a P2P transaction should be >> locked from being evicted. So if there's a get_user_pages call it needs >> to be pinned until the put_page. The

[PATCH libdrm v3 0/4] etna_pipe_wait_ns(..)

On Wed, Nov 23, 2016 at 1:18 PM, Emil Velikov wrote: > On 23 November 2016 at 07:26, Christian Gmeiner > wrote: >> Add an API to pass the timeout value (ns) from pipe->fence_finish(..) >> to the kernel. The current API accepts ms and special handling is needed >> for PIPE_TIMEOUT_INFINITE. >>

[PATCH RFC] drm: Add a new connector atomic property for link status

On Wed, Nov 23, 2016 at 11:00:59AM +0100, Daniel Vetter wrote: > On Tue, Nov 22, 2016 at 05:30:21PM -0800, Manasi Navare wrote: > > This is RFC patch for adding a connector link-status property > > and making it atomic by adding it to the drm_connector_state. > > This is to make sure its wired

[Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state

. And if movie is over MCLK is constants again... -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/904bbbcd/attachment.html>

Enabling peer to peer device transactions for PCIe devices

On 2016-11-23 12:27 PM, Bart Van Assche wrote: > On 11/23/2016 09:13 AM, Logan Gunthorpe wrote: >> IMO any memory that has been registered for a P2P transaction should be >> locked from being evicted. So if there's a get_user_pages call it needs >> to be pinned until the put_page. The main issue

Enabling peer to peer device transactions for PCIe devices

On 2016-11-23 02:05 PM, Jason Gunthorpe wrote: > On Wed, Nov 23, 2016 at 10:13:03AM -0700, Logan Gunthorpe wrote: > >> an MR would be very tricky. The MR may be relied upon by another host >> and the kernel would have to inform user-space the MR was invalid then >> user-space would have to tell

[PATCH] drm/doc: Fix links in drm_property.c

One of the functions was missing () to make the autolinks work, unfortunately copy-pasted a few times all over. Cc: Manasi Navare Signed-off-by: Daniel Vetter --- drivers/gpu/drm/drm_property.c | 42 +- 1 file changed, 21 insertions(+), 21 deletions(-)

  1   2   >