[Bug 98690] [nouveau bisected] System freeze when starting X using kernel 4.9-rc1 or later

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98690 Jani Nikula changed: What|Removed |Added QA Contact|intel-gfx-bugs@lists.freede | |sktop.org

[Bug 98690] [nouveau bisected] System freeze when starting X using kernel 4.9-rc1 or later

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98690 Jari Tahvanainen changed: What|Removed |Added Whiteboard|ReadyForDev | Keywords|bisected, regress

[Bug 98690] [nouveau bisected] System freeze when starting X using kernel 4.9-rc1 or later

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98690 Jani Nikula changed: What|Removed |Added QA Contact||xorg-t...@lists.x.org Product|D

Re: [PATCH libdrm v8] amdgpu: move asic id table to a separate file

2017-06-15 Thread Emil Velikov
On 15 June 2017 at 04:16, Michel Dänzer wrote: > On 14/06/17 08:34 PM, Emil Velikov wrote: >> On 13 June 2017 at 10:45, Michel Dänzer wrote: >>> From: Xiaojie Yuan >>> >>> v2: fix an off by one error and leading white spaces >>> v3: use thread safe strtok_r(); initialize len before calling getli

Re: [PATCH libdrm v8] amdgpu: move asic id table to a separate file

2017-06-15 Thread Michel Dänzer
On 15/06/17 04:42 PM, Emil Velikov wrote: > On 15 June 2017 at 04:16, Michel Dänzer wrote: >> On 14/06/17 08:34 PM, Emil Velikov wrote: >> >>> Personally I would not have bothered with the table_max_size thing >> >> It seemed silly to reallocate the memory in the default case where the >> amdgpu.i

[PATCH 4/6] v4l: vsp1: Add pipe index argument to the VSP-DU API

2017-06-15 Thread Laurent Pinchart
In the H3 ES2.0 SoC the VSP2-DL instance has two connections to DU channels that need to be configured independently. Extend the VSP-DU API with a pipeline index to identify which pipeline the caller wants to operate on. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_vsp.c

[Bug 101442] Piglit shaders@ssa@fs-if-def-else-break fails with sb but passes with R600_DEBUG=nosb

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101442 Bug ID: 101442 Summary: Piglit shaders@ssa@fs-if-def-else-break fails with sb but passes with R600_DEBUG=nosb Product: Mesa Version: git Hardware: Other OS

[Bug 101442] Piglit shaders@ssa@fs-if-def-else-break fails with sb but passes with R600_DEBUG=nosb

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101442 --- Comment #1 from Gert Wollny --- Also shaders@ssa@fs-while-loop-rotate-value fails with sb enabled, but passes with nosb. -- You are receiving this mail because: You are the assignee for the bug._

Re: [PATCH] drm: atmel-hlcdc: sama5d4 does not have overlay2

2017-06-15 Thread Boris Brezillon
On Thu, 15 Jun 2017 11:24:13 +0200 Peter Rosin wrote: > From: Peter Rosin > > Remove the layer. Duh. It was present in the datasheet I had. Just downloaded last version of the datasheet and it's no longer there. Nicolas, there's still a reference to OVR2 in the block diagram (Section "31.3 Bl

[PATCH v2 4/4] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

2017-06-15 Thread Hoegeun Kwon
The display-timing and delay are included in the panel driver. So it should be removed in dts. Signed-off-by: Hoegeun Kwon --- arch/arm/boot/dts/exynos3250-rinato.dts | 22 -- 1 file changed, 22 deletions(-) diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/bo

[PATCH v2 0/4] Add support for the s6e63j0x03 panel on Rinato board

2017-06-15 Thread Hoegeun Kwon
Hi all, The purpose of this patch is add support for s6e63j0x03 AMOLED panel on the rinato board(Samsung Galaxy Gear 2). Changes for V2: - Added the interface info in binding document. - Added Reviewed-by: Andrzej Hajda (1/3 patch). - Added Acked-by: Rob Herring (1/3 patch). - Fixed the tristat

[PATCH v2 3/4] ARM: dts: exynos: Fix the active of reset gpios from rinato dts

2017-06-15 Thread Hoegeun Kwon
This reset gpios is active low, therefore fix from active high to low. Signed-off-by: Hoegeun Kwon --- arch/arm/boot/dts/exynos3250-rinato.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos3250-rinato.dts in

[PATCH v2 1/4] dt-bindings: Add support for samsung s6e63j0x03 panel binding

2017-06-15 Thread Hoegeun Kwon
The Samsung s6e63j0x03 is a 1.63" 320x320 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Hoegeun Kwon Reviewed-by: Andrzej Hajda Acked-by: Rob Herring --- .../bindings/display/panel/samsung,s6e63j0x03.txt | 24 ++ 1 file changed, 24 insertions(+) create

[PATCH v2 2/4] drm/panel: Add support for s6e63j0x03 panel driver

2017-06-15 Thread Hoegeun Kwon
This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63" physical panel. This panel is used in Samsung Galaxy Gear 2. Signed-off-by: Inki Dae Signed-off-by: Hyungwon Hwang Signed-off-by: Hoegeun

Re: Color lookup support for the atmel-hlcdc driver

2017-06-15 Thread Boris Brezillon
On Thu, 15 Jun 2017 11:54:29 +0200 Peter Rosin wrote: > On 2017-06-13 17:30, Boris Brezillon wrote: > > Hi Peter, > > > > On Tue, 13 Jun 2017 16:34:25 +0200 > > Peter Rosin wrote: > > > >> Hi! > >> > >> I need color lookup support for the atmel-hlcdc driver, and had a peek > >> at the code.

Re: [PATCH] drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-15 Thread Chris Wilson
Quoting Rob Clark (2017-06-14 17:49:02) > On Tue, Jun 13, 2017 at 6:52 PM, Sushmita Susheelendra > wrote: > > Buffer object specific resources like pages, domains, sg list > > need not be protected with struct_mutex. They can be protected > > with a buffer object level lock. This simplifies lockin

[PATCH] drm: Reduce scope of 'state' variable

2017-06-15 Thread Dawid Kurek
Smaller scope reduces visibility of variable and makes usage of uninitialized variable less possible. --- drivers/gpu/drm/drm_atomic.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c index f32506a..ea5a9a7 100644

Re: [PATCH] drm: Reduce scope of 'state' variable

2017-06-15 Thread Jani Nikula
On Thu, 15 Jun 2017, Dawid Kurek wrote: > Smaller scope reduces visibility of variable and makes usage of > uninitialized variable less possible. > --- > drivers/gpu/drm/drm_atomic.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/drm_atomic.c b/drive

Re: Color lookup support for the atmel-hlcdc driver

2017-06-15 Thread Boris Brezillon
On Thu, 15 Jun 2017 13:47:35 +0200 Peter Rosin wrote: > On 2017-06-15 12:15, Boris Brezillon wrote: > > On Thu, 15 Jun 2017 11:54:29 +0200 > > Peter Rosin wrote: > > > >> On 2017-06-13 17:30, Boris Brezillon wrote: > >>> Hi Peter, > >>> > >>> On Tue, 13 Jun 2017 16:34:25 +0200 > >>> Peter R

Re: [PATCH] gpu: host1x: Fix error handling

2017-06-15 Thread Thierry Reding
On Mon, Apr 10, 2017 at 10:29:22PM +0200, Christophe JAILLET wrote: > If 'devm_reset_control_get' returns an error, then we erroneously return > success because error code is taken from 'host->clk' instead of > 'host->rst'. > > Fixes: b386c6b73ac6 ("gpu: host1x: Support module reset") > > Signed

Re: [PATCH v3 01/20] drm/tegra: Fix lockup on a use of staging API

2017-06-15 Thread Thierry Reding
On Thu, Jun 15, 2017 at 02:18:24AM +0300, Dmitry Osipenko wrote: > Commit bdd2f9cd ("Don't leak kernel pointer to userspace") added a mutex > around staging IOCTL's, some of those mutexes are taken twice. > > Fixes: bdd2f9cd10eb ("drm/tegra: Don't leak kernel pointer to userspace") > Signed-off-by

Re: [PATCH v3 02/20] drm/tegra: Correct idr_alloc() minimum id

2017-06-15 Thread Thierry Reding
On Thu, Jun 15, 2017 at 02:18:25AM +0300, Dmitry Osipenko wrote: > The client ID 0 is reserved by the host1x/cdma to mark the timeout timer > work as already been scheduled and context ID is used as the clients one. > This fixes spurious CDMA timeouts. > > Fixes: bdd2f9cd10eb ("drm/tegra: Don't le

Re: [PATCH 10/37] drm/doc: vblank cleanup

2017-06-15 Thread Thierry Reding
On Wed, May 24, 2017 at 04:51:45PM +0200, Daniel Vetter wrote: [...] > -Resources allocated by :c:func:`drm_vblank_init()` must be freed > -with a call to :c:func:`drm_vblank_cleanup()` in the driver unload > -operation handler. I think perhaps this is the reason why this was cargo-culted. It's co

Re: [PATCH 33/37] drm/tegra: Drop drm_vblank_cleanup

2017-06-15 Thread Thierry Reding
On Wed, May 24, 2017 at 04:52:08PM +0200, Daniel Vetter wrote: > Again, doesn't seem to serve a purpose. > > Cc: Thierry Reding > Signed-off-by: Daniel Vetter > --- > drivers/gpu/drm/tegra/drm.c | 5 + > 1 file changed, 1 insertion(+), 4 deletions(-) I'm assuming that you want to apply the

Re: [Intel-gfx] [PATCH][drm-next] drm/i915/cnl: make function cnl_ddi_dp_set_dpll_hw_state static

2017-06-15 Thread Ville Syrjälä
On Wed, Jun 14, 2017 at 02:03:05PM +0100, Tvrtko Ursulin wrote: > > On 13/06/2017 14:47, Colin King wrote: > > From: Colin Ian King > > > > The function cnl_ddi_dp_set_dpll_hw_state does not need to be in global > > scope, so make it static. > > > > Cleans up sparse warning: > > "symbol 'cnl_dd

[PATCH] fixup! drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-15 Thread Rob Clark
--- This is roughly based on Chris's suggestion, in particular the part about using mutex_lock_nested(). It's not *exactly* the same, in particular msm_obj->lock protects a bit more than just backing store and we don't currently track a pin_count. (Instead we currently keep pages pinned until the

Re: [PATCH v3 02/14] drm/edid: Complete CEA modedb(VIC 1-107)

2017-06-15 Thread Ville Syrjälä
On Wed, Jun 14, 2017 at 11:17:33PM +0530, Shashank Sharma wrote: > CEA-861-F specs defines new video modes to be used with > HDMI 2.0 EDIDs. The VIC range has been extended from 1-64 to > 1-107. > > Our existing CEA modedb contains only 64 modes (VIC=1 to VIC=64). Now > to be able to parse new CEA

Re: [PATCH v3 02/14] drm/edid: Complete CEA modedb(VIC 1-107)

2017-06-15 Thread Sharma, Shashank
Regards Shashank On 6/15/2017 6:59 PM, Ville Syrjälä wrote: On Wed, Jun 14, 2017 at 11:17:33PM +0530, Shashank Sharma wrote: CEA-861-F specs defines new video modes to be used with HDMI 2.0 EDIDs. The VIC range has been extended from 1-64 to 1-107. Our existing CEA modedb contains only 64 mo

Re: [PATCH v3 00/20] Tegra DRM fixes

2017-06-15 Thread Thierry Reding
On Thu, Jun 15, 2017 at 02:18:23AM +0300, Dmitry Osipenko wrote: > I've dropped the two "GART restoring" patches from the series, postponing > them till a full solution of GART utilization would be ready. > > The "Forbid relocation address shifting in the firewall" patch has been > reverted to v1,

[PATCH v2] drm: Reduce scope of 'state' variable

2017-06-15 Thread Dawid Kurek
Smaller scope reduces visibility of variable and makes usage of uninitialized variable less possible. Changes in v2: - separate declaration and initialization --- drivers/gpu/drm/drm_atomic.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_atomic.

[Bug 194761] amdgpu driver breaks on Oland (SI)

2017-06-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=194761 --- Comment #66 from siyia (eutychio...@gmail.com) --- Regression persists with kernel 4.11.5, but https://bugzilla.kernel.org/attachment.cgi?id=256949 thankfully works and fixes the issue. -- You are receiving this mail because: You are watchin

[PATCH] drm/msm/hdmi: Use bitwise operators when building register values

2017-06-15 Thread Liviu Dudau
Commit c0c0d9eeeb8d ("drm/msm: hdmi audio support") uses logical OR operators to build up a value to be written in the REG_HDMI_AUDIO_INFO0 and REG_HDMI_AUDIO_INFO1 registers when it should have used bitwise operators. Signed-off-by: Liviu Dudau Fixes: c0c0d9eeeb8d ("drm/msm: hdmi audio support")

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #59 from i...@posteo.net --- (In reply to Eike from comment #56) > Sorry to correct you, but my monitor has not been faultier than any other > MG279Q that was bought before 2017. Mine is bought before 2017 and it ain't broken. > BTW

Re: [PATCH] drm: Reduce scope of 'state' variable

2017-06-15 Thread Dawid Kurek
On 15/06/17, Jani Nikula wrote: > On Thu, 15 Jun 2017, Dawid Kurek wrote: > > Smaller scope reduces visibility of variable and makes usage of > > uninitialized variable less possible. > > --- > > drivers/gpu/drm/drm_atomic.c | 5 +++-- > > 1 file changed, 3 insertions(+), 2 deletions(-) > > > > d

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

2017-06-15 Thread Ville Syrjälä
On Wed, Jun 14, 2017 at 11:17:35PM +0530, Shashank Sharma wrote: > HDMI 2.0 spec adds support for YCBCR420 sub-sampled output. > CEA-861-F adds two new blocks in EDID's CEA extension blocks, > to provide information about sink's YCBCR420 output capabilities. > > These blocks are: > > - YCBCR420vd

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #9 from Alex Deucher --- Can you please attach a copy of your vbios? (as root) (use lspci to get the bus id) cd /sys/bus/pci/devices/ echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom -- You are receiving this mail because: You

Re: [PATCH v3 02/14] drm/edid: Complete CEA modedb(VIC 1-107)

2017-06-15 Thread Ville Syrjälä
On Thu, Jun 15, 2017 at 07:01:38PM +0530, Sharma, Shashank wrote: > Regards > > Shashank > > > On 6/15/2017 6:59 PM, Ville Syrjälä wrote: > > On Wed, Jun 14, 2017 at 11:17:33PM +0530, Shashank Sharma wrote: > >> CEA-861-F specs defines new video modes to be used with > >> HDMI 2.0 EDIDs. The VIC

[PULL] drm-intel-fixes

2017-06-15 Thread Jani Nikula
Hi Dave, a GVT fix and a couple of rotation related fixes. BR, Jani. The following changes since commit ef6c4d75e35345f8f362d6754bcd9a28292a897c: drm/i915: fix warning for unused variable (2017-06-08 17:09:44 +0300) are available in the git repository at: git://anongit.freedesktop.org/git

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #10 from Alex Deucher --- Created attachment 131982 --> https://bugs.freedesktop.org/attachment.cgi?id=131982&action=edit possible fix This patch should fix the issue. -- You are receiving this mail because: You are the assignee

Re: [PATCH] drm: Reduce scope of 'state' variable

2017-06-15 Thread Jani Nikula
On Thu, 15 Jun 2017, Dawid Kurek wrote: > On 15/06/17, Jani Nikula wrote: >> Separate declaration and initialization would lead to a cleaner patch >> and result. > > I saw combining declaration and initialization is quite common, i.e. in > drm_atomic file. Personally, I also prefer those in one st

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

2017-06-15 Thread Fabio Estevam
Hi Marek, On Mon, Jun 5, 2017 at 9:08 AM, Marek Vasut wrote: > I'm currently on vacation, try one more time and if it doesn't work out > (which means this trivial list is not really working?), I'll send a PR > sometime mid-month. Tried your suggestion, but it did not work. Could you please con

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #60 from Alex Deucher --- Created attachment 131983 --> https://bugs.freedesktop.org/attachment.cgi?id=131983&action=edit possible fix -- You are receiving this mail because: You are the assignee for the bug.__

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #11 from Carlo Caione --- Yes, that solves the panic issue, thank you. I still have the corruption at boot though, any idea what that can be? -- You are receiving this mail because: You are the assignee for the bug.

[drm-intel:for-linux-next 2/3] drivers/gpu/drm/i915/i915_gem_execbuffer.c:300:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is

2017-06-15 Thread kbuild test robot
tree: git://anongit.freedesktop.org/drm-intel for-linux-next head: 8c45cec48e5871f93e56650f7e476d4ea7174a0e commit: d55495b4dcce2efb4656edfe211eb0bfb27c3387 [2/3] drm/i915: Use vma->exec_entry as our double-entry placeholder coccinelle warnings: (new ones prefixed by >>) >> drivers/gpu/drm/

[PATCH] drm/i915: fix ifnullfree.cocci warnings

2017-06-15 Thread kbuild test robot
drivers/gpu/drm/i915/i915_gem_execbuffer.c:300:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values. NULL check before some freeing functions

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #12 from Carlo Caione --- Also (in case it is useful for the corruption issue): 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 9874 (rev ca) ... 03:00.0 Display controller: Advanced Micro Devices, I

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

2017-06-15 Thread Sharma, Shashank
Regards Shashank On 6/15/2017 8:13 PM, Ville Syrjälä wrote: On Wed, Jun 14, 2017 at 11:17:35PM +0530, Shashank Sharma wrote: HDMI 2.0 spec adds support for YCBCR420 sub-sampled output. CEA-861-F adds two new blocks in EDID's CEA extension blocks, to provide information about sink's YCBCR420 o

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #13 from Alex Deucher --- (In reply to Carlo Caione from comment #12) > Also (in case it is useful for the corruption issue): > not likely related. > 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Devi

[PATCH] dim: allow setup to work with different usernames

2017-06-15 Thread Lionel Landwerlin
If your username on fd.o differs from your local username, you'll run into issues while setting up dim. Let's use regexp to filter remotes so it doesn't fail. Signed-off-by: Lionel Landwerlin --- dim | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/dim b/dim index

[pull] amdgpu drm-next-4.13

2017-06-15 Thread Alex Deucher
Hi Dave, A few more patches for 4.13. Mostly bug fixes and code cleanup. This is on top of my pull request from last week. The following changes since commit b58c11314a1706bf094c489ef5cb28f76478c704: drm/amdgpu: drop deprecated drm_get_pci_dev and drm_put_dev (2017-06-08 10:54:39 -0400) ar

Re: [PATCH] drm/i915: fix ifnullfree.cocci warnings

2017-06-15 Thread Chris Wilson
Quoting kbuild test robot (2017-06-15 16:23:12) > drivers/gpu/drm/i915/i915_gem_execbuffer.c:300:2-7: WARNING: NULL check > before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive > or usb_free_urb is not needed. Maybe consider reorganizing relevant code to > avoid passing

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

2017-06-15 Thread Ville Syrjälä
On Thu, Jun 15, 2017 at 09:05:10PM +0530, Sharma, Shashank wrote: > Regards > > Shashank > > > On 6/15/2017 8:13 PM, Ville Syrjälä wrote: > > On Wed, Jun 14, 2017 at 11:17:35PM +0530, Shashank Sharma wrote: > >> HDMI 2.0 spec adds support for YCBCR420 sub-sampled output. > >> CEA-861-F adds two

Re: [PATCH] drm: Remove duplicate forward declaration

2017-06-15 Thread Sean Paul
On Wed, Jun 14, 2017 at 11:35:18PM +0200, Dawid Kurek wrote: > Forward declarations in C are great but I'm pretty sure one is enough. Applied to drm-misc-next Thanks, Sean > > Signed-off-by: Dawid Kurek > --- > include/drm/drm_connector.h | 2 -- > 1 file changed, 2 deletions(-) > > diff --

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #14 from Carlo Caione --- > not likely related. Alright, any hint where to start looking? As I said before it looks like the visual corruption (this https://pasteboard.co/qrC9mh4p.jpg) at boot starts at [drm] amdgpu atom DIG backli

[tegra-drm:drm/tegra/for-next 2/20] htmldocs: drivers/gpu/host1x/bus.c:50: warning: Excess function parameter 'driver' description in 'host1x_subdev_add'

2017-06-15 Thread kbuild test robot
tree: git://anongit.freedesktop.org/tegra/linux.git drm/tegra/for-next head: 43240bbd871e2c8f89584d369278a3d18680d9ea commit: fa6d095eb23a8b1aae78d221879032497f6e457f [2/20] drm/tegra: Add driver documentation reproduce: make htmldocs All warnings (new ones prefixed by >>): WARNING: conve

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

2017-06-15 Thread Sharma, Shashank
Regards Shashank On 6/15/2017 9:42 PM, Ville Syrjälä wrote: On Thu, Jun 15, 2017 at 09:05:10PM +0530, Sharma, Shashank wrote: Regards Shashank On 6/15/2017 8:13 PM, Ville Syrjälä wrote: On Wed, Jun 14, 2017 at 11:17:35PM +0530, Shashank Sharma wrote: HDMI 2.0 spec adds support for YCBCR4

Re: [PATCH] drm: Reduce scope of 'state' variable

2017-06-15 Thread Dawid Kurek
On 15/06/17, Jani Nikula wrote: > On Thu, 15 Jun 2017, Dawid Kurek wrote: > > On 15/06/17, Jani Nikula wrote: > >> Separate declaration and initialization would lead to a cleaner patch > >> and result. > > > > I saw combining declaration and initialization is quite common, i.e. in > > drm_atomic f

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

2017-06-15 Thread Ville Syrjälä
On Thu, Jun 15, 2017 at 10:18:40PM +0530, Sharma, Shashank wrote: > Regards > > Shashank > > > On 6/15/2017 9:42 PM, Ville Syrjälä wrote: > > On Thu, Jun 15, 2017 at 09:05:10PM +0530, Sharma, Shashank wrote: > >> Regards > >> > >> Shashank > >> > >> > >> On 6/15/2017 8:13 PM, Ville Syrjälä wrote

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #15 from Alex Deucher --- (In reply to Carlo Caione from comment #14) > > Fortunately it disappears after ~2 seconds when plymouth kicks in. My > impression is that the visual corruption is triggered again when > interpreting some a

Re: [PATCH v3 04/14] drm/edid: parse YCBCR 420 videomodes from EDID

2017-06-15 Thread Sharma, Shashank
Yes, we should check for features, not for some standard version that implements some/all of those features. But not convinced we need any featur flags for the other things you listed. Aren't we already doing all those things anyway? Yep, I realized you will come back with this point, while typi

Re: [PATCH 1/1] drm/mgag200: Fix to always set HiPri for G200e4 V2

2017-06-15 Thread Sean Paul
On Wed, Jun 14, 2017 at 10:39:42AM -0400, mathieu.larou...@matrox.com wrote: > From: Mathieu Larouche > > - Changed the HiPri value for G200e4 to always be 0. > - Added Bandwith limitation to block resolution above 1920x1200x60Hz > > Signed-off-by: Mathieu Larouche Applied to -misc-fixes w

Re: [PATCH v2] drm: Reduce scope of 'state' variable

2017-06-15 Thread Sean Paul
On Thu, Jun 15, 2017 at 04:04:36PM +0200, Dawid Kurek wrote: > Smaller scope reduces visibility of variable and makes usage of > uninitialized variable less possible. > > Changes in v2: > - separate declaration and initialization Your patch is missing Signed-off-by tag Sean > --- > drive

Re: [PATCH v2] drm: Reduce scope of 'state' variable

2017-06-15 Thread Dawid Kurek
On 15/06/17, Sean Paul wrote: > On Thu, Jun 15, 2017 at 04:04:36PM +0200, Dawid Kurek wrote: > > Smaller scope reduces visibility of variable and makes usage of > > uninitialized variable less possible. > > > > Changes in v2: > > - separate declaration and initialization > > Your patch is mis

[PATCH v3] drm: Reduce scope of 'state' variable

2017-06-15 Thread Dawid Kurek
Smaller scope reduces visibility of variable and makes usage of uninitialized variable less possible. Changes in v2: - separate declaration and initialization Changes in v3: - add missing signed-off-by tag Signed-off-by: Dawid Kurek --- drivers/gpu/drm/drm_atomic.c | 3 ++- 1 fi

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

2017-06-15 Thread Sean Paul
On Fri, May 05, 2017 at 03:01:41PM -0300, Fabio Estevam wrote: > According to the eLCDIF initialization steps listed in the MX6SX > Reference Manual the eLCDIF block reset is mandatory. > > Without performing the eLCDIF reset the display shows garbage content > when the kernel boots. > > In earl

[PATCH] bridge: Fix panel-bridge error return on !panel.

2017-06-15 Thread Eric Anholt
ERR_PTR() needs a negative errno argument. Signed-off-by: Eric Anholt --- drivers/gpu/drm/bridge/panel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bridge/panel.c b/drivers/gpu/drm/bridge/panel.c index 99f9a4beb859..67fe19e5a9c6 100644 --- a/drivers/gpu/d

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #16 from Carlo Caione --- I see. The problem is that the garbage lines result in a very bad experience for the user. Do you have any idea how to fix / mitigate that? -- You are receiving this mail because: You are the assignee for

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #61 from Pavel Bordukov --- (In reply to Alex Deucher from comment #60) > Created attachment 131983 [details] [review] > possible fix It works for me (MG279Q, R9 290x, vanilla 4.11.4, echo high > /sys/class/drm/card0/device/power_dpm

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #17 from Alex Deucher --- (In reply to Carlo Caione from comment #16) > I see. The problem is that the garbage lines result in a very bad experience > for the user. Do you have any idea how to fix / mitigate that? If it's related to

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #62 from i...@posteo.net --- It works for me, too, but I already said that ;-) However, the problem Pavel describes is another bothersome issue. PowerPlay changes to the higher memory DPM state which results in ~40 Watts (Hawaii; esti

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #63 from Alex Deucher --- (In reply to iuno from comment #62) > It works for me, too, but I already said that ;-) > > However, the problem Pavel describes is another bothersome issue. PowerPlay > changes to the higher memory DPM stat

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

2017-06-15 Thread Sean Paul
On Thu, Jun 15, 2017 at 01:53:15PM -0400, Sean Paul wrote: > On Fri, May 05, 2017 at 03:01:41PM -0300, Fabio Estevam wrote: > > According to the eLCDIF initialization steps listed in the MX6SX > > Reference Manual the eLCDIF block reset is mandatory. > > > > Without performing the eLCDIF reset th

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #64 from i...@posteo.net --- (In reply to Alex Deucher from comment #63) > > Are you forcing the power state to high? The mclk shouldn't be affected by > the display clock. No, setting the refresh rate to 144 results in high mclk, e

[PULL] drm-misc-fixes

2017-06-15 Thread Sean Paul
Hi Dave, Here's this week's pull. Nothing worth noting beyond the onelines and summaries. drm-misc-fixes-2017-06-15: Driver Changes: - dw-hdmi: Fix compilation error if REGMAP_MMIO not selected (Laurent) - host1x: Fix incorrect return value (Christophe) - tegra: Shore up idr API usage in tegra sta

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #65 from Alex Deucher --- (In reply to iuno from comment #64) > (In reply to Alex Deucher from comment #63) > > > > Are you forcing the power state to high? The mclk shouldn't be affected by > > the display clock. > > No, setting t

[PATCH 4/7] drm/vc4: Use drm_mode_vrefresh() in DSI fixup, in case vrefresh is 0.

2017-06-15 Thread Eric Anholt
I'm not sure what changed where I started getting vrefresh=0 from the mode to be fixed up. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c index 629d3

[PATCH 3/7] drm/vc4: Fix misleading name of the continuous flag.

2017-06-15 Thread Eric Anholt
The logic was all right in the end, the name was just backwards. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c index 15f6d5005ab9..629d372633e6

[PATCH 0/7] RPi touchscreen as a panel driver again

2017-06-15 Thread Eric Anholt
After splitting the panel driver out into a panel and bridge due to panel review, the feedback from bridge maintainers was that it didn't make sense as a bridge. I completely agree with them. This series returns the driver to being a panel, but this time probing as an i2c client rather than a DSI

[PATCH 7/7] ARM: dts: bcm2835: Enable the Raspberry Pi touchscreen panel.

2017-06-15 Thread Eric Anholt
This commit is not intended to be merged. Instead we will use overlays to enable the panel, and this commit is just a demo of how things get wired up. Signed-off-by: Eric Anholt --- arch/arm/boot/dts/bcm2835-rpi-b-plus.dts | 5 arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts | 5

[PATCH 2/7] drm/vc4: Fix DSI T_INIT timing.

2017-06-15 Thread Eric Anholt
The DPHY spec requires a much larger T_INIT than I was specifying before. In the absence of clear specs from the slave of what their timing is, just use the value that the firmware was using. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 12 +++- 1 file changed, 11 inse

[PATCH 5/7] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

2017-06-15 Thread Eric Anholt
This doesn't yet cover input, but the driver does get the display working when the firmware is disabled from talking to our I2C lines. Signed-off-by: Eric Anholt --- .../panel/raspberrypi,7inch-touchscreen.txt| 49 ++ 1 file changed, 49 insertions(+) create mode 1006

[PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.

2017-06-15 Thread Eric Anholt
If the panel-bridge is being set up after the drm_mode_config_reset(), then the connector's state would never get initialized, and we'd dereference the NULL in the hotplug path. We also need to register the connector, so that userspace can get at it. Signed-off-by: Eric Anholt --- drivers/gpu/d

[PATCH 6/7] drm/panel: Add support for the Raspberry Pi 7" Touchscreen.

2017-06-15 Thread Eric Anholt
This driver communicates with the Atmel microcontroller for sequencing the poweron of the TC358762 DSI-DPI bridge and controlling the backlight PWM. v2: Set the same default orientation as the closed source firmware used, which is the best for viewing angle. v3: Rewrite as an i2c client driver

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #66 from i...@posteo.net --- (In reply to Alex Deucher from comment #65) > > Yes, that is independent of the patch in attachment 131983 [details] > [review]. The driver disables dynamic mclk switching for refresh rates > above 120 hz

[PULL] drm-misc-next

2017-06-15 Thread Sean Paul
Hi Dave, Here's the final drm-misc-next request for 4.13, we'll switch over to drm-misc-next-fixes for 4.13 with drm-misc-next now targetting 4.14. I'll send out a separate email to -misc committers to ensure we're all on the same page. The drm_panel_bridge change introduced a little bit of instab

-misc feature freeze: drm-misc-next-fixes->4.13, drm-misc-next->4.14

2017-06-15 Thread Sean Paul
Hi -misc committers, I just sent out the last drm-misc-next pull request for 4.13. Once Dave has applied it to drm-next, I'll perform a backmerge (there is a single patch erroneously committed to drm-misc-next-fixes which prevents fast-forward) and the branch will be open for fixes. Sean -- Sea

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #67 from Alex Deucher --- (In reply to iuno from comment #66) > (In reply to Alex Deucher from comment #65) > > > > Yes, that is independent of the patch in attachment 131983 [details] > > [review] > > [review]. The driver disables

[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101387 --- Comment #18 from Alex Deucher --- The VCE regression is fixed. If you want to try those patches, they are available here: https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.13-wip -- You are receiving this mail because: You are t

[Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate

2017-06-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93826 --- Comment #68 from i...@posteo.net --- (In reply to Alex Deucher from comment #67) > Do you get flickering at 144Hz without forcing the mclk to high? I.e., > without these patches: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linu

Re: [PATCH 2/2] drm/vc4: Add get/set tiling ioctls.

2017-06-15 Thread Eric Anholt
Boris Brezillon writes: > Hi Eric, > > On Wed, 7 Jun 2017 17:13:36 -0700 > Eric Anholt wrote: > >> This allows mesa to set the tiling format for a BO and have that >> tiling format be respected by mesa on the other side of an >> import/export (and by vc4 scanout in the kernel), without defining

Re: [PATCH] fixup! drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-15 Thread Rob Clark
On Thu, Jun 15, 2017 at 5:59 PM, Susheelendra, Sushmita wrote: > Hi Rob, > > I can see how we can trigger the shrinker on objB while holding objA->lock. > So, the nested lock with class SHRINKER makes sense. > However, I’m trying to figure how the get_pages/vmap/fault path on an objA > can end up

Re: [PATCH] drm/core: Fail atomic IOCTL with no CRTC state but with signaling.

2017-06-15 Thread Andrey Grodzovsky
Just a reminder. Thanks. On 06/09/2017 05:30 PM, Andrey Grodzovsky wrote: Problem: While running IGT kms_atomic_transition test suite i encountered a hang in drmHandleEvent immidietly follwoing an atomic_commit. After dumping the atomic state I relized that in this case there was not even one C

[PATCH v2 6/6 squash] drm/vc4: Fixup for the drm core async changes.

2017-06-15 Thread Eric Anholt
With this squashed in, the vc4 patch is: Reviewed-by: Eric Anholt Signed-off-by: Eric Anholt --- Without this, the cursor never moved :) drivers/gpu/drm/vc4/vc4_plane.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c ind

Re: [PATCH 2/7] drm/vc4: Fix vblank handling

2017-06-15 Thread Eric Anholt
Boris Brezillon writes: > There are two problems related to VBLANK handling in the current CRTC > driver: > > * VBLANK events are missed when the CRTC is being disabled because the > driver does not wait till the end of the frame before stopping the > HVS and PV blocks. In this case, we shoul

Re: [PATCH 3/7] drm/vc4: Mimic drm_atomic_helper_commit() behavior

2017-06-15 Thread Eric Anholt
Eric Anholt writes: > [ Unknown signature status ] > Boris Brezillon writes: > >> On Tue, 06 Jun 2017 13:27:09 -0700 >> Eric Anholt wrote: >> >>> Boris Brezillon writes: >>> >>> > The VC4 KMS driver is implementing its own ->atomic_commit() but there >>> > are a few generic helpers we can use

sub maintainer trees

2017-06-15 Thread Dave Airlie
rc6 is this Sunday most likely which means I'll be mostly finished merging at that point. nouveau and msm are known outstanding, but I've talked to those, anyone else got something I should know about? Dave. ___ dri-devel mailing list dri-devel@lists.fr

Re: Color lookup support for the atmel-hlcdc driver

2017-06-15 Thread Peter Rosin
On 2017-06-15 12:15, Boris Brezillon wrote: > On Thu, 15 Jun 2017 11:54:29 +0200 > Peter Rosin wrote: > >> On 2017-06-13 17:30, Boris Brezillon wrote: >>> Hi Peter, >>> >>> On Tue, 13 Jun 2017 16:34:25 +0200 >>> Peter Rosin wrote: >>> Hi! I need color lookup support for the atm

Re: [PATCH] fixup! drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-15 Thread Susheelendra, Sushmita
Hi Rob, I can see how we can trigger the shrinker on objB while holding objA->lock. So, the nested lock with class SHRINKER makes sense. However, I’m trying to figure how the get_pages/vmap/fault path on an objA can end up triggering the shrinker on objA itself. As objA itself would not be purg

Re: [PATCH] drm: atmel-hlcdc: sama5d4 does not have overlay2

2017-06-15 Thread Peter Rosin
On 2017-06-15 11:37, Boris Brezillon wrote: > On Thu, 15 Jun 2017 11:24:13 +0200 > Peter Rosin wrote: > >> From: Peter Rosin >> >> Remove the layer. > > Duh. It was present in the datasheet I had. Just downloaded last > version of the datasheet and it's no longer there. Heh. > Nicolas, there'

lvds-encoder... why not lvds-bridge

2017-06-15 Thread Jean-Francois Dagenais
Bonjour Laurent! I was wondering why you choose to name the lvds-encoder.c driver like so. (https://github.com/torvalds/linux/commit/67cc3e22b00f9027eaa0902ecf52ac5f4f5cac97) The driver is clearly a drm_bridge, nested in the drm/bridge subdir... so why not "lvds-bridge.c"? Also, the associated b

  1   2   >