[PATCH 2/4] sync_file: add replace and export some functionality (v2)

2017-03-20 Thread Dave Airlie
From: Dave Airlie Using sync_file to back vulkan semaphores means need to replace the fence underlying the sync file. This replace function removes the callback, swaps the fence, and returns the old one. This also exports the alloc and fdget functionality for the semaphore wrapper code. v2: use

[rfc/repost] amdgpu/sync_file shared semaphores

2017-03-20 Thread Dave Airlie
This is a repost of the file_sync semaphore support. The main difference in this patch is patch1 does a lot better at handling NULL fences in some places. The poll code and ioctls should handle ending up with fence being NULL properly now. Dave. ___ dr

[PATCH 3/4] amdgpu/cs: split out fence dependency checking

2017-03-20 Thread Dave Airlie
From: Dave Airlie This just splits out the fence depenency checking into it's own function to make it easier to add semaphore dependencies. Signed-off-by: Dave Airlie --- drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 86 +++--- 1 file changed, 48 insertions(+), 38 deleti

[PATCH 1/4] sync_file: add a mutex to protect fence and callback members. (v3)

2017-03-20 Thread Dave Airlie
From: Dave Airlie This patch allows the underlying fence in a sync_file to be changed or set to NULL. This isn't currently required but for Vulkan semaphores we need to be able to swap and reset the fence. In order to faciliate this, it uses rcu to protect the fence, along with a new mutex. The

[PATCH 4/4] amdgpu: use sync file for shared semaphores

2017-03-20 Thread Dave Airlie
From: Dave Airlie This creates a new interface for amdgpu with ioctls to create/destroy/import and export shared semaphores using sem object backed by the sync_file code. The semaphores are not installed as fd (except for export), but rather like other driver internal objects in an idr. The idr h

Re: linux-next: build failure after merge of the drm tree

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 1:51 AM, Stephen Rothwell wrote: > This cherry picking of fixes from new development back to Linus' tree > can be a real pain when so many other changes happen in the same files. One possible fix for this would be if you reuse our rerere cache. The only reason we don't go

Re: linux-next: build failure after merge of the drm tree

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 9:03 AM, Daniel Vetter wrote: > On Mon, Mar 20, 2017 at 1:51 AM, Stephen Rothwell > wrote: >> This cherry picking of fixes from new development back to Linus' tree >> can be a real pain when so many other changes happen in the same files. > > One possible fix for this wou

Re: [PATCH 1/3] drm/etnaviv: submit support for in-fences

2017-03-20 Thread Daniel Vetter
On Fri, Mar 17, 2017 at 11:00:44AM -0300, Gustavo Padovan wrote: > 2017-03-16 Philipp Zabel : > > > Hi Gustavo, > > > > On Mon, 2017-03-13 at 14:37 -0300, Gustavo Padovan wrote: > > [...] > > > I was thinking on some function that would iterate over all fences in > > > the fence_array and check t

Re: [PATCH 1/4] sync_file: add a mutex to protect fence and callback members. (v3)

2017-03-20 Thread Chris Wilson
On Mon, Mar 20, 2017 at 05:03:04PM +1000, Dave Airlie wrote: > From: Dave Airlie > > This patch allows the underlying fence in a sync_file to be changed > or set to NULL. This isn't currently required but for Vulkan > semaphores we need to be able to swap and reset the fence. > > In order to fac

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Daniel Vetter
On Fri, Mar 17, 2017 at 05:52:32PM +0100, Maarten Lankhorst wrote: > Op 16-03-17 om 21:15 schreef Daniel Vetter: > > On Thu, Mar 16, 2017 at 5:09 PM, Maarten Lankhorst > > wrote: > >> Op 16-03-17 om 16:52 schreef Daniel Vetter: > >>> The vblank code really wants to look at crtc->state without havi

Re: [PATCH 1/4] sync_file: add a mutex to protect fence and callback members. (v3)

2017-03-20 Thread Chris Wilson
On Mon, Mar 20, 2017 at 05:03:04PM +1000, Dave Airlie wrote: > From: Dave Airlie > > This patch allows the underlying fence in a sync_file to be changed > or set to NULL. This isn't currently required but for Vulkan > semaphores we need to be able to swap and reset the fence. > > In order to fac

Re: [PATCH] drm: add check for plane functions

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 09:58:01AM +0530, Shirish S wrote: > First of all, thanks for your comments/insights. > > On Sat, Mar 18, 2017 at 12:59 AM, Eric Anholt wrote: > > Ville Syrjälä writes: > > > >> On Fri, Mar 17, 2017 at 05:57:52PM +0100, Daniel Vetter wrote: > >>> On Fri, Mar 17, 2017 at 0

Re: [PATCH 2/2] drm/pl111: Initial drm/kms driver for pl111

2017-03-20 Thread Daniel Vetter
On Fri, Mar 17, 2017 at 03:47:42PM -0700, Eric Anholt wrote: > From: Tom Cooksey > > This is a modesetting driver for the pl111 CLCD display controller > found on various ARM platforms such as the Versatile Express. The > driver has only been tested on the bcm911360_entphn platform so far, > with

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Maarten Lankhorst
Op 20-03-17 om 09:18 schreef Daniel Vetter: > On Fri, Mar 17, 2017 at 05:52:32PM +0100, Maarten Lankhorst wrote: >> Op 16-03-17 om 21:15 schreef Daniel Vetter: >>> On Thu, Mar 16, 2017 at 5:09 PM, Maarten Lankhorst >>> wrote: Op 16-03-17 om 16:52 schreef Daniel Vetter: > The vblank code r

Re: [PATCH 1/4] sync_file: add a mutex to protect fence and callback members. (v3)

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 08:16:36AM +, Chris Wilson wrote: > On Mon, Mar 20, 2017 at 05:03:04PM +1000, Dave Airlie wrote: > > From: Dave Airlie > > > > This patch allows the underlying fence in a sync_file to be changed > > or set to NULL. This isn't currently required but for Vulkan > > semap

Re: [rfc/repost] amdgpu/sync_file shared semaphores

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 05:03:03PM +1000, Dave Airlie wrote: > This is a repost of the file_sync semaphore support. > > The main difference in this patch is patch1 does a lot > better at handling NULL fences in some places. The poll code > and ioctls should handle ending up with fence being NULL p

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 09:38:52AM +0100, Maarten Lankhorst wrote: > Op 20-03-17 om 09:18 schreef Daniel Vetter: > > On Fri, Mar 17, 2017 at 05:52:32PM +0100, Maarten Lankhorst wrote: > >> Op 16-03-17 om 21:15 schreef Daniel Vetter: > >>> On Thu, Mar 16, 2017 at 5:09 PM, Maarten Lankhorst > >>> wr

Re: [PATCH] drm/etnaviv: add etnaviv cooling device

2017-03-20 Thread Lucas Stach
Am Sonntag, den 19.03.2017, 13:03 -0700 schrieb Chris Healy: > I don't have any input on this binary divider subject but I do want to > bring up some observations regarding Etnaviv GPU power management that > seems relevant. > > I've done some comparisons between the Freescale Vivante GPU driver >

Re: [PATCH] drm/etnaviv: add etnaviv cooling device

2017-03-20 Thread Lucas Stach
Am Mittwoch, den 15.03.2017, 14:05 + schrieb Russell King - ARM Linux: > On Wed, Mar 15, 2017 at 02:03:09PM +0100, Lucas Stach wrote: > > Am Sonntag, den 12.03.2017, 19:00 + schrieb Russell King: > > > Each Vivante GPU contains a clock divider which can divide the GPU clock > > > by 2^n, wh

Re: [PATCH] drm: add check for plane functions

2017-03-20 Thread Shirish S
On Mon, Mar 20, 2017 at 1:51 PM, Daniel Vetter wrote: > On Mon, Mar 20, 2017 at 09:58:01AM +0530, Shirish S wrote: >> First of all, thanks for your comments/insights. >> >> On Sat, Mar 18, 2017 at 12:59 AM, Eric Anholt wrote: >> > Ville Syrjälä writes: >> > >> >> On Fri, Mar 17, 2017 at 05:57:52

[PATCH 1/3] drm/i915: allocate mock file pointer dynamically

2017-03-20 Thread Arnd Bergmann
A struct file is a bit too large to put on the kernel stack in general and triggers a warning for low settings of CONFIG_FRAME_WARN: drivers/gpu/drm/i915/selftests/mock_drm.c: In function 'mock_file': drivers/gpu/drm/i915/selftests/mock_drm.c:46:1: error: the frame size of 1328 bytes is larger th

[PATCH 2/3] drm/i915: split out check for noncontiguous pfn range

2017-03-20 Thread Arnd Bergmann
We get a warning with gcc-7 about a pointless comparison when using a linear memmap: drivers/gpu/drm/i915/selftests/scatterlist.c: In function 'alloc_table': drivers/gpu/drm/i915/selftests/scatterlist.c:219:66: error: self-comparison always evaluates to false [-Werror=tautological-compare] Split

[PATCH 3/3] [RFC] Revert "drm/i915: use variadic macros and arrays to choose port/pipe based registers"

2017-03-20 Thread Arnd Bergmann
The varargs macro trick in _PIPE3/_PHY3/_PORT3 was meant as an optimization to shrink the i915 kernel module by around 1000 bytes. However, the downside is a size regression with CONFIG_KASAN, as I found from stack size warnings with gcc-7.0.1: before: drivers/gpu/drm/i915/intel_dpll_mgr.c: In fun

[PATCH] drm/msm: add stubs for msm_{perf,rd}_debugfs_cleanup

2017-03-20 Thread Arnd Bergmann
We now call those two functions even when they are not defined or declared anywhere because DEBUG_FS is disabled: drivers/gpu/drm/msm/msm_drv.c: In function 'msm_drm_uninit': drivers/gpu/drm/msm/msm_drv.c:244:2: error: implicit declaration of function 'msm_perf_debugfs_cleanup';did you mean 'msm_

Re: [PATCH 1/3] drm/i915: allocate mock file pointer dynamically

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 10:40:27AM +0100, Arnd Bergmann wrote: > A struct file is a bit too large to put on the kernel stack in general > and triggers a warning for low settings of CONFIG_FRAME_WARN: > > drivers/gpu/drm/i915/selftests/mock_drm.c: In function 'mock_file': > drivers/gpu/drm/i915/sel

Re: [PATCH v2 1/8] dt-bindings: add binding for the Allwinner DE2 CCU

2017-03-20 Thread Maxime Ripard
On Fri, Mar 17, 2017 at 04:47:41AM +0800, Icenowy Zheng wrote: > Allwinner "Display Engine 2.0" contains some clock controls in it. > > Add them as a clock driver, and make a device tree binding. > > Signed-off-by: Icenowy Zheng > --- > .../devicetree/bindings/clock/sun8i-de2.txt| 31 >

Re: [PATCH v2 3/8] dt-bindings: add bindings for DE2 on V3s SoC

2017-03-20 Thread Maxime Ripard
On Fri, Mar 17, 2017 at 04:47:43AM +0800, Icenowy Zheng wrote: > Allwinner V3s SoC have a display engine which have a different pipeline > with older SoCs. > > Add document for it (new compatibles and the new "mixer" part). > > The paragraph of TCON is also refactored, for furtherly add TCONs in

Re: [PATCH] drm/msm: add stubs for msm_{perf,rd}_debugfs_cleanup

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 10:39:25AM +0100, Arnd Bergmann wrote: > We now call those two functions even when they are not defined > or declared anywhere because DEBUG_FS is disabled: > > drivers/gpu/drm/msm/msm_drv.c: In function 'msm_drm_uninit': > drivers/gpu/drm/msm/msm_drv.c:244:2: error: implic

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Maarten Lankhorst
Op 20-03-17 om 09:59 schreef Daniel Vetter: > On Mon, Mar 20, 2017 at 09:38:52AM +0100, Maarten Lankhorst wrote: >> Op 20-03-17 om 09:18 schreef Daniel Vetter: >>> On Fri, Mar 17, 2017 at 05:52:32PM +0100, Maarten Lankhorst wrote: Op 16-03-17 om 21:15 schreef Daniel Vetter: > On Thu, Mar 1

Re: [PATCH 3/3] [RFC] Revert "drm/i915: use variadic macros and arrays to choose port/pipe based registers"

2017-03-20 Thread Jani Nikula
On Mon, 20 Mar 2017, Arnd Bergmann wrote: > The varargs macro trick in _PIPE3/_PHY3/_PORT3 was meant as an optimization > to shrink the i915 kernel module by around 1000 bytes. To be clear, it was not at all intended to be an optimization, nothing of the sort. The intention was to make it easier

Re: [PATCH] drm/vc4: use platform_register_drivers

2017-03-20 Thread Philipp Zabel
On Sun, 2017-03-19 at 11:28 +, Emil Velikov wrote: > Hi Philipp, > > I think you patch is OK, just a small question about the existing code. > It might be better suited for Eric... not sure. > > On 17 March 2017 at 17:00, Philipp Zabel wrote: > > Use platform_register_drivers instead of open

Re: [PATCH] drm/msm: for array in-fences, check if all backing fences are from our own context before waiting

2017-03-20 Thread Philipp Zabel
On Sat, 2017-03-18 at 08:48 -0400, Rob Clark wrote: > On Fri, Mar 17, 2017 at 2:38 PM, Philipp Zabel wrote: > > Use the dma_fence_match_context helper to check if all backing fences > > are from our own context, in which case we don't have to wait. > > > > Signed-off-by: Philipp Zabel > > Cc: Rob

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Chris Wilson
On Mon, Mar 20, 2017 at 11:01:59AM +0100, Maarten Lankhorst wrote: > Op 20-03-17 om 09:59 schreef Daniel Vetter: > > But my idea was kinda that we'd do the same for probe -> modeset data > > flows like here for the other way round: Just a bunch of READ_ONCE and > > maybe lookup the edid with rcu to

Re: [PATCH v2 4/8] drm/sun4i: add support for sun8i DE2 mixers and display engines

2017-03-20 Thread Maxime Ripard
Hi, On Fri, Mar 17, 2017 at 04:47:44AM +0800, Icenowy Zheng wrote: > Allwinner have a new "Display Engine 2.0" in there new SoCs, which comes > in a new "Display Engine" (mixers instead of old backends and > frontends). > > Add support for the mixer on Allwinner V3s SoC; it's the simplest one. >

Re: [PATCH] drm: bochs: Don't remove uninitialized fbdev framebuffer

2017-03-20 Thread Gerd Hoffmann
On Fr, 2017-03-17 at 15:14 -0300, Gabriel Krisman Bertazi wrote: > In the same spirit of the fix for QXL in commit 861078381ba5 ("drm: > qxl: > Don't alloc fbdev if emulation is not supported"), prevent the Oops in > the unbind path of Bochs if fbdev emulation is disabled. pushed to drm-misc-next

Re: [PATCH 3/3] [RFC] Revert "drm/i915: use variadic macros and arrays to choose port/pipe based registers"

2017-03-20 Thread Arnd Bergmann
On Mon, Mar 20, 2017 at 11:08 AM, Jani Nikula wrote: > On Mon, 20 Mar 2017, Arnd Bergmann wrote: >> The varargs macro trick in _PIPE3/_PHY3/_PORT3 was meant as an optimization >> to shrink the i915 kernel module by around 1000 bytes. > > To be clear, it was not at all intended to be an optimizati

Re: DRM Atomic property for color-space conversion

2017-03-20 Thread Hans Verkuil
On 03/17/2017 03:09 PM, Ville Syrjälä wrote: > On Fri, Mar 17, 2017 at 10:33:15AM +, Brian Starkey wrote: >> For not-programmable hardware, would a second "DEGAMMA_FIXED" property >> make sense, which is an enum type exposing what curves are supported? >> (with analogous GAMMA_FIXED as well) >

Re: [PATCHv2 03/10] Revert "drm: omapdrm: Remove manual update display support"

2017-03-20 Thread Tomi Valkeinen
On 05/03/17 02:43, Sebastian Reichel wrote: > This reverts commit 5a35876e2830511cb8110667fc426c6a6165a593. > > Revert the removal of manual update display support in > preparation for DSI command mode panels. I think it's much better to just add the manual update support from scratch rather than

Re: [PATCHv2 09/10] drm: omapdrm: crtc: get manual mode displays working

2017-03-20 Thread Tomi Valkeinen
On 05/03/17 02:43, Sebastian Reichel wrote: > From: Tony Lindgren > > With manual mode displays we need to flush the panel manually. > > Let's add flushing so we get Tomi's fbtest, kmstest, kmstest --flip, > and X and wayland working. > > Signed-off-by: Tony Lindgren > [On Nokia N950] > Tested

Re: [PATCH 3/3] [RFC] Revert "drm/i915: use variadic macros and arrays to choose port/pipe based registers"

2017-03-20 Thread Jani Nikula
On Mon, 20 Mar 2017, Arnd Bergmann wrote: > I don't know how to generate a URL for it, but after adding this to the > command line for gcc-7, > > -fsanitize=kernel-address -fasan-shadow-offset=0xdfff9000 > --param asan-stack=1 --param asan-globals=1 --param > asan-instrumentation-with-call

Re: [PATCHv2 00/10] Nokia N950 basic display support

2017-03-20 Thread Tomi Valkeinen
Hi, On 05/03/17 01:50, Sebastian Reichel wrote: > Hi, > > Some of you may remember, that I sent a series for the N950 display > some time ago. N950 has command mode DSI panel, so the main part of > the patchset takes care of adding manual display update support in > omapdrm. > > The N950 also re

Re: [PATCH 1/3] drm/i915: allocate mock file pointer dynamically

2017-03-20 Thread Joonas Lahtinen
On ma, 2017-03-20 at 10:40 +0100, Arnd Bergmann wrote: > A struct file is a bit too large to put on the kernel stack in general > and triggers a warning for low settings of CONFIG_FRAME_WARN: > > drivers/gpu/drm/i915/selftests/mock_drm.c: In function 'mock_file': > drivers/gpu/drm/i915/selftests/m

[Bug 98604] [VDPAU, DRI3] Fullscreen flash video fails when hardware acceleration is enabled.

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98604 --- Comment #14 from Dieter Nützel --- Any progress? Michel? DRI2 vs DRI3 Wouldn't it be nice to have this in 7.1? -- You are receiving this mail because: You are the assignee for the bug.___ dri-de

Re: [PATCH 1/3] drm/i915: allocate mock file pointer dynamically

2017-03-20 Thread Arnd Bergmann
On Mon, Mar 20, 2017 at 1:00 PM, Joonas Lahtinen wrote: > On ma, 2017-03-20 at 10:40 +0100, Arnd Bergmann wrote: >> diff --git a/drivers/gpu/drm/i915/selftests/mock_drm.c >> b/drivers/gpu/drm/i915/selftests/mock_drm.c >> index 113dec05c7dc..18514065c93d 100644 >> --- a/drivers/gpu/drm/i915/selft

Re: [PATCH 1/3] drm/i915: allocate mock file pointer dynamically

2017-03-20 Thread Arnd Bergmann
On Mon, Mar 20, 2017 at 1:02 PM, Arnd Bergmann wrote: > On Mon, Mar 20, 2017 at 1:00 PM, Joonas Lahtinen > wrote: >> On ma, 2017-03-20 at 10:40 +0100, Arnd Bergmann wrote: > >>> diff --git a/drivers/gpu/drm/i915/selftests/mock_drm.c >>> b/drivers/gpu/drm/i915/selftests/mock_drm.c >>> index 113de

[Bug 194949] New: Amdgpu: RX 460 idle temp is 45C

2017-03-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=194949 Bug ID: 194949 Summary: Amdgpu: RX 460 idle temp is 45C Product: Drivers Version: 2.5 Kernel Version: 4.12-wip Hardware: x86-64 OS: Linux Tree: Mainline

Re: [PATCH v2] drm/bridge: dw_hdmi: support i2c extended read mode

2017-03-20 Thread Vladimir Zapolskiy
Hi Nickey, On 03/20/2017 04:57 AM, Nickey Yang wrote: > "I2C Master Interface Extended Read Mode" implements a segment > pointer-based read operation using the Special Register configuration. > > This patch fix https://patchwork.kernel.org/patch/7098101/ mentioned > "The current implementation do

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Maarten Lankhorst
Op 20-03-17 om 11:22 schreef Chris Wilson: > On Mon, Mar 20, 2017 at 11:01:59AM +0100, Maarten Lankhorst wrote: >> Op 20-03-17 om 09:59 schreef Daniel Vetter: >>> But my idea was kinda that we'd do the same for probe -> modeset data >>> flows like here for the other way round: Just a bunch of READ_

Re: [PATCH v2 0/2] drm/panel: Add support for the Sitronix ST7789V

2017-03-20 Thread Maxime Ripard
Hi Thierry, On Thu, Feb 09, 2017 at 02:14:26PM +0100, Maxime Ripard wrote: > Hi, > > Here is an attempt at supporting the ST7789V LCD controller from Sitronix. > > It is controlled through an SPI bus, with a twist, since each byte sent > must be prefixed by a bit, which needs an 9-bits-per-word

[Bug 194949] Amdgpu: RX 460 idle temp is 45C

2017-03-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=194949 --- Comment #1 from fin4...@hotmail.com --- There is following errors in dmesg: [5.175777] amdgpu: [powerplay] failed to send message 260 ret is 0 [5.176128] [drm:amdgpu_set_powergating_state [amdgpu]] *ERROR* set_powerga

[Bug 194949] Amdgpu: RX 460 idle temp is 45C

2017-03-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=194949 --- Comment #2 from fin4...@hotmail.com --- Created attachment 255365 --> https://bugzilla.kernel.org/attachment.cgi?id=255365&action=edit dmesg output -- You are receiving this mail because: You are watching the assignee of the bug. _

[Bug 194949] Amdgpu: RX 460 idle temp is 45C

2017-03-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=194949 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-20 Thread Emil Velikov
Seems like we ended up all over the place, so let me try afresh. Above all: - Saying "I don't care" about your users is arrogant - let us _not_ do that, please ? Even Linux distribution maintainers have responded that "upstream does not care us", which is indicative that we should be more careful

Re: [PATCH 01/41] drm/panel: simple: Change mode for Sharp lq123p1jx31

2017-03-20 Thread Thierry Reding
On Thu, Mar 09, 2017 at 11:32:16PM -0500, Sean Paul wrote: > Change the mode for Sharp lq123p1jx31 panel to something more > rockchip-friendly such that we can use the fixed PLLs to > generate the pixel clock > > Cc: Chris Zhong > Cc: Stéphane Marchesin > Signed-off-by: Sean Paul > --- > drive

[Bug 100270] power usage increase by approx 4W between kernel 4.7.8 and 4.8.5

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100270 --- Comment #3 from Alex Deucher --- What is the date on your system bios? The core kernel only enables pcie port pm (d3cold) on systems with a date of 2015 or newer, but there have been systems shipping which use those methods since 2013. --

Re: [PATCH v3 3/6] documentation: media: Add documentation for new RGB and YUV bus formats

2017-03-20 Thread Hans Verkuil
On 03/07/2017 05:42 PM, Neil Armstrong wrote: > Add documentation for added Bus Formats to describe RGB and YUS formats used > as input to the Synopsys DesignWare HDMI TX Controller. > > Signed-off-by: Neil Armstrong > --- > Documentation/media/uapi/v4l/subdev-formats.rst | 4992 > +

[Bug 194949] Amdgpu: RX 460 idle temp is 45C

2017-03-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=194949 --- Comment #4 from fin4...@hotmail.com --- (In reply to Alex Deucher from comment #3) > (In reply to fin4478 from comment #0) > > I have the latest firmware from: > > https://people.freedesktop.org/~agd5f/radeon_ucode/polaris/ > > Does it work p

Re: [PATCHv2 1/4] video: add hotplug detect notifier support

2017-03-20 Thread Hans Verkuil
On 03/20/2017 03:27 PM, Russell King - ARM Linux wrote: On Mon, Mar 20, 2017 at 02:26:16PM +, Russell King - ARM Linux wrote: On Mon, Jan 02, 2017 at 03:19:04PM +0100, Hans Verkuil wrote: From: Hans Verkuil Add support for video hotplug detect and EDID/ELD notifiers, which is used to conv

Re: [PATCH v3 3/6] documentation: media: Add documentation for new RGB and YUV bus formats

2017-03-20 Thread Hans Verkuil
On 03/17/2017 05:11 PM, Neil Armstrong wrote: > On 03/16/2017 06:01 PM, Archit Taneja wrote: >> >> >> On 3/7/2017 10:12 PM, Neil Armstrong wrote: >>> Add documentation for added Bus Formats to describe RGB and YUS formats used >> >> s/YUS/YUV > > Thanks again > >> >>> as input to the Synopsys

Re: [PATCH] drm/atomic: protect crtc|connector->state with rcu

2017-03-20 Thread Daniel Vetter
On Mon, Mar 20, 2017 at 11:01:59AM +0100, Maarten Lankhorst wrote: > Op 20-03-17 om 09:59 schreef Daniel Vetter: > > On Mon, Mar 20, 2017 at 09:38:52AM +0100, Maarten Lankhorst wrote: > >> Op 20-03-17 om 09:18 schreef Daniel Vetter: > >>> On Fri, Mar 17, 2017 at 05:52:32PM +0100, Maarten Lankhorst

Re: [PATCH v2] dt-bindings: drm: rcar-du: Document optional reset properties

2017-03-20 Thread Rob Herring
On Thu, Mar 16, 2017 at 09:59:04PM +0100, Geert Uytterhoeven wrote: > Hi Rob, > > On Thu, Mar 16, 2017 at 9:56 PM, Rob Herring wrote: > > On Thu, Mar 16, 2017 at 09:13:16AM +0100, Geert Uytterhoeven wrote: > >> On Wed, Mar 15, 2017 at 6:01 PM, Rob Herring wrote: > >> > On Mon, Mar 06, 2017 at 05

[Bug 93050] Amdgpu, Tonga "IO_PAGE_FAULT" and "[amdgpu]] *ERROR* amdgpu: ring 0 test failed" result in Kernel Panic

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=93050 --- Comment #4 from Vedran Miletić --- (In reply to jk from comment #0) > Created attachment 12 [details] > Logfile > > Switched from catalyst to amdgpu, Kernel 4.2 and Kernel 4.3 with powerplay > fixes crash, wenn modesetting is enabled (wh

[PULL] drm-intel-next

2017-03-20 Thread Daniel Vetter
/anongit.freedesktop.org/git/drm-intel tags/drm-intel-next-2017-03-20 for you to fetch changes up to c5bd2e14e85d180bc7fb3b8b62ac9348bddaf898: drm/i915: Update DRIVER_DATE to 20170320 (2017-03-20 08:21:05 +0100) More in i915 for

Re: [PATCH v3 2/6] media: uapi: Add RGB and YUV bus formats for Synopsys HDMI TX Controller

2017-03-20 Thread Hans Verkuil
On 03/07/2017 05:42 PM, Neil Armstrong wrote: > In order to describe the RGB and YUB bus formats used to feed the > Synopsys DesignWare HDMI TX Controller, add missing formats to the > list of Bus Formats. > > Documentation for these formats is added in a separate patch. > > Signed-off-by: Neil A

[Bug 100212] Implement vload_* and vstore_* to make Theano/libgpuarray working

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100212 --- Comment #2 from Vedran Miletić --- Does https://www.khronos.org/registry/OpenCL/sdk/1.1/docs/man/xhtml/vload_half.html https://www.khronos.org/registry/OpenCL/sdk/1.1/docs/man/xhtml/vstore_half.html help? -- You are receiving this mail b

[PATCH 2/2] drm/etnaviv: update MLCG disables with info from newer Vivante driver

2017-03-20 Thread Lucas Stach
PA clock gating can be enabled when the right bugfix bit is present. There are broken revs of GC4000 and GC2000, which need TX clock gating to be disabled. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff

[PATCH 1/2] drm/etnaviv: update common.xml.h

2017-03-20 Thread Lucas Stach
Update the common hardware header with new information from rnndb. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/common.xml.h | 150 +-- 1 file changed, 89 insertions(+), 61 deletions(-) diff --git a/drivers/gpu/drm/etnaviv/common.xml.h b/drivers/gpu/dr

[Bug 100288] clover unable to run OpenCL kernels since 03127bb radeonsi: compile all TGSI compute shaders asynchronously

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100288 Bug ID: 100288 Summary: clover unable to run OpenCL kernels since 03127bb radeonsi: compile all TGSI compute shaders asynchronously Product: Mesa Version: git

Re: [PATCH v6] drm/rockchip: Refactor the component match logic.

2017-03-20 Thread Heiko Stuebner
Am Montag, 20. März 2017, 11:42:40 CET schrieb Jeffy Chen: > Currently we are adding all components from the dts, if one of their > drivers been disabled, we would not be able to bring up others. > > Refactor component match logic, follow exynos drm. > > Signed-off-by: Jeffy Chen > Reviewed-by:

[PATCH v2 0/2] drm/omapdrm: Remove CONFIG_DRM_OMAP_NUM_CRTCS and cleanup

2017-03-20 Thread Jyri Sarha
The first patch removes CONFIG_DRM_OMAP_NUM_CRTCS config option. The rest cleans up the unnecessary complexity from omap_modeset_init(). Changes since first version: - drm/omapdrm: Get rid of DRM_OMAP_NUM_CRTCS config option - drm/omapdrm: -> drm/omap: - Drop: - drm/omapdrm: Change possible_cr

[PATCH v2 1/2] drm/omap: Get rid of DRM_OMAP_NUM_CRTCS config option

2017-03-20 Thread Jyri Sarha
Allocate one CRTC for each connected output and get rid of DRM_OMAP_NUM_CRTCS config option. We still can not create more CRTCs than we have DSS display managers. We also reserve one overlay per CRTC for primary plane so we can not have more CRTCs than we have overlays either. Signed-off-by: Jyri

[PATCH v2 2/2] drm/omap: Major omap_modeset_init() cleanup

2017-03-20 Thread Jyri Sarha
Cleanup overly complex omap_modeset_init(). The function is trying to support many unusual configuration, that have never been tested and are not supported by other parts of the dirver. After cleanup the init function creates exactly one connector, encoder, crtc, and primary plane per each connect

Re: [PATCHv2 03/10] Revert "drm: omapdrm: Remove manual update display support"

2017-03-20 Thread Tomi Valkeinen
On 20/03/17 18:14, Tony Lindgren wrote: > * Tomi Valkeinen [170320 04:10]: >> On 05/03/17 02:43, Sebastian Reichel wrote: >>> This reverts commit 5a35876e2830511cb8110667fc426c6a6165a593. >>> >>> Revert the removal of manual update display support in >>> preparation for DSI command mode panels. >>

Re: [PATCH 01/41] drm/panel: simple: Change mode for Sharp lq123p1jx31

2017-03-20 Thread Doug Anderson
Hi, On Mon, Mar 20, 2017 at 6:59 AM, Thierry Reding wrote: > On Thu, Mar 09, 2017 at 11:32:16PM -0500, Sean Paul wrote: >> Change the mode for Sharp lq123p1jx31 panel to something more >> rockchip-friendly such that we can use the fixed PLLs to >> generate the pixel clock >> >> Cc: Chris Zhong >

Re: [PATCH] drm/tegra: add tiling FB modifiers

2017-03-20 Thread Thierry Reding
On Tue, Nov 08, 2016 at 06:19:01PM +0900, Alexandre Courbot wrote: > On 11/08/2016 06:07 PM, Erik Faye-Lund wrote: > > On Tue, Nov 8, 2016 at 8:50 AM, Alexandre Courbot > > wrote: > >> Add FB modifiers to allow user-space to specify that a surface is in one > >> of the two tiling formats supporte

Re: [PATCH] drm/vc4: use platform_register_drivers

2017-03-20 Thread Eric Anholt
Emil Velikov writes: > Hi Philipp, > > I think you patch is OK, just a small question about the existing code. > It might be better suited for Eric... not sure. > > On 17 March 2017 at 17:00, Philipp Zabel wrote: >> Use platform_register_drivers instead of open coding the iteration over >> compo

Re: [PATCH] drm/tegra: add tiling FB modifiers

2017-03-20 Thread Thierry Reding
On Tue, Nov 08, 2016 at 04:50:42PM +0900, Alexandre Courbot wrote: > Add FB modifiers to allow user-space to specify that a surface is in one > of the two tiling formats supported by Tegra chips, and add support in > the tegradrm driver to handle them properly. This is necessary for the > display c

Re: GEM allocation for para-virtualized DRM driver

2017-03-20 Thread Rob Clark
On Mon, Mar 20, 2017 at 1:18 PM, Oleksandr Andrushchenko wrote: > > > On 03/18/2017 02:22 PM, Rob Clark wrote: >> >> On Fri, Mar 17, 2017 at 1:39 PM, Oleksandr Andrushchenko >> wrote: >>> >>> Hello, >>> I am writing a para-virtualized DRM driver for Xen hypervisor >>> and it now works with DRM CM

[PATCH] drm/gma500: fix memory leak on edid

2017-03-20 Thread Colin King
From: Colin Ian King edid is allocated on the call to psb_intel_sdvo_get_edid but not kfree'd at all, causing a memory leak. Fix this by kfree'ing the edid. (This may be null, but kfree can handle null frees). Detected by CoverityScan, CID#1090730 ("Resource Leak") Fixes: 5736995b473b ("gma50

[Bug 100289] 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100289 Bug ID: 100289 Summary: 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor Product: DRI

Re: GEM allocation for para-virtualized DRM driver

2017-03-20 Thread Rob Clark
On Mon, Mar 20, 2017 at 2:01 PM, Oleksandr Andrushchenko wrote: > On 03/20/2017 07:38 PM, Rob Clark wrote: >> >> On Mon, Mar 20, 2017 at 1:18 PM, Oleksandr Andrushchenko >> wrote: >>> >>> >>> On 03/18/2017 02:22 PM, Rob Clark wrote: On Fri, Mar 17, 2017 at 1:39 PM, Oleksandr Andrushchen

Re: [PATCH 2/2] drm/pl111: Initial drm/kms driver for pl111

2017-03-20 Thread Eric Anholt
Daniel Vetter writes: > On Fri, Mar 17, 2017 at 03:47:42PM -0700, Eric Anholt wrote: >> From: Tom Cooksey >> >> This is a modesetting driver for the pl111 CLCD display controller >> found on various ARM platforms such as the Versatile Express. The >> driver has only been tested on the bcm911360

Re: [PATCH] drm/gma500: fix memory leak on edid

2017-03-20 Thread walter harms
Am 20.03.2017 18:56, schrieb Colin King: > From: Colin Ian King > > edid is allocated on the call to psb_intel_sdvo_get_edid but not > kfree'd at all, causing a memory leak. Fix this by kfree'ing > the edid. (This may be null, but kfree can handle null frees). > > Detected by CoverityScan, C

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-20 Thread Matt Turner
On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov wrote: > Seems like we ended up all over the place, so let me try afresh. > > Above all: > - Saying "I don't care" about your users is arrogant - let us _not_ > do that, please ? Let's be honest, the OpenBSD is subjecting itself to some pretty arbitr

[PATCH] gpu: host1x: Refactor/fix channel allocation code

2017-03-20 Thread Mikko Perttunen
This is largely a rewrite of the Host1x channel allocation code in channel.c, bringing several changes: - The previous code could deadlock due to an interaction between the 'reflock' mutex and CDMA timeout handling. This gets rid of the mutex. - In the future, per-user channel allocation will

Re: GEM allocation for para-virtualized DRM driver

2017-03-20 Thread Rob Clark
On Mon, Mar 20, 2017 at 2:25 PM, Oleksandr Andrushchenko wrote: > On 03/20/2017 08:17 PM, Rob Clark wrote: >> >> On Mon, Mar 20, 2017 at 2:01 PM, Oleksandr Andrushchenko >> wrote: >>> >>> On 03/20/2017 07:38 PM, Rob Clark wrote: On Mon, Mar 20, 2017 at 1:18 PM, Oleksandr Andrushchenko >

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-20 Thread Rob Clark
On Mon, Mar 20, 2017 at 9:55 AM, Emil Velikov wrote: > Seems like we ended up all over the place, so let me try afresh. > > Above all: > - Saying "I don't care" about your users is arrogant - let us _not_ > do that, please ? > Even Linux distribution maintainers have responded that "upstream does

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-20 Thread Emil Velikov
On 20 March 2017 at 18:30, Matt Turner wrote: > On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov > wrote: >> Seems like we ended up all over the place, so let me try afresh. >> >> Above all: >> - Saying "I don't care" about your users is arrogant - let us _not_ >> do that, please ? > > Let's be ho

Re: [PATCH 01/41] drm/panel: simple: Change mode for Sharp lq123p1jx31

2017-03-20 Thread Stéphane Marchesin
On Mon, Mar 20, 2017 at 9:37 AM, Doug Anderson wrote: > Hi, > > On Mon, Mar 20, 2017 at 6:59 AM, Thierry Reding > wrote: > > On Thu, Mar 09, 2017 at 11:32:16PM -0500, Sean Paul wrote: > >> Change the mode for Sharp lq123p1jx31 panel to something more > >> rockchip-friendly such that we can use t

Re: [PATCH 01/41] drm/panel: simple: Change mode for Sharp lq123p1jx31

2017-03-20 Thread Doug Anderson
Hi, On Mon, Mar 20, 2017 at 1:01 PM, Stéphane Marchesin wrote: >> 1. We have validated with the panel manufacturer that 266.667 MHz is >> valid and within spec. The panel's datasheet itself says something >> like "if you want to try other values you can, but they might not >> work", so technical

[Bug 100270] power usage increase by approx 4W between kernel 4.7.8 and 4.8.5

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100270 brett.hass...@gmail.com changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comm

[PATCH] drm/i915: use static const array for PICK macro

2017-03-20 Thread Arnd Bergmann
The varargs macro trick in _PIPE3/_PHY3/_PORT3 was meant as an optimization to shrink the i915 kernel module by around 1000 bytes. However, the downside is a size regression with CONFIG_KASAN, as I found from stack size warnings with gcc-7.0.1: before: drivers/gpu/drm/i915/intel_dpll_mgr.c: In fun

Re: [PATCH v3 5/9] gpu: ipu-v3: document valid IPUv3 compatibles and extend for i.MX6 QuadPlus

2017-03-20 Thread Rob Herring
On Tue, Mar 14, 2017 at 11:38:44AM +0100, Philipp Zabel wrote: > From: Lucas Stach > > Document the valid compatible strings for the IPUv3. > > On i.MX6 QuadPlus the IPU needs to know which PRG has to be > used for this IPU instance. Add a "fsl,prg" property containing > a phandle pointing to th

[Bug 100288] clover unable to run OpenCL kernels since 03127bb radeonsi: compile all TGSI compute shaders asynchronously

2017-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100288 --- Comment #1 from Marek Olšák --- It should be fixed by: https://cgit.freedesktop.org/mesa/mesa/commit/?id=827ae79b2cQ6cf53e26b3467e4c3965ce6acab3c6 -- You are receiving this mail because: You are the assignee for the bug.___

[PATCH v3 3/3] drm: Clarify the role of plane_state argument to drm_simple update().

2017-03-20 Thread Eric Anholt
Like the atomic update hook it's wrapping, the plane_state is the old one, and the new one is in plane->state. Both msxfb and tinydrm use it correctly, but I mistook it for the new state in pl111 due to its naming. Signed-off-by: Eric Anholt --- drivers/gpu/drm/drm_simple_kms_helper.c | 4 ++--

[PATCH v3 2/3] drm/pl111: Initial drm/kms driver for pl111

2017-03-20 Thread Eric Anholt
From: Tom Cooksey This is a modesetting driver for the pl111 CLCD display controller found on various ARM platforms such as the Versatile Express. The driver has only been tested on the bcm911360_entphn platform so far, with PRIME-based buffer sharing between vc4 and clcd. It reuses the existing

[PATCH v3 1/3] video: ARM CLCD: Move registers to a separate header.

2017-03-20 Thread Eric Anholt
We'd like to reuse these register definitions for the DRM CLCD driver, but there's a bunch of fbdev-specific code in the current header. Signed-off-by: Eric Anholt --- include/linux/amba/clcd-regs.h | 76 ++ include/linux/amba/clcd.h | 68 +---

linux-next: manual merge of the drm tree with the drm-intel-fixes tree

2017-03-20 Thread Stephen Rothwell
Hi Dave, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/i915/gvt/cmd_parser.c between commit: 695fbc08d80f ("drm/i915/gvt: replace the gvt_err with gvt_vgpu_err") from the drm-intel-fixes tree and commit: 73dec95e6ba3 ("drm/i915: Emit to ringbuffer directly"

Re: [PATCHv2 03/10] Revert "drm: omapdrm: Remove manual update display support"

2017-03-20 Thread Tony Lindgren
* Tomi Valkeinen [170320 09:38]: > On 20/03/17 18:14, Tony Lindgren wrote: > > * Tomi Valkeinen [170320 04:10]: > >> On 05/03/17 02:43, Sebastian Reichel wrote: > >>> This reverts commit 5a35876e2830511cb8110667fc426c6a6165a593. > >>> > >>> Revert the removal of manual update display support in >

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-20 Thread Timothy Arceri
On 21/03/17 06:39, Emil Velikov wrote: On 20 March 2017 at 18:30, Matt Turner wrote: On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov wrote: Seems like we ended up all over the place, so let me try afresh. Above all: - Saying "I don't care" about your users is arrogant - let us _not_ do that

  1   2   >