[RFC] drm: Add AMD GFX9+ format modifiers.

2019-10-16 Thread Bas Nieuwenhuizen
This adds initial format modifiers for AMD GFX9 and newer GPUs. This is particularly useful to determine if we can use DCC, and whether we need an extra display compatible DCC metadata plane. Design decisions: - Always expose a single plane This way everything works correctly with images

Re: [PATCH v6 5/8] drm: rcar-du: crtc: Control CMM operations

2019-10-16 Thread Laurent Pinchart
Hi Jacopo, Thank you for the patch. On Wed, Oct 16, 2019 at 10:55:45AM +0200, Jacopo Mondi wrote: > Implement CMM handling in the crtc begin and enable atomic callbacks, > and enable CMM unit through the Display Extensional Functions > register at group setup time. > > Reviewed-by: Kieran Bingha

[PATCH V5 3/3] ARM: logicpd-torpedo-37xx-devkit-28: Reference new DRM panel

2019-10-16 Thread Adam Ford
With the removal of the panel-dpi from the omap drivers, the LCD no longer works. This patch points the device tree to a newly created panel named "logicpd,type28" Fixes: 8bf4b1621178 ("drm/omap: Remove panel-dpi driver") Signed-off-by: Adam Ford Acked-by: Sam Ravnborg --- V5: No Change V4:

[PATCH V5 1/3] drm/panel: simple: Add Logic PD Type 28 display support

2019-10-16 Thread Adam Ford
Previously, there was an omap panel-dpi driver that would read generic timings from the device tree and set the display timing accordingly. This driver was removed so the screen no longer functions. This patch modifies the panel-simple file to setup the timings to the same values previously used.

[PATCH V5 2/3] dt-bindings: Add Logic PD Type 28 display panel

2019-10-16 Thread Adam Ford
This patch adds documentation of device tree bindings for the WVGA panel Logic PD Type 28 display. Signed-off-by: Adam Ford --- V5: Replace GPIO_ACTIVE_HIGH with 0 to fix make dt_binding_check -k V4: Update per Rob H's suggestions and copy other panel yaml example from 5.4-rc1 V3: Correct bui

Re: [PATCH V4 2/3] dt-bindings: Add Logic PD Type 28 display panel

2019-10-16 Thread Adam Ford
On Wed, Oct 16, 2019 at 8:15 AM Rob Herring wrote: > > On Tue, Oct 15, 2019 at 6:04 PM Adam Ford wrote: > > > > On Wed, Oct 9, 2019 at 6:31 PM Rob Herring wrote: > > > > > > On Tue, Oct 01, 2019 at 06:39:22PM -0500, Adam Ford wrote: > > > > This patch adds documentation of device tree bindings f

Re: [PATCH 1/4] dma-buf: change DMA-buf locking convention

2019-10-16 Thread Daniel Vetter
On Wed, Oct 16, 2019 at 3:46 PM Koenig, Christian wrote: > > Am 08.10.19 um 10:55 schrieb Daniel Vetter: > > On Wed, Oct 02, 2019 at 08:37:50AM +, Koenig, Christian wrote: > >> Hi Daniel, > >> > >> once more a ping on this. Any more comments or can we get it comitted? > > Sorry got a bit smash

[Bug 204241] amdgpu fails to resume from suspend

2019-10-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204241 --- Comment #32 from m...@cschwarz.com --- @Alex: Didn't have a crash with the old uvd6 patch (attachment 285473) so far, but apparently I am just lucky. Which patch (series?) should I test now? -- You are receiving this mail because: You are w

[PATCH 1/2] drm/etnaviv: fix deadlock in GPU coredump

2019-10-16 Thread Lucas Stach
The GPU coredump function violates the locking order by holding the MMU context lock while trying to acquire the etnaviv_gem_object lock. This results in a possible ABBA deadlock with other codepaths which follow the established locking order. Fortunately this is easy to fix by dropping the MMU con

[PATCH 2/2] drm/etnaviv: reinstate MMUv1 command buffer window check

2019-10-16 Thread Lucas Stach
The switch to per-process address spaces erroneously dropped the check which validated that the command buffer is mapped through the linear apperture as required by the hardware. This turned a system misconfiguration with a helpful error message into a very hard to debug issue. Reinstate the check

[Bug 204241] amdgpu fails to resume from suspend

2019-10-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204241 --- Comment #33 from Alex Deucher (alexdeuc...@gmail.com) --- (In reply to me from comment #32) > @Alex: Didn't have a crash with the old uvd6 patch (attachment 285473 > [details]) so far, but apparently I am just lucky. > > Which patch (series?)

Re: [PATCH v5 4/4] drm/komeda: Adds gamma and color-transform support for DOU-IPS

2019-10-16 Thread Mihail Atanassov
On Wednesday, 16 October 2019 11:34:30 BST james qian wang (Arm Technology China) wrote: > From: "Lowry Li (Arm Technology China)" > > Adds gamma and color-transform support for DOU-IPS. > Adds two caps members fgamma_coeffs and ctm_coeffs to komeda_improc_state. > If color management changed, s

Re: [PATCH V5 2/3] dt-bindings: Add Logic PD Type 28 display panel

2019-10-16 Thread Laurent Pinchart
Hi Adam, Thank you for the patch. On Wed, Oct 16, 2019 at 08:51:46AM -0500, Adam Ford wrote: > This patch adds documentation of device tree bindings for the WVGA panel > Logic PD Type 28 display. > > Signed-off-by: Adam Ford > --- > V5: Replace GPIO_ACTIVE_HIGH with 0 to fix make dt_binding_ch

[PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-10-16 Thread Karol Herbst
Fixes state transitions of Nvidia Pascal GPUs from D3cold into higher device states. v2: convert to pci_dev quirk put a proper technical explanation of the issue as a in-code comment v3: disable it only for certain combinations of intel and nvidia hardware Signed-off-by: Karol Herbst Cc: Bjo

Re: [PATCH V5 2/3] dt-bindings: Add Logic PD Type 28 display panel

2019-10-16 Thread Adam Ford
On Wed, Oct 16, 2019 at 9:40 AM Laurent Pinchart wrote: > > Hi Adam, > > Thank you for the patch. > > On Wed, Oct 16, 2019 at 08:51:46AM -0500, Adam Ford wrote: > > This patch adds documentation of device tree bindings for the WVGA panel > > Logic PD Type 28 display. > > > > Signed-off-by: Adam Fo

Re: [PATCH v4 08/11] drm/ttm: add drm_gem_ttm_mmap()

2019-10-16 Thread Daniel Vetter
On Wed, Oct 16, 2019 at 01:52:00PM +0200, Gerd Hoffmann wrote: > Add helper function to mmap ttm bo's using &drm_gem_object_funcs.mmap(). > > Note that with this code path access verification is done by > drm_gem_mmap() (which calls drm_vma_node_is_allowed(()). > The &ttm_bo_driver.verify_access()

[PATCH v4] dt-bindings: display: renesas: du: Document optional reset properties

2019-10-16 Thread Geert Uytterhoeven
Document the optional properties for describing module resets, to support resetting display channels on R-Car Gen2 and Gen3. Signed-off-by: Geert Uytterhoeven Acked-by: Laurent Pinchart Acked-by: Rob Herring --- v4: - Use "All but R8A7779" instead of "R8A779[0123456]", to reduce future ch

Re: [RFC,3/3] drm/komeda: Allow non-component drm_bridge only endpoints

2019-10-16 Thread Mihail Atanassov
Hi James, On Wednesday, 9 October 2019 06:54:15 BST james qian wang (Arm Technology China) wrote: > On Fri, Oct 04, 2019 at 02:34:42PM +, Mihail Atanassov wrote: > > To support transmitters other than the tda998x, we need to allow > > non-component framework bridges to be attached to a dummy

Re: [PATCH] drm: Funnel drm logs to tracepoints

2019-10-16 Thread Sean Paul
On Wed, Oct 16, 2019 at 03:23:45PM +0200, Thomas Zimmermann wrote: > Hi > > Am 16.10.19 um 15:05 schrieb Pekka Paalanen: > > On Wed, 16 Oct 2019 00:35:39 +0200 > > Daniel Vetter wrote: > > > >> Yeah I don't think tuning the spam level will ever work. What we need > >> is some external input (mos

Re: [PATCH v2 05/11] drm/tinydrm: Remove tinydrm_spi_max_transfer_size()

2019-10-16 Thread Andy Shevchenko
On Tue, Oct 15, 2019 at 05:57:20PM +0200, Daniel Vetter wrote: > On Tue, Oct 15, 2019 at 05:41:53PM +0200, Noralf Trønnes wrote: > > Den 15.10.2019 16.32, skrev Andy Shevchenko: > > > On Fri, Jul 19, 2019 at 05:59:10PM +0200, Noralf Trønnes wrote: > > >> spi-bcm2835 can handle >64kB buffers now so

Re: [PATCHv8 1/2] drm: tda998x: use cec_notifier_conn_(un)register

2019-10-16 Thread Russell King - ARM Linux admin
On Wed, Oct 16, 2019 at 03:39:15PM +0200, Hans Verkuil wrote: > From: Dariusz Marcinkiewicz > > Use the new cec_notifier_conn_(un)register() functions to > (un)register the notifier for the HDMI connector. > > Signed-off-by: Dariusz Marcinkiewicz > Signed-off-by: Hans Verkuil Please explain i

Re: [PATCH -next] drm/amd/display: Make dc_link_detect_helper static

2019-10-16 Thread Alex Deucher
On Wed, Oct 16, 2019 at 8:29 AM YueHaibing wrote: > > Fix sparse warning: > > drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:746:6: > warning: symbol 'dc_link_detect_helper' was not declared. Should it be > static? > > Reported-by: Hulk Robot > Signed-off-by: YueHaibing Applied. tha

Re: [RFC,3/3] drm/komeda: Allow non-component drm_bridge only endpoints

2019-10-16 Thread Brian Starkey
Hi, On Wed, Oct 16, 2019 at 03:51:39PM +, Mihail Atanassov wrote: > Hi James, > > On Wednesday, 9 October 2019 06:54:15 BST james qian wang (Arm Technology > China) wrote: > > On Fri, Oct 04, 2019 at 02:34:42PM +, Mihail Atanassov wrote: > > > To support transmitters other than the tda99

Re: [PATCHv8 2/2] drm: tda998x: set the connector info

2019-10-16 Thread Russell King - ARM Linux admin
On Wed, Oct 16, 2019 at 03:39:16PM +0200, Hans Verkuil wrote: > From: Dariusz Marcinkiewicz > > Fill in the cec_connector_info when calling cec_notifier_conn_register(). > > Signed-off-by: Dariusz Marcinkiewicz > Tested-by: Hans Verkuil > Signed-off-by: Hans Verkuil > --- > drivers/gpu/drm/i

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

2019-10-16 Thread Alex Deucher
Applied. Thanks! Alex On Tue, Oct 15, 2019 at 8:22 PM Stephen Rothwell wrote: > > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/gpu/drm/amd/amdgpu/amdgpu_tmz.c:23:10: fatal error: drm/drmP.h: No > such file or direct

Re: [PATCH V3 4/7] mdev: introduce device specific ops

2019-10-16 Thread Alex Williamson
On Wed, 16 Oct 2019 15:31:25 + Parav Pandit wrote: > > -Original Message- > > From: Cornelia Huck > > Sent: Wednesday, October 16, 2019 3:53 AM > > To: Parav Pandit > > Cc: Alex Williamson ; Jason Wang > > ; k...@vger.kernel.org; linux-s...@vger.kernel.org; > > linux-ker...@vger.ker

[PATCH v2] drm: Generalized NV Block Linear DRM format mod

2019-10-16 Thread James Jones
Builds upon the existing NVIDIA 16Bx2 block linear format modifiers by adding more "fields" to the existing parameterized DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier macro that allow fully defining a unique-across- all-NVIDIA-hardware bit layout using a minimal set of fields and values. The

Re: [PATCH] drm: Generalized NV Block Linear DRM format mod

2019-10-16 Thread James Jones
On 10/15/19 8:42 AM, Daniel Vetter wrote: On Tue, Oct 15, 2019 at 5:14 PM James Jones wrote: On 10/15/19 7:19 AM, Daniel Vetter wrote: On Mon, Oct 14, 2019 at 03:13:21PM -0700, James Jones wrote: Builds upon the existing NVIDIA 16Bx2 block linear format modifiers by adding more "fields" to t

Re: [RFC] new uapi policy for drm

2019-10-16 Thread Matt Roper
On Tue, Oct 15, 2019 at 04:16:00AM +1000, Dave Airlie wrote: > I've kicked this around in my head over the past few weeks but wanted > to get some feedback on whether it's a good idea or what impact it > might have that I haven't considered. > > We are getting requests via both amdgpu/amdkfd and i

[Bug 204241] amdgpu fails to resume from suspend

2019-10-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204241 --- Comment #34 from a...@tutanota.com --- (In reply to Alex Deucher from comment #29) > Created attachment 285507 [details] > possible fix for uvd6 > > The session info is 128K according to mesa. This version of the patch didn't fail for 100 su

[Bug 109628] WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()

2019-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109628 --- Comment #30 from peter m --- kernel 5.3.5-200.fc30.x86_64 (mockbu...@bkernel04.phx2.fedoraproject.org) xfce - 4.14 kernel still crushing [ cut here ] WARNING: CPU: 2 PID: 184 at drivers/gpu/drm/amd/amdgpu/../display

Re: [RESEND][PATCH v8 0/5] DMA-BUF Heaps (destaging ION)

2019-10-16 Thread John Stultz
On Wed, Oct 9, 2019 at 10:38 AM Ayan Halder wrote: > > On Tue, Sep 24, 2019 at 04:22:18PM +, Ayan Halder wrote: > > On Thu, Sep 19, 2019 at 10:21:52PM +0530, Sumit Semwal wrote: > > > Hello Christoph, everyone, > > > > > > On Sat, 7 Sep 2019 at 00:17, John Stultz wrote: > > > > > > > > Here i

Re: [RESEND][PATCH v8 0/5] DMA-BUF Heaps (destaging ION)

2019-10-16 Thread Andrew F. Davis
On 10/14/19 5:07 AM, Brian Starkey wrote: > Hi Andrew, > > On Wed, Oct 09, 2019 at 02:27:15PM -0400, Andrew F. Davis wrote: >> The CMA driver that registers these nodes will have to be expanded to >> export them using this framework as needed. We do something similar to >> export SRAM nodes: >> >>

Re: [PATCH v2 05/11] drm/tinydrm: Remove tinydrm_spi_max_transfer_size()

2019-10-16 Thread Daniel Vetter
On Wed, Oct 16, 2019 at 6:13 PM Andy Shevchenko wrote: > > On Tue, Oct 15, 2019 at 05:57:20PM +0200, Daniel Vetter wrote: > > On Tue, Oct 15, 2019 at 05:41:53PM +0200, Noralf Trønnes wrote: > > > Den 15.10.2019 16.32, skrev Andy Shevchenko: > > > > On Fri, Jul 19, 2019 at 05:59:10PM +0200, Noralf

[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

2019-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111481 --- Comment #97 from Shmerl --- Unfortunately I just got a random sdma Firefox hang, with that bitmask fix enabled. I didn't enable other two patches above though. Building the 5.4-rc3 with all three applied now. -- You are receiving this mail

Re: [PATCH v2 05/11] drm/tinydrm: Remove tinydrm_spi_max_transfer_size()

2019-10-16 Thread Mark Brown
On Wed, Oct 16, 2019 at 07:44:51PM +0200, Daniel Vetter wrote: > On Wed, Oct 16, 2019 at 6:13 PM Andy Shevchenko > > On Tue, Oct 15, 2019 at 05:57:20PM +0200, Daniel Vetter wrote: > > > Something like this, as a test patch. > > max_transfer_size should be a function. In that case it works. > Why

[PATCH] drm: Move radeon and amdgpu Kconfig options into their directories

2019-10-16 Thread Andrew F. Davis
Most Kconfig options to enable a driver are in the Kconfig file inside the relevant directory, move these two to the same. Signed-off-by: Andrew F. Davis --- drivers/gpu/drm/Kconfig| 34 -- drivers/gpu/drm/amd/amdgpu/Kconfig | 18 drivers/

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-10-16 Thread Bjorn Helgaas
On Wed, Oct 16, 2019 at 04:44:49PM +0200, Karol Herbst wrote: > Fixes state transitions of Nvidia Pascal GPUs from D3cold into higher device > states. > > v2: convert to pci_dev quirk > put a proper technical explanation of the issue as a in-code comment > v3: disable it only for certain combi

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-10-16 Thread Karol Herbst
but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the platform means of putting the device into D3cold, right? That's actually what should still happen, just the D3hot step should be skipped. On Wed, Oct 16, 2019 at 9:14 PM Bjorn Helgaas wrote: > > On Wed, Oct 16, 2019 at 04:44:49PM +02

Re: [PATCH 1/2] drm/shmem: Add madvise state and purge helpers

2019-10-16 Thread Sean Paul
On Mon, Aug 05, 2019 at 08:33:57AM -0600, Rob Herring wrote: > Add support to the shmem GEM helpers for tracking madvise state and > purging pages. This is based on the msm implementation. > > The BO provides a list_head, but the list management is handled outside > of the shmem helpers as there a

Re: [RFC] new uapi policy for drm

2019-10-16 Thread Stéphane Marchesin
On Wed, Oct 16, 2019 at 10:28 AM Matt Roper wrote: > > On Tue, Oct 15, 2019 at 04:16:00AM +1000, Dave Airlie wrote: > > I've kicked this around in my head over the past few weeks but wanted > > to get some feedback on whether it's a good idea or what impact it > > might have that I haven't conside

[PATCH] spi: pxa2xx: Set controller->max_transfer_size in dma mode

2019-10-16 Thread Daniel Vetter
In DMA mode we have a maximum transfer size, past that the driver falls back to PIO (see the check at the top of pxa2xx_spi_transfer_one). Falling back to PIO for big transfers defeats the point of a dma engine, hence set the max transfer size to inform spi clients that they need to do something sm

Re: [PATCH 28/34] drm/i810: Refer to `PREEMPTION' in comment

2019-10-16 Thread Daniel Vetter
On Tue, Oct 15, 2019 at 09:18:15PM +0200, Sebastian Andrzej Siewior wrote: > The dependency has been changed from `PREEMPT' to `PREEMPTION'. Reflect > this change in the comment. > > Use `PREEMPTION' in the comment. > > Cc: Maarten Lankhorst > Cc: Maxime Ripard > Cc: Sean Paul > Cc: David Airl

Re: [RFC] new uapi policy for drm

2019-10-16 Thread Alex Deucher
On Mon, Oct 14, 2019 at 2:16 PM Dave Airlie wrote: > > I've kicked this around in my head over the past few weeks but wanted > to get some feedback on whether it's a good idea or what impact it > might have that I haven't considered. > > We are getting requests via both amdgpu/amdkfd and i915 for

Re: [RFC] new uapi policy for drm

2019-10-16 Thread Sean Paul
On Tue, Oct 15, 2019 at 04:16:00AM +1000, Dave Airlie wrote: > I've kicked this around in my head over the past few weeks but wanted > to get some feedback on whether it's a good idea or what impact it > might have that I haven't considered. > > We are getting requests via both amdgpu/amdkfd and i

Re: [v5 1/2] dt/bindings: display: Add optional property node define for Mali DP500

2019-10-16 Thread Sean Paul
On Tue, Sep 10, 2019 at 4:10 AM Wen He wrote: > > Add optional property node 'arm,malidp-arqos-value' for the Mali DP500. > This property describe the ARQoS levels of DP500's QoS signaling. > > Signed-off-by: Wen He > Reviewed-by: Rob Herring Liviu, I see you applied 2/2, but didn't apply this

Re: [PATCH] spi: pxa2xx: Set controller->max_transfer_size in dma mode

2019-10-16 Thread Noralf Trønnes
Den 16.10.2019 21.57, skrev Daniel Vetter: > In DMA mode we have a maximum transfer size, past that the driver > falls back to PIO (see the check at the top of pxa2xx_spi_transfer_one). > Falling back to PIO for big transfers defeats the point of a dma engine, > hence set the max transfer size to

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-10-16 Thread Bjorn Helgaas
[+cc linux-acpi] On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote: > but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the > platform means of putting the device into D3cold, right? That's > actually what should still happen, just the D3hot step should be > skipped. If I und

Re: [RFC] new uapi policy for drm

2019-10-16 Thread Dave Airlie
On Thu, 17 Oct 2019 at 06:00, Alex Deucher wrote: > > On Mon, Oct 14, 2019 at 2:16 PM Dave Airlie wrote: > > > > I've kicked this around in my head over the past few weeks but wanted > > to get some feedback on whether it's a good idea or what impact it > > might have that I haven't considered. >

[ANNOUNCE] libdrm 2.4.100

2019-10-16 Thread Marek Olšák
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Anusha Srivatsa (1): intel: sync i915_pciids.h with kernel Emil Velikov (1): *-symbols-check: use normal shell over bash Eric Engestrom (7): xf86drm: dedupe `#define`s xf86drm: use max size of drm node name instead of arbit

Re: [RFC] new uapi policy for drm

2019-10-16 Thread Dave Airlie
On Thu, 17 Oct 2019 at 03:28, Matt Roper wrote: > > On Tue, Oct 15, 2019 at 04:16:00AM +1000, Dave Airlie wrote: > > I've kicked this around in my head over the past few weeks but wanted > > to get some feedback on whether it's a good idea or what impact it > > might have that I haven't considered

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-10-16 Thread Karol Herbst
On Wed, Oct 16, 2019 at 11:37 PM Bjorn Helgaas wrote: > > [+cc linux-acpi] > > On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote: > > but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the > > platform means of putting the device into D3cold, right? That's > > actually what sho

Re: [PATCH] spi: pxa2xx: Set controller->max_transfer_size in dma mode

2019-10-16 Thread Mark Brown
On Wed, Oct 16, 2019 at 11:30:51PM +0200, Noralf Trønnes wrote: > As Andy mentioned, ->max_transfer_size is a callback: > struct spi_controller { > /* >* on some hardware transfer / message size may be constrained >* the limit may depend on device transfer settings >

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-10-16 Thread Bjorn Helgaas
On Wed, Oct 16, 2019 at 11:48:22PM +0200, Karol Herbst wrote: > On Wed, Oct 16, 2019 at 11:37 PM Bjorn Helgaas wrote: > > On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote: > > > but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the > > > platform means of putting the device i

[Bug 204241] amdgpu fails to resume from suspend

2019-10-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204241 --- Comment #35 from Andreas Jackisch (andreas.jacki...@gmail.com) --- (In reply to Ahzo from comment #34) > (In reply to Alex Deucher from comment #29) > > Created attachment 285507 [details] > > possible fix for uvd6 > > > > The session info

Re: [PATCH V3 4/7] mdev: introduce device specific ops

2019-10-16 Thread Alex Williamson
On Wed, 16 Oct 2019 20:48:06 + Parav Pandit wrote: > > From: Alex Williamson > > On Wed, 16 Oct 2019 15:31:25 + > > Parav Pandit wrote: > > > > From: Cornelia Huck > > > > Parav Pandit wrote: > > > > > > From: Alex Williamson > > > > > > On Tue, 15 Oct 2019 20:17:01 +0800 Jason Wang

[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

2019-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111481 --- Comment #98 from David Biró --- Recently, I've just become an RX 5700 xt user, with the same issues, but for me the keyboard and the mouse also dies after those errors. ( There is a Caps Lock indicator led, but after the error I can't toggle

[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

2019-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111481 --- Comment #99 from Shmerl --- (In reply to David Biró from comment #98) > > Can I help you somehow? (Unfortunately, I've got no idea how can I patch a > kernel module on Arch.) On Debian testing, I simply build a whole kernel, applying neede

Re: [PATCH V3 0/7] mdev based hardware virtio offloading support

2019-10-16 Thread Jason Wang
On 2019/10/15 下午10:37, Stefan Hajnoczi wrote: On Tue, Oct 15, 2019 at 11:37:17AM +0800, Jason Wang wrote: On 2019/10/15 上午1:49, Stefan Hajnoczi wrote: On Fri, Oct 11, 2019 at 04:15:50PM +0800, Jason Wang wrote: There are hardware that can do virtio datapath offloading while having its own co

[pull] amdgpu, radeon drm-fixes-5.4

2019-10-16 Thread Alex Deucher
Hi Dave, Daniel, A few fixes for 5.4. Nothing too major. The following changes since commit 083164dbdb17c5ea4ad92c1782b59c9d75567790: drm/amdgpu: fix memory leak (2019-10-09 11:45:59 -0500) are available in the Git repository at: git://people.freedesktop.org/~agd5f/linux tags/drm-fixes-5.

Re: [RFC,3/3] drm/komeda: Allow non-component drm_bridge only endpoints

2019-10-16 Thread james qian wang (Arm Technology China)
On Wed, Oct 16, 2019 at 04:22:07PM +, Brian Starkey wrote: > Hi, > > On Wed, Oct 16, 2019 at 03:51:39PM +, Mihail Atanassov wrote: > > Hi James, > > > > On Wednesday, 9 October 2019 06:54:15 BST james qian wang (Arm Technology > > China) wrote: > > > On Fri, Oct 04, 2019 at 02:34:42PM +0

[Bug 112038] [All browsers] The number of countries and regions text for activities is poorly read on the region pages

2019-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112038 Bug ID: 112038 Summary: [All browsers] The number of countries and regions text for activities is poorly read on the region pages Product: DRI Version: XOrg git Hardware:

[Bug 112038] [All browsers] The number of countries and regions text for activities is poorly read on the region pages

2019-10-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112038 Andre Klapper changed: What|Removed |Added Resolution|--- |INVALID Group|

[PATCH] spi: pxa2xx: Set controller->max_transfer_size in dma mode

2019-10-16 Thread Daniel Vetter
In DMA mode we have a maximum transfer size, past that the driver falls back to PIO (see the check at the top of pxa2xx_spi_transfer_one). Falling back to PIO for big transfers defeats the point of a dma engine, hence set the max transfer size to inform spi clients that they need to do something sm

Re: [PATCH v2 05/11] drm/tinydrm: Remove tinydrm_spi_max_transfer_size()

2019-10-16 Thread Andy Shevchenko
On Wed, Oct 16, 2019 at 07:44:51PM +0200, Daniel Vetter wrote: > On Wed, Oct 16, 2019 at 6:13 PM Andy Shevchenko > wrote: > > On Tue, Oct 15, 2019 at 05:57:20PM +0200, Daniel Vetter wrote: > > max_transfer_size should be a function. In that case it works. > > Why do you want to make it a functio

<    1   2