[Intel-gfx] [PATCH v3 1/2] drm: Wrap the check for atomic_commit implementation

2016-12-23 Thread kbuild test robot
ytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161223/1c13aad4/attachment-0001.gz>

[git pull] drm fixes for 4.10-rc1

2016-12-23 Thread Dave Airlie
Hi Linus, Some fixes came in while I was out, mostly intel and amdgpu ones, with one ast fix. If you can land them before -rc1 it would be good but I don't mind if they don't. Dave. The following changes since commit 50f6584e4c626b8fa39edb66f33fec27bab3996c: Merge tag 'leds_for_4.10_email_upd

[Intel-gfx] [PATCH v3 1/3] drm: Create new structure for HDMI info

2016-12-23 Thread Sharma, Shashank
Regards Shashank On 12/22/2016 5:26 PM, Ville Syrjälä wrote: > On Thu, Dec 22, 2016 at 10:02:26AM +, Jose Abreu wrote: >> Hi Shashank, >> >> >> On 21-12-2016 15:29, Shashank Sharma wrote: >> >> [snip] >> >>> + >>> + /** >>> +* @edid_yuv420_dc_modes: bpc for deep color yuv420 encoding

drm_mm crash with multi threads

2016-12-23 Thread Mark yao
An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161223/9a90c85e/attachment.html>

[PATCH 1/2] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

2016-12-23 Thread hoegeun kwon
On 12/20/2016 03:55 AM, Rob Herring wrote: > On Wed, Dec 14, 2016 at 03:04:04PM +0900, Hoegeun Kwon wrote: >> This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel >> driver. This panel has 1440x2560 resolution in 5.7-inch physical >> panel in the TM2 device. >> >> Signed-off-by: Donghwa

[Bug 96488] [r600g]OpenCL driver causes segfault in ImageMagick's Histogram kernel

2016-12-23 Thread bugzilla-dae...@freedesktop.org
part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161223/0fbbb327/attachment-0001.html>

[Intel-gfx] drm_mm crash with multi threads

2016-12-23 Thread Rob Clark
On Thu, Dec 22, 2016 at 11:07 PM, Mark yao wrote: > Hi Chris Wilson > > We port drm_mm to my internal kernel, with high load test, found following > crash: > > [49451.856244] > == > [49451.856350] BUG: KASAN: wild-memory-access on add

[Intel-gfx] drm_mm crash with multi threads

2016-12-23 Thread Mark yao
On 2016年12月23日 13:57, Rob Clark wrote: > On Thu, Dec 22, 2016 at 11:07 PM, Mark yao wrote: >> Hi Chris Wilson >> >> We port drm_mm to my internal kernel, with high load test, found following >> crash: >> >> [49451.856244] >> ==

[PATCH] drm/i915: check if execlist_port is empty before using its content

2016-12-23 Thread Jani Nikula
On Fri, 23 Dec 2016, changbin.du at intel.com wrote: > From: "Du, Changbin" > > This patch fix a crash in function reset_common_ring. In this case, > the port[0].request is null when reset the render ring, so a null > dereference exception is raised. We need to check execlist_port status > first.

[Intel-gfx] [PATCH] drm/i915: check if execlist_port is empty before using its content

2016-12-23 Thread Chris Wilson
On Fri, Dec 23, 2016 at 01:46:36PM +0800, changbin.du at intel.com wrote: > From: "Du, Changbin" > > This patch fix a crash in function reset_common_ring. In this case, > the port[0].request is null when reset the render ring, so a null > dereference exception is raised. We need to check execlist

[Bug 190971] New: amdgpu (on Kabini) fails to resume, atombios stuck executing BA98

2016-12-23 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=190971 Bug ID: 190971 Summary: amdgpu (on Kabini) fails to resume, atombios stuck executing BA98 Product: Drivers Version: 2.5 Kernel Version: 4.9 Hardware: x86-64

[PATCH v3 05/12] locking/ww_mutex: Remove the __ww_mutex_lock inline wrappers

2016-12-23 Thread Peter Zijlstra
On Wed, Dec 21, 2016 at 07:46:33PM +0100, Nicolai Hähnle wrote: > diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h > index a5960e5..b2eaaab 100644 > --- a/include/linux/ww_mutex.h > +++ b/include/linux/ww_mutex.h > @@ -186,11 +186,6 @@ static inline void ww_acquire_fini(struct ww_a

[Bug 99191] Weird blocky green stuff rendered in High Fidelity

2016-12-23 Thread bugzilla-dae...@freedesktop.org
tps://lists.freedesktop.org/archives/dri-devel/attachments/20161223/675180dc/attachment-0001.html>

[PATCH v4 3/5] drm: bridge: Link encoder and bridge in core code

2016-12-23 Thread Philipp Zabel
Am Freitag, den 16.12.2016, 14:05 +0530 schrieb Archit Taneja: > Hi, > > On 12/14/2016 03:29 PM, Laurent Pinchart wrote: > > Instead of linking encoders and bridges in every driver (and getting it > > wrong half of the time, as many drivers forget to set the drm_bridge > > encoder pointer), do so

[PATCH v3 05/12] locking/ww_mutex: Remove the __ww_mutex_lock inline wrappers

2016-12-23 Thread Nicolai Hähnle
On 23.12.2016 11:48, Peter Zijlstra wrote: > On Wed, Dec 21, 2016 at 07:46:33PM +0100, Nicolai Hähnle wrote: >> diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h >> index a5960e5..b2eaaab 100644 >> --- a/include/linux/ww_mutex.h >> +++ b/include/linux/ww_mutex.h >> @@ -186,11 +186,6

[PATCH v3 05/12] locking/ww_mutex: Remove the __ww_mutex_lock inline wrappers

2016-12-23 Thread Peter Zijlstra
On Fri, Dec 23, 2016 at 12:16:03PM +0100, Nicolai Hähnle wrote: > >For some reason this patch appears to make lib/locking-selftest.c really > >unhappy. > > > >I get endless streams of: > > > >../lib/locking-selftest.c: In function ‘ww_test_fail_acquire’: > >../lib/locking-selftest.c:1141:6: e

[Intel-gfx] [PATCH 1/2] drm : adds Y-coordinate and Colorimetry Format

2016-12-23 Thread Jani Nikula
On Thu, 22 Dec 2016, vathsala nagaraju wrote: > PSR2 vsc revision number hb2( as per table 6-11)is updated to > 4 or 5 based on Y cordinate and Colorimetry Format as below > 04h = 3D stereo + PSR/PSR2 + Y-coordinate. > 05h = -3D stereo- + PSR/PSR2 + Y-coordinate + Pixel Encoding/Colorimetry > Form

[PATCH 06/18] drm/i915/dsi: Move disable pll call outside of clear_device_ready()

2016-12-23 Thread Jani Nikula
On Thu, 01 Dec 2016, Hans de Goede wrote: > On enable intel_dsi_enable() directly calls intel_enable_dsi_pll(), > make intel_dsi_disable() also directly call intel_disable_dsi_pll(), > rather then hiding the call in intel_dsi_clear_device_ready(), > no functional changes. > > Signed-off-by: Hans d

[git pull] drm fixes for 4.10-rc1

2016-12-23 Thread Daniel Vetter
On Fri, Dec 23, 2016 at 2:59 AM, Dave Airlie wrote: > Hi Linus, > > Some fixes came in while I was out, mostly intel and amdgpu ones, > with one ast fix. If you can land them before -rc1 it would be good > but I don't mind if they don't. This should also shut up the WARN_ON(!intel_dp->lane_count)

[Bug 96488] [r600g]OpenCL driver causes segfault in ImageMagick's Histogram kernel

2016-12-23 Thread bugzilla-dae...@freedesktop.org
... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161223/4dd7fd40/attachment.html>

[Intel-gfx] [PATCH 1/2] drm : adds Y-coordinate and Colorimetry Format

2016-12-23 Thread Jani Nikula
On Fri, 23 Dec 2016, "Nagaraju, Vathsala" wrote: > In DP V1.3 spec , Table 2-149 , page number-374 , for Register 0x2210 > , bit 7:4 is reserved. See DP 1.4. BR, Jani. > > -Original Message- > From: Jani Nikula [mailto:jani.nikula at linux.intel.com] > Sent: Friday, December 23, 201

[PATCH libdrm 1/2] xf86drm: Fix indentation

2016-12-23 Thread Thierry Reding
From: Thierry Reding libdrm uses spaces for indentation. Fix the two inconsistent lines in this file. Signed-off-by: Thierry Reding --- xf86drm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xf86drm.c b/xf86drm.c index b5eeeb090ecb..ac59bf513d6c 100644 --- a/xf86drm.

[PATCH libdrm 2/2] Add .editorconfig

2016-12-23 Thread Thierry Reding
From: Thierry Reding This encodes the indentation style for libdrm and can be used with various editors. See http://editorconfig.org for instructions. Signed-off-by: Thierry Reding --- .editorconfig | 19 +++ 1 file changed, 19 insertions(+) create mode 100644 .editorconfig d

[PATCH libdrm 0/3] xf86drm: Add USB, platform and host1x bus support

2016-12-23 Thread Thierry Reding
From: Thierry Reding Hi, This series enables support for USB, platform and host1x busses in the drmDevice infrastructure. The goal is to make use of these in Mesa for PRIME support (via the DRI_PRIME environment variable) for devices on one of these busses. I'll be sending out Mesa patches for

[PATCH libdrm 1/3] xf86drm: Factor out drmDeviceAlloc()

2016-12-23 Thread Thierry Reding
From: Thierry Reding Subsequent patches will add support for other bus types to drmDevice and they will duplicate a lot of the code to allocate a drmDevice. Factor out the common code so it can be reused. Signed-off-by: Thierry Reding --- xf86drm.c | 78

[PATCH libdrm 3/3] xf86drm: Add platform and host1x bus support

2016-12-23 Thread Thierry Reding
From: Thierry Reding ARM SoCs usually have their DRM/KMS devices on the platform bus, so add support for that to enable these devices to be used with the drmDevice infrastructure. NVIDIA Tegra SoCs have an additional level in the hierarchy and DRM/KMS devices can also be on the host1x bus. This

[PATCH libdrm 2/3] xf86drm: Add USB support

2016-12-23 Thread Thierry Reding
Allow DRM/KMS devices hosted on USB to be detected by the drmDevice infrastructure. Signed-off-by: Thierry Reding --- Note that this is completely untested because I don't have a UDL device for testing. I'm fairly confident that this will work, though, and it'd be nice to include it before the ne

[Bug 99089] Random screen lockups

2016-12-23 Thread bugzilla-dae...@freedesktop.org
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/20161223/fff054cb/attachment.html>

Implementing Miracast

2016-12-23 Thread norbert
Hello, about a year ago there was a discussion about Implementing Miracast on this list: https://lists.freedesktop.org/archives/dri-devel/2015-December/096035.html Since then I could not find further information about that topic there. So maybe someone can answer this question: Is that implement

[PATCH 1/2] drm : adds Y-coordinate and Colorimetry Format

2016-12-23 Thread vathsala nagaraju
PSR2 vsc revision number hb2( as per table 6-11)is updated to 4 or 5 based on Y cordinate and Colorimetry Format as below 04h = 3D stereo + PSR/PSR2 + Y-coordinate. 05h = -3D stereo- + PSR/PSR2 + Y-coordinate + Pixel Encoding/Colorimetry Format indication. A DP Source device is allowed to indicate

[Intel-gfx] [PATCH 1/2] drm : adds Y-coordinate and Colorimetry Format

2016-12-23 Thread Nagaraju, Vathsala
In DP V1.3 spec , Table 2-149 , page number-374 , for Register 0x2210 , bit 7:4 is reserved. -Original Message- From: Jani Nikula [mailto:jani.nik...@linux.intel.com] Sent: Friday, December 23, 2016 6:57 PM To: Nagaraju, Vathsala ; dri-devel at lists.freedesktop.org; intel-gfx a

[PATCH v4 2/2] drm: Get atomic property value even if DRIVER_ATOMIC is not set

2016-12-23 Thread Dhinakaran Pandiyan
i915 does not set DRIVER_ATOMIC by default yet but uses atomic_check and atomic_commit. drm_object_property_get_value() does not read the correct value of atomic properties if DRIVER_ATOMIC is not set. Checking whether the driver uses atomic modeset is a better check instead as the property values

[PATCH] drm/i915: check if execlist_port is empty before using its content

2016-12-23 Thread changbin...@intel.com
From: "Du, Changbin" This patch fix a crash in function reset_common_ring. In this case, the port[0].request is null when reset the render ring, so a null dereference exception is raised. We need to check execlist_port status first. [ 35.748034] BUG: unable to handle kernel NULL pointer derefe

[PATCH 2/2] drm/i915/psr: program vsc header for psr2

2016-12-23 Thread vathsala nagaraju
Function hsw_psr_setup handles vsc header setup for psr1 and skl_psr_setup_vsc handles vsc header setup for psr2. Setup VSC header in function skl_psr_setup_vsc for psr2 support, as per edp 1.4 spec, table 6-11:VSC SDP HEADER Extension for psr2 operation. v2: (Jani) - Initialize variables to 0 -

[PATCH v4 1/2] drm: Wrap the check for atomic_commit implementation

2016-12-23 Thread Dhinakaran Pandiyan
This check is useful for drivers that do not have DRIVER_ATOMIC set but have atomic modesetting internally implemented. Wrap the check into a function since this is used in many places and as a bonus, the function name helps to document what the check is for. v2: Change return type to bool (Ville)

[RFC 00/10] implement alternative and much simpler id allocator

2016-12-23 Thread Rasmus Villemoes
On Sat, Dec 17 2016, Matthew Wilcox wrote: > From: Matthew Wilcox >> From: Rasmus Villemoes [mailto:linux at rasmusvillemoes.dk] >> > This sounds good. I think there may still be a lot of users that never >> > allocate more than a handful of IDAs, making a 128 byte allocation still >> > somewhat

[RFC 00/10] implement alternative and much simpler id allocator

2016-12-23 Thread Matthew Wilcox
From: Rasmus Villemoes [mailto:li...@rasmusvillemoes.dk] > Nice work! A few random comments/questions: > > - It does add some complexity, but I think a few comments would make it > more digestable. I'm open to adding some comments ... I need some time between writing the code and writing the c