25898 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/038d9bb7/attachment-0001.gz>
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>
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>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20161123/025c7e61/attachment.html>
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:
>>> @
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
vbla
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 is
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 +
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 etna_bo_cpu_prep(st
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
--- a/etnaviv/etnaviv_pipe
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
@@ -189,15
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 10:3
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 William
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
> > > wai
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
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:
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 -
drivers/staging
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 -
drivers/staging/Makef
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 -
drivers/staging/Kc
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 ju
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 dr
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 the
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.
>>
>>
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 missin
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
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 Tue
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 the
sc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/9ff4e52f/attachment.sig>
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 mad
19 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/df060f80/attachment.sig>
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 drm_atomic_connector_ge
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 controller
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 ("drm
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 parame
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 a
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
+++ b/drivers/
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(-)
di
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
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 generi
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 proceedin
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 #0Thread #1Thread #
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 b/Documentation/locking/00-INDEX
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 b/include/linux/ww_mutex.h
index 760399a..fd
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 the wait in
__mutex_lo
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 fun
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
>> >
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 enco
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 enco
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,
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 orde
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 a
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 regist
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 | 1
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 --g
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
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:
> >> > > drm_g
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 [
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 b/drivers
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 a/drivers/bu
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
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 i
tps://lists.freedesktop.org/archives/dri-devel/attachments/20161123/a6aeb622/attachment.html>
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(&lock->base);
> #endif
> - __mutex_fastpath_unlock(&lock->base.count, __mutex_unlock_slowpath);
> + /*
> +
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
add
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 insertion
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 fi
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
---
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: Joonas
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 the
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;"
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(&lock->base);
> > #endif
> > - __mutex_fastpath_un
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 (J
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 @@
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&back-off. Could we perhaps steal something
> from rt mutexes to make it fair&efficient?
rt_mutexes order the waiters by 'priorit
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 drm_conne
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:
>
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
> ---
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
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 RFC
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 Tue,
ssignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/b9c14e77/attachment.html>
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 PM
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,
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
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 ue
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/44a8d443/attachment-0001.html>
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 | 1
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: https://github.com/notro/
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/ce9841c1/attachment-0001.html>
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>
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>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20161123/dfe12ef7/attachment.html>
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. I
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
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.
>>
>>
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 prop
is enable.
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/20161
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 be
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 th
On 23 November 2016 at 18:45, Rob Clark wrote:
> 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 specia
1 - 100 of 151 matches
Mail list logo
