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

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_get_property functions. v3: * Fixed a build error (Jani Saarinen) v2: *

[PATCH] drm/sun4i: Only count TCON endpoints as valid outputs

On Tue, Nov 22, 2016 at 11:37 PM, Maxime Ripard wrote: > Hi, > > On Fri, Nov 18, 2016 at 10:22:40AM +0800, Chen-Yu Tsai wrote: >> On Fri, Nov 18, 2016 at 3:02 AM, Maxime Ripard >> wrote: >> > On Wed, Nov 16, 2016 at 05:37:31PM +0800, Chen-Yu Tsai wrote: >> >> The sun4i DRM driver counts the

[Bug 97942] [IGT] [BYT] /gem_mmap_gtt subtest basic-wc fails due to Test assertion failure

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

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

Hi Emil, 2016-11-23 19:18 GMT+01:00 Emil Velikov : > 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. >> >>

[Bug 97338] Black squares in the Spec Ops: The Line chapter select screen

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/2df793e2/attachment.html>

[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(-)

[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/ba70d83c/attachment.html>

[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>

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

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_get_property functions. v2: * Removed connector->link_status (Daniel

[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:

Enabling peer to peer device transactions for PCIe devices

On 23/11/16 02:55 PM, Jason Gunthorpe wrote: >>> Only ODP hardware allows changing the DMA address on the fly, and it >>> works at the page table level. We do not need special handling for >>> RDMA. >> >> I am aware of ODP but, noted by others, it doesn't provide a general >> solution to the

[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 |

[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.

[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 v3 1/3] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name()

Hi Bartosz, On Wednesday 23 November 2016 04:36 PM, Bartosz Golaszewski wrote: > 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 > --- >

[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>

[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

[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 98834] Screen not refreshed after 1106b2f773ad0611c729b27f4c192a26b43ef1e7

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

[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

[PATCH 1/3] of: base: add support to get machine compatible string

On Wednesday 23 November 2016 05:37 PM, Sudeep Holla wrote: >> So, the if(!of_node_get()) is just an expensive NULL pointer check. I >> think >> it is better to be explicit about it by not using of_node_get/put() at >> all. >> How about: >> > > Are we planning to use this in any time sensitive

[PATCH 1/3] of: base: add support to get machine compatible string

On Wednesday 23 November 2016 03:35 PM, Sudeep Holla wrote: > > > On 23/11/16 07:49, Sekhar Nori wrote: >> On Tuesday 22 November 2016 09:16 PM, Sudeep Holla wrote: >>> Hi Sekhar, >>> >>> On 22/11/16 15:06, Sekhar Nori wrote: Hi Sudeep, On Tuesday 22 November 2016 04:23 PM, Sudeep

[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 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

[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: >

[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 v2] ARM: dts: da850: add the mstpri and ddrctl nodes

On 11/23/2016 04:32 PM, Kevin Hilman wrote: > David Lechner writes: > >> On 11/23/2016 04:27 AM, Bartosz Golaszewski wrote: >>> 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

[PATCH v2 2/3] drm/bridge: Add ti-tfp410 DVI transmitter driver

On Thu, Nov 17, 2016 at 3:45 AM, Laurent Pinchart wrote: > Hi Jyri, > > On Wednesday 16 Nov 2016 16:39:28 Jyri Sarha wrote: >> On 11/16/16 15:33, Rob Herring wrote: >> >> +Optional properties >> >> >> >>> + - reg: I2C address. If and only if present the driver node > > I assume you meant device

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

On Wed, Nov 23, 2016 at 2:23 PM, Daniel Vetter wrote: > One of the functions was missing () to make the autolinks work, > unfortunately copy-pasted a few times all over. > > Cc: Manasi Navare Reviewed-by: Sean Paul > Signed-off-by: Daniel Vetter > --- > drivers/gpu/drm/drm_property.c | 42

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:42:12PM -0800, Dan Williams wrote: > > The crucial part for this discussion is the ability to fence and block > > DMA for a specific range. This is the hardware capability that lets > > page migration happen: fence DMA, migrate page, update page > > table in HCA, unblock

[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 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 08/37] drm/arcpgu: Add local 'fb' variables

Hi Ville, On Fri, 2016-11-18 at 21:52 +0200, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > Add a local 'fb' variable to a few places to get rid of the > 'crtc->primary->fb' stuff. Looks neater and helps me with my ppor > coccinelle skills later. > > Cc: Alexey Brodkin >

[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 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 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

[pull] radeon and amdgpu drm-next-4.10

Hi Dave, More features for 4.10. Highlights: - lots of code cleanup - lots of bug fixes - expose rpm based fan info via hwmon - lots of clock and powergating fixes - SI register header cleanup and conversion to common format used by newer asics The following changes since commit

[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 1/5] drm/i915: Add support for DP link training compliance

On Wed, Nov 23, 2016 at 03:07:30PM +0200, Jani Nikula wrote: > 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 > >

[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] 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] 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 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 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 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 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 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,

[pull] radeon and amdgpu drm-fixes-4.9

Hi Dave, Just a regression fix for certain older PX systems using d3cold. The following changes since commit da7800a88c5a3b798f763d6f9f343e9a49860c4f: drm/amd/powerplay: avoid out of bounds access on array ps. (2016-11-16 14:26:17 -0500) are available in the git repository at:

[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

Enabling peer to peer device transactions for PCIe devices

. > > As Dan suggested, maybe we need to do both. Some kind of fix for > get_user_pages() for smaller mappings (eg ZONE_DEVICE) and a mandatory > API conversion to get_user_dma_sg() for other cases? > > Jason Sincerely yours, Serguei Sagalovitch -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161123/eaeeec3a/attachment.html>

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:11:29PM -0700, Logan Gunthorpe wrote: > > As I said, there is no possible special handling. Standard IB hardware > > does not support changing the DMA address once a MR is created. Forget > > about doing that. > > Yeah, that's essentially the point I was trying to make.

[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 3/3] drm/msm: gpu Add new gpu register read/write functions

On Wed, Nov 23, 2016 at 2:34 PM, Stephen Boyd wrote: > On 11/22/2016 07:47 AM, Jordan Crouse wrote: >> Add some new functions to manipulate GPU registers. gpu_read64 and >> gpu_write64 can read/write a 64 bit value to two 32 bit registers. >> For 4XX and older these are normally perfcounter

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

On Wed, Nov 23, 2016 at 2:22 PM, Emil Velikov wrote: > 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

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 1:55 PM, Jason Gunthorpe wrote: > On Wed, Nov 23, 2016 at 02:11:29PM -0700, Logan Gunthorpe wrote: >> > As I said, there is no possible special handling. Standard IB hardware >> > does not support changing the DMA address once a MR is created. Forget >> > about doing that.

[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 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 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes

Op 23-11-16 om 14:11 schreef Daniel Vetter: > 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

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

David Lechner writes: > On 11/23/2016 04:27 AM, Bartosz Golaszewski wrote: >> 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.

Enabling peer to peer device transactions for PCIe devices

On 2016-11-23 03:51 AM, Christian König wrote: > 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: >

[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 |

Enabling peer to peer device transactions for PCIe devices

On 2016-11-23 02:12 PM, Jason Gunthorpe wrote: > On Wed, Nov 23, 2016 at 10:40:47AM -0800, Dan Williams wrote: > >> I don't think that was designed for the case where the backing memory >> is a special/static physical address range rather than anonymous >> "System RAM", right? > The hardware

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

[RFC PATCH 3/3] staging: remove fbtft

On Wed, Nov 23, 2016 at 2:03 AM, Tomi Valkeinen wrote: > 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 I'd request that fbtft please be kept in staging until a

[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

Enabling peer to peer device transactions for PCIe devices

On 23/11/16 01:33 PM, Jason Gunthorpe wrote: > On Wed, Nov 23, 2016 at 02:58:38PM -0500, Serguei Sagalovitch wrote: > >>We do not want to have "highly" dynamic translation due to >>performance cost. We need to support "overcommit" but would >>like to minimize impact. To support

[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 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 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

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

[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 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 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

[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: > 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 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 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: > >> > >

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:58:38PM -0500, Serguei Sagalovitch wrote: >We do not want to have "highly" dynamic translation due to >performance cost. We need to support "overcommit" but would >like to minimize impact. To support RDMA MRs for GPU/VRAM/PCIe >device memory (which is

[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 1/3] of: base: add support to get machine compatible string

On Tuesday 22 November 2016 09:16 PM, Sudeep Holla wrote: > Hi Sekhar, > > On 22/11/16 15:06, Sekhar Nori wrote: >> Hi Sudeep, >> >> On Tuesday 22 November 2016 04:23 PM, Sudeep Holla wrote: >>> >>> >>> On 22/11/16 10:41, Bartosz Golaszewski wrote: Add a function allowing to retrieve the

[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, 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

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:14:40PM -0500, Serguei Sagalovitch wrote: > > On 2016-11-23 02:05 PM, Jason Gunthorpe wrote: > >As Bart says, it would be best to be combined with something like > >Mellanox's ODP MRs, which allows a page to be evicted and then trigger > >a CPU interrupt if a DMA is

[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 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 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 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 1/3] of: base: add support to get machine compatible string

On 23/11/16 12:13, Sekhar Nori wrote: > On Wednesday 23 November 2016 05:37 PM, Sudeep Holla wrote: >>> So, the if(!of_node_get()) is just an expensive NULL pointer check. I >>> think >>> it is better to be explicit about it by not using of_node_get/put() at >>> all. >>> How about: >>> >> >> Are

Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 10:40:47AM -0800, Dan Williams wrote: > I don't think that was designed for the case where the backing memory > is a special/static physical address range rather than anonymous > "System RAM", right? The hardware doesn't care where the memory is. ODP is just a generic

[PATCH 1/3] of: base: add support to get machine compatible string

On 23/11/16 11:47, Sekhar Nori wrote: > On Wednesday 23 November 2016 03:35 PM, Sudeep Holla wrote: >> >> >> On 23/11/16 07:49, Sekhar Nori wrote: >>> On Tuesday 22 November 2016 09:16 PM, Sudeep Holla wrote: Hi Sekhar, On 22/11/16 15:06, Sekhar Nori wrote: > Hi Sudeep, >

[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 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

Enabling peer to peer device transactions for PCIe devices

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 the remote application. As Bart says, it would be best

[PATCH 3/3] drm/msm: gpu Add new gpu register read/write functions

On 11/23/2016 11:46 AM, Rob Clark wrote: > On Wed, Nov 23, 2016 at 2:34 PM, Stephen Boyd wrote: >> On 11/22/2016 07:47 AM, Jordan Crouse wrote: >>> Add some new functions to manipulate GPU registers. gpu_read64 and >>> gpu_write64 can read/write a 64 bit value to two 32 bit registers. >>> For

[PATCH 3/3] drm/msm: gpu Add new gpu register read/write functions

On 11/22/2016 07:47 AM, Jordan Crouse wrote: > Add some new functions to manipulate GPU registers. gpu_read64 and > gpu_write64 can read/write a 64 bit value to two 32 bit registers. > For 4XX and older these are normally perfcounter registers, but > future targets will use 64 bit addressing so

[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

  1   2   >