Re: [PATCH] dma-buf: rename reservation_object to dma_resv

2019-08-14 Thread Sumit Semwal
Hello Christian, On Sun, 11 Aug 2019 at 14:48, Chris Wilson wrote: > Quoting Christian König (2019-08-11 09:56:01) > > Be more consistent with the naming of the other DMA-buf objects. > > From the tip of my fingers, \o/ > > > Signed-off-by: Christian König > Thanks for doing this! Acked-by:

RE: [EXT] Re: [v2 2/3] dt/bindings: display: Add optional property node defined for Mali DP500

2019-08-14 Thread Wen He
> -Original Message- > From: Rob Herring > Sent: 2019年8月13日 7:20 > To: Wen He > Cc: linux-ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; > devicet...@vger.kernel.org; mark.rutl...@arm.com; liviu.du...@arm.com; > brian.star...@arm.com; airl...@linux.ie; dan...@ffwll.ch; Leo Li

[Bug 110886] After S3 resume, kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:57:crtc-0] flip_done timed out

2019-08-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110886 --- Comment #10 from Samantha McVey --- I am getting this same issue (at least I believe the same). It is in the 5.2 series but not in the 5.1 series of the kernel. If needed I can post my logs. I have Lenovo A485 w/ 2700U -- You are

[git pull] vmwgfx-next

2019-08-14 Thread VMware
From: Thomas Hellstrom (VMware) Dave, Daniel A couple of independent patches extracted from the 5.3 pull request, fixed for merge conflicts. And the drmP.h removal from Sam. /Thomas The following changes since commit e7f7287bf5f746d29f3607178851246a005dd398: Merge tag

Re: [PATCH RFC 14/19] drm/bridge: Add the necessary bits to support bus format negotiation

2019-08-14 Thread Neil Armstrong
On 08/08/2019 17:11, Boris Brezillon wrote: > This takes the form of various helpers, plus the addition of 2 new > structs: > * drm_bus_caps: describe the bus capabilities of a bridge/encoder. For > bridges we have one for the input port and one for the output port. > Encoders just have one

Re: [PATCH 08/60] drm/bridge: Extend bridge API to disable connector creation

2019-08-14 Thread Daniel Vetter
On Thu, Aug 08, 2019 at 07:36:49PM +0200, Andrzej Hajda wrote: > On 08.08.2019 16:25, Laurent Pinchart wrote: > > Hi Andrzej, > > > > On Wed, Jul 17, 2019 at 08:39:47AM +0200, Andrzej Hajda wrote: > >> On 07.07.2019 20:18, Laurent Pinchart wrote: > >>> Most bridge drivers create a DRM connector to

Re: [PATCH] m68k: atari: Rename shifter to shifter_st to avoid conflict

2019-08-14 Thread Linus Walleij
On Mon, Aug 12, 2019 at 9:30 AM Geert Uytterhoeven wrote: > When test-compiling the BCM2835 pin control driver on m68k: > > In file included from arch/m68k/include/asm/io_mm.h:32:0, > from arch/m68k/include/asm/io.h:8, > from include/linux/io.h:13, >

Re: [PATCH 09/60] drm/bridge: Add connector-related bridge operations and data

2019-08-14 Thread Andrzej Hajda
Hi Laurent, Sorry for late response. On 11.08.2019 00:43, Laurent Pinchart wrote: > Hi Andrzej, > > On Fri, Aug 09, 2019 at 01:55:53PM +0200, Andrzej Hajda wrote: >> On 08.08.2019 21:32, Laurent Pinchart wrote: >>> On Tue, Jul 16, 2019 at 03:57:21PM +0200, Andrzej Hajda wrote: On

Re: [PATCH v13 14/18] kunit: defconfig: add defconfigs for building KUnit tests

2019-08-14 Thread Stephen Boyd
Quoting Brendan Higgins (2019-08-13 22:51:04) > Add defconfig for UML and a fragment that can be used to configure other > architectures for building KUnit tests. Add option to kunit_tool to use > a defconfig to create the kunitconfig. > > Signed-off-by: Brendan Higgins > Reviewed-by: Greg

Re: [PATCH v13 12/18] kunit: test: add tests for KUnit managed resources

2019-08-14 Thread Stephen Boyd
Quoting Brendan Higgins (2019-08-13 22:51:02) > From: Avinash Kondareddy > > Add unit tests for KUnit managed resources. KUnit managed resources > (struct kunit_resource) are resources that are automatically cleaned up > at the end of a KUnit test, similar to the concept of devm_* managed >

Re: [PATCH v13 03/18] kunit: test: add string_stream a std::stream like string builder

2019-08-14 Thread Stephen Boyd
Quoting Brendan Higgins (2019-08-13 22:50:53) > A number of test features need to do pretty complicated string printing > where it may not be possible to rely on a single preallocated string > with parameters. > > So provide a library for constructing the string as you go similar to > C++'s

[Bug 204181] NULL pointer dereference regression in amdgpu

2019-08-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204181 chirn...@hotmail.com changed: What|Removed |Added CC||chirn...@hotmail.com --- Comment

Re: [EXT] Re: [PATCH 05/10] dt-bindings: display: Add max-res property for mxsfb

2019-08-14 Thread Robert Chiras
On Lu, 2019-07-22 at 11:48 -0600, Rob Herring wrote: > On Wed, Jun 26, 2019 at 04:32:13PM +0300, Robert Chiras wrote: > > > > Add new optional property 'max-res', to limit the maximum supported > > resolution by the MXSFB_DRM driver. > Bindings are for h/w description, not driver config. > > >

Re: [PATCH v2 2/4] drm/komeda: Introduce komeda_color_manager/state

2019-08-14 Thread james qian wang (Arm Technology China)
On Tue, Aug 13, 2019 at 09:51:08AM +, Mihail Atanassov wrote: > Hi James, > > On Tuesday, 13 August 2019 05:56:07 BST james qian wang (Arm Technology > China) wrote: > > Many komeda component support color management like layer and IPS, so > > komeda_color_manager/state are introduced to

Re: linux-next: manual merge of the drm-misc tree with the drm and drm-intel trees

2019-08-14 Thread Koenig, Christian
Am 14.08.19 um 04:54 schrieb Stephen Rothwell: > Hi all, > > Today's linux-next merge of the drm-misc tree got a conflict in: > >drivers/gpu/drm/amd/amdgpu/amdgpu_object.c >drivers/gpu/drm/i915/i915_vma.c >drivers/gpu/drm/i915/i915_gem_batch_pool.c >

Re: [PATCH v13 09/18] kunit: test: add support for test abort

2019-08-14 Thread Stephen Boyd
Quoting Brendan Higgins (2019-08-13 22:50:59) > Add support for aborting/bailing out of test cases, which is needed for > implementing assertions. > > An assertion is like an expectation, but bails out of the test case > early if the assertion is not met. The idea with assertions is that you >

Re: Best practice for embedded code samles? [Was: drm/drv: Use // for comments in example code]

2019-08-14 Thread Jani Nikula
On Tue, 13 Aug 2019, Jonathan Corbet wrote: > On Sun, 11 Aug 2019 23:32:15 +0200 > Sam Ravnborg wrote: > >> I wonder if there is a better way to embed a code sample >> than reverting to // style comments. >> >> As the kernel do not like // comments we should try to avoid them in >> examples. >

Re: [PATCH v2 4/4] drm/komeda: Enable Layer color management for komeda

2019-08-14 Thread james qian wang (Arm Technology China)
On Tue, Aug 13, 2019 at 10:07:36AM +, Mihail Atanassov wrote: > Hi James, > > On Tuesday, 13 August 2019 05:56:19 BST james qian wang (Arm Technology > China) wrote: > > - D71 has 3 global layer gamma table which can be used for all layers as > > gamma lookup table, no matter inverse or

[Bug 111399] Freeze after suspend/resume with kernel 5.0

2019-08-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111399 Vladimir changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW

[Bug 110258] Lenovo V110-15AST AMD A9-9410 AMD R5 Stoney hangs after waking after suspend. 5.0 onwards

2019-08-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110258 Vladimir changed: What|Removed |Added CC||vl4d1m1...@gmail.com --- Comment #15 from

Re: [EXT] Re: [PATCH v2 12/15] drm/mxsfb: Improve the axi clock usage

2019-08-14 Thread Robert Chiras
Hi Stefan, On Mi, 2019-08-14 at 13:06 +0200, Stefan Agner wrote: > On 2019-08-14 12:48, Robert Chiras wrote: > > > > Currently, the enable of the axi clock return status is ignored, > > causing > > issues when the enable fails then we try to disable it. Therefore, > > it is > > better to check

Re: [EXT] Re: [PATCH v2 09/15] dt-bindings: display: Add max-res property for mxsfb

2019-08-14 Thread Robert Chiras
Hi Stefann, On Mi, 2019-08-14 at 13:25 +0200, Stefan Agner wrote: > On 2019-08-14 13:14, Robert Chiras wrote: > > > > Hi Stefan, > > On Mi, 2019-08-14 at 13:03 +0200, Stefan Agner wrote: > > > > > > On 2019-08-14 12:48, Robert Chiras wrote: > > > > > > > > > > > > Add new optional property

[Bug 111244] amdgpu kernel 5.2 blank display after resume from suspend

2019-08-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111244 --- Comment #24 from mib...@gmx.at --- Having the same issue on a ThinkPad T495s (BIOS 1.06) with a Ryzen 7 PRO 3700U, Kernel 5.2.8-arch1-1-ARCH, Mesa 19.1.4-1 and running sway (wayland) as a window manager. dmesg shows me: [drm] Fence fallback

Re: [PATCH v2 2/3] drm/etnaviv: allow to request specific virtual address for gem mapping

2019-08-14 Thread Guido Günther
Hi, On Fri, Aug 09, 2019 at 02:05:13PM +0200, Lucas Stach wrote: > Allow the mapping code to request a specific virtual address for the gem > mapping. If the virtual address is zero we fall back to the old mode of > allocating a virtual address for the mapping. > > Signed-off-by: Lucas Stach >

[Bug 111399] Freeze after suspend/resume with kernel 5.0

2019-08-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111399 Bug ID: 111399 Summary: Freeze after suspend/resume with kernel 5.0 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

Re: [PATCH 09/60] drm/bridge: Add connector-related bridge operations and data

2019-08-14 Thread Laurent Pinchart
Hi Andrzej, On Wed, Aug 14, 2019 at 08:23:12AM +0200, Andrzej Hajda wrote: > Hi Laurent, > > Sorry for late response. No worries. > On 11.08.2019 00:43, Laurent Pinchart wrote: > > On Fri, Aug 09, 2019 at 01:55:53PM +0200, Andrzej Hajda wrote: > >> On 08.08.2019 21:32, Laurent Pinchart wrote:

Re: [PATCH v13 00/18] kunit: introduce KUnit, the Linux kernel unit testing framework

2019-08-14 Thread Brendan Higgins
On Tue, Aug 13, 2019 at 10:52 PM Brendan Higgins wrote: > > ## TL;DR > > This revision addresses comments from Stephen and Bjorn Helgaas. Most > changes are pretty minor stuff that doesn't affect the API in anyway. > One significant change, however, is that I added support for freeing >

[PATCH v7 7/9] drm: tegra: use cec_notifier_conn_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_conn_(un)register() functions to (un)register the notifier for the HDMI connector, and fill in the cec_connector_info. Changes since v4: - only create a CEC notifier for HDMI connectors Signed-off-by: Dariusz Marcinkiewicz Tested-by: Hans Verkuil ---

[PATCH v7 8/9] drm: dw-hdmi: use cec_notifier_conn_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_conn_(un)register() functions to (un)register the notifier for the HDMI connector, and fill in the cec_connector_info. Changes since v6: - move cec_notifier_conn_unregister to a bridge detach function, - add a mutex protecting a CEC notifier.

[PATCH v7 3/9] dw-hdmi-cec: use cec_notifier_cec_adap_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_cec_adap_(un)register() functions to (un)register the notifier for the CEC adapter. Also adds CEC_CAP_CONNECTOR_INFO capability to the adapter. Changes since v3: - add CEC_CAP_CONNECTOR_INFO to cec_allocate_adapter, - replace CEC_CAP_LOG_ADDRS |

[PATCH v7 4/9] tda9950: use cec_notifier_cec_adap_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_cec_adap_(un)register() functions to (un)register the notifier for the CEC adapter. Signed-off-by: Dariusz Marcinkiewicz Signed-off-by: Hans Verkuil Tested-by: Hans Verkuil --- drivers/gpu/drm/i2c/tda9950.c | 12 ++-- 1 file changed, 6 insertions(+), 6

[PATCH v7 5/9] drm: tda998x: use cec_notifier_conn_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_conn_(un)register() functions to (un)register the notifier for the HDMI connector, and fill in the cec_connector_info. Changes since v6: - move cec_notifier_conn_unregister to tda998x_bridge_detach, - add a mutex protecting accesses to a CEC notifier.

[PATCH v7 9/9] drm: exynos: exynos_hdmi: use cec_notifier_conn_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_conn_(un)register() functions to (un)register the notifier for the HDMI connector, and fill in the cec_connector_info. Changes since v2: - removed unnecessary call to invalidate phys address before deregistering the notifier, - use

[PATCH v7 6/9] drm: sti: use cec_notifier_conn_(un)register

2019-08-14 Thread Dariusz Marcinkiewicz
Use the new cec_notifier_conn_(un)register() functions to (un)register the notifier for the HDMI connector, and fill in the cec_connector_info. Changes since v2: Don't invalidate physical address before unregistering the notifier. Signed-off-by: Dariusz Marcinkiewicz ---

Re: [PATCH v2 12/15] drm/mxsfb: Improve the axi clock usage

2019-08-14 Thread Stefan Agner
On 2019-08-14 12:48, Robert Chiras wrote: > Currently, the enable of the axi clock return status is ignored, causing > issues when the enable fails then we try to disable it. Therefore, it is > better to check the return status and disable it only when enable > succeeded. Is this actually the

Re: [EXT] Re: [PATCH v2 09/15] dt-bindings: display: Add max-res property for mxsfb

2019-08-14 Thread Robert Chiras
Hi Stefan, On Mi, 2019-08-14 at 13:03 +0200, Stefan Agner wrote: > On 2019-08-14 12:48, Robert Chiras wrote: > > > > Add new optional property 'max-res', to limit the maximum supported > > resolution by the MXSFB_DRM driver. > I would also mention the reason why we need this. > > I guess this

Re: [EXT] Re: [PATCH v2 09/15] dt-bindings: display: Add max-res property for mxsfb

2019-08-14 Thread Stefan Agner
On 2019-08-14 13:14, Robert Chiras wrote: > Hi Stefan, > On Mi, 2019-08-14 at 13:03 +0200, Stefan Agner wrote: >> On 2019-08-14 12:48, Robert Chiras wrote: >> > >> > Add new optional property 'max-res', to limit the maximum supported >> > resolution by the MXSFB_DRM driver. >> I would also mention

Re: [EXT] Re: [PATCH v2 04/15] drm/mxsfb: Reset vital register for a proper initialization

2019-08-14 Thread Robert Chiras
Hi Stefan, On Mi, 2019-08-14 at 13:11 +0200, Stefan Agner wrote: > On 2019-08-14 12:48, Robert Chiras wrote: > > > > Some of the regiters need, like LCDC_CTRL and > > CTRL2_OUTSTANDING_REQS > Typo in registers, and there is a need to many. Thanks, will fix this. > > > > > needs to be properly

Re: [PATCH v2 06/15] drm/mxsfb: Update mxsfb with additional pixel formats

2019-08-14 Thread Daniel Stone
Hi Robert, On Wed, 14 Aug 2019 at 11:49, Robert Chiras wrote: > + case DRM_FORMAT_BGR565: /* BG16 */ > + if (mxsfb->devdata->ipversion < 4) > + goto err; > + writel(CTRL2_ODD_LINE_PATTERN(CTRL2_LINE_PATTERN_BGR) | > +

[PATCH 4/7] gpu: ipu-v3: image-convert: fix image downsize coefficients and tiling calculation

2019-08-14 Thread Philipp Zabel
This patch effectively reverts commit 912bbf7e9ca4 ("gpu: ipu-v3: image-convert: Fix image downsize coefficients") and replaces it with a different solution based on the preceding patches. The previous fix tried to solve the problem of intermediate tile size between IC downsizing and main

[PATCH 6/7] gpu: ipu-v3: image-convert: move tile burst alignment out of loop

2019-08-14 Thread Philipp Zabel
Burst aligned input and output width can be calculated once per column, instead of repeatedly for each tile in the column. The same goes for input and output height per row. Also don't round up the same values repeatedly. Signed-off-by: Philipp Zabel --- drivers/gpu/ipu-v3/ipu-image-convert.c |

[PATCH 3/7] gpu: ipu-v3: image-convert: limit input seam position to hardware requirements

2019-08-14 Thread Philipp Zabel
Limit the input seam position to an interval that guarantees the tile size does not exceed 1024 pixels after the IC downsizing section and that space is left for the next tile. Signed-off-by: Philipp Zabel --- drivers/gpu/ipu-v3/ipu-image-convert.c | 30 -- 1 file

[PATCH 1/7] gpu: ipu-v3: image-convert: fix output seam valid interval

2019-08-14 Thread Philipp Zabel
This fixes a failure to determine any seam if the output size is exactly 1024 multiplied by the number of tiles in a given direction. In that case an empty interval out_start == out_end is being passed to find_best_seam, which looks for a seam out_start <= x < out_end. Also reduce the interval

[PATCH 5/7] gpu: ipu-v3: image-convert: bail on invalid tile sizes

2019-08-14 Thread Philipp Zabel
If we managed to create tiles sized 0x0 because of a bug in the seam calculation, return with an error message instead of letting the driver run into a division by zero later. Also check for tile sizes that are larger than supported by the hardware. Signed-off-by: Philipp Zabel ---

[PATCH 2/7] gpu: ipu-v3: image-convert: move output seam valid interval calculation into find_best_seam

2019-08-14 Thread Philipp Zabel
This reduces code duplication and allows to easily calculate the valid interval for the input seam position in the same place. Signed-off-by: Philipp Zabel --- drivers/gpu/ipu-v3/ipu-image-convert.c | 30 +++--- 1 file changed, 12 insertions(+), 18 deletions(-) diff --git

[PATCH 7/7] gpu: ipu-v3: image-convert: only sample into the next tile if necessary

2019-08-14 Thread Philipp Zabel
The first pixel of the next tile is only sampled by the hardware if the fractional input position corresponding to the last written output pixel is not an integer position. Signed-off-by: Philipp Zabel --- drivers/gpu/ipu-v3/ipu-image-convert.c | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH v2 1/3] drm/etnaviv: skip command stream validation on PPAS capable GPUs

2019-08-14 Thread Guido Günther
Hi, On Fri, Aug 09, 2019 at 02:05:12PM +0200, Lucas Stach wrote: > With per-process address spaces in place, a rogue process submitting > bogus command streams can only hurt itself. There is no need to > validate the command stream before execution anymore. > > Signed-off-by: Lucas Stach >

Re: [PATCH 08/60] drm/bridge: Extend bridge API to disable connector creation

2019-08-14 Thread Daniel Vetter
On Wed, Aug 14, 2019 at 12:55:29PM +0300, Laurent Pinchart wrote: > On Wed, Aug 14, 2019 at 10:18:40AM +0200, Daniel Vetter wrote: > > On Thu, Aug 08, 2019 at 07:36:49PM +0200, Andrzej Hajda wrote: > > > On 08.08.2019 16:25, Laurent Pinchart wrote: > > > > On Wed, Jul 17, 2019 at 08:39:47AM +0200,

Re: [PATCH] video/fbdev/aty128fb: Remove dead code

2019-08-14 Thread Souptick Joarder
On Wed, Aug 7, 2019 at 2:12 PM Souptick Joarder wrote: > > On Wed, Jul 31, 2019 at 12:38 AM Souptick Joarder > wrote: > > > > This is dead code since 3.15. If there is no plan to use it > > further, this can be removed forever. > > Any comment on this patch ? Any comment on this patch ? > > >

Re: [PATCH v2 3/3] drm/etnaviv: implement softpin

2019-08-14 Thread Guido Günther
Hi, nOn Fri, Aug 09, 2019 at 02:05:14PM +0200, Lucas Stach wrote: > With softpin we allow the userspace to take control over the GPU virtual > address space. The new capability is relected by a bump of the minor DRM > version. There are a few restrictions for userspace to take into > account: > >

Re: [PATCH 09/60] drm/bridge: Add connector-related bridge operations and data

2019-08-14 Thread Daniel Vetter
On Thu, Aug 08, 2019 at 10:32:14PM +0300, Laurent Pinchart wrote: > Hello, > > On Tue, Jul 16, 2019 at 03:57:21PM +0200, Andrzej Hajda wrote: > > On 16.07.2019 11:00, Daniel Vetter wrote: > > > On Fri, Jul 12, 2019 at 11:01:38AM +0200, Andrzej Hajda wrote: > > >> On 11.07.2019 17:50, Daniel

Re: [PATCH 09/60] drm/bridge: Add connector-related bridge operations and data

2019-08-14 Thread Daniel Vetter
On Wed, Aug 14, 2019 at 01:04:03PM +0300, Laurent Pinchart wrote: > Hi Andrzej, > > On Wed, Aug 14, 2019 at 08:23:12AM +0200, Andrzej Hajda wrote: > > Hi Laurent, > > > > Sorry for late response. > > No worries. > > > On 11.08.2019 00:43, Laurent Pinchart wrote: > > > On Fri, Aug 09, 2019 at

Re: [PATCH v3 hmm 11/11] mm/mmu_notifiers: remove unregister_no_release

2019-08-14 Thread Ralph Campbell
On 8/6/19 4:15 PM, Jason Gunthorpe wrote: From: Jason Gunthorpe mmu_notifier_unregister_no_release() and mmu_notifier_call_srcu() no longer have any users, they have all been converted to use mmu_notifier_put(). So delete this difficult to use interface. Signed-off-by: Jason Gunthorpe

[PATCH 2/6] mips: export arch_sync_dma_for_*()

2019-08-14 Thread Rob Clark
From: Rob Clark Signed-off-by: Rob Clark --- arch/arm64/mm/flush.c | 2 ++ arch/mips/mm/dma-noncoherent.c | 2 ++ drivers/gpu/drm/drm_cache.c| 20 +--- include/drm/drm_cache.h| 4 4 files changed, 25 insertions(+), 3 deletions(-) diff --git

Re: [PATCH v4 0/9] DRM panel drivers for omapdrm

2019-08-14 Thread Laurent Pinchart
Hi Sam, On Wed, Aug 14, 2019 at 10:28:01PM +0200, Sam Ravnborg wrote: > On Wed, Aug 14, 2019 at 06:44:26PM +0200, Sam Ravnborg wrote: > > On Tue, Aug 13, 2019 at 11:10:52PM +0300, Laurent Pinchart wrote: > > > Hello everybody, > > > > > > This patch series adds DT bindings and drivers for 6

[PATCH 3/6] powerpc: export arch_sync_dma_for_*()

2019-08-14 Thread Rob Clark
From: Rob Clark Signed-off-by: Rob Clark --- arch/powerpc/mm/dma-noncoherent.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/powerpc/mm/dma-noncoherent.c b/arch/powerpc/mm/dma-noncoherent.c index c617282d5b2a..80d53b950821 100644 --- a/arch/powerpc/mm/dma-noncoherent.c +++

Re: [PATCH 1/5] mm: Check if mmu notifier callbacks are allowed to fail

2019-08-14 Thread Jason Gunthorpe
On Wed, Aug 14, 2019 at 03:14:47PM -0700, Andrew Morton wrote: > On Wed, 14 Aug 2019 22:20:23 +0200 Daniel Vetter > wrote: > > > Just a bit of paranoia, since if we start pushing this deep into > > callchains it's hard to spot all places where an mmu notifier > > implementation might fail when

Re: [PATCH 1/5] mm: Check if mmu notifier callbacks are allowed to fail

2019-08-14 Thread Ralph Campbell
On 8/14/19 3:14 PM, Andrew Morton wrote: On Wed, 14 Aug 2019 22:20:23 +0200 Daniel Vetter wrote: Just a bit of paranoia, since if we start pushing this deep into callchains it's hard to spot all places where an mmu notifier implementation might fail when it's not allowed to. Inspired by

Re: [PATCH v3 hmm 00/11] Add mmu_notifier_get/put for managing mmu notifier registrations

2019-08-14 Thread Ralph Campbell
On 8/6/19 4:15 PM, Jason Gunthorpe wrote: From: Jason Gunthorpe This series introduces a new registration flow for mmu_notifiers based on the idea that the user would like to get a single refcounted piece of memory for a mm, keyed to its use. For instance many users of mmu_notifiers use an

[Bug 204241] amdgpu fails to resume from suspend

2019-08-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204241 --- Comment #9 from Andrey Grodzovsky (andrey.grodzov...@amd.com) --- I was able to reproduce. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing

Re: [PATCH v3 hmm 03/11] mm/mmu_notifiers: add a get/put scheme for the registration

2019-08-14 Thread Ralph Campbell
On 8/6/19 4:15 PM, Jason Gunthorpe wrote: From: Jason Gunthorpe Many places in the kernel have a flow where userspace will create some object and that object will need to connect to the subsystem's mmu_notifier subscription for the duration of its lifetime. In this case the subsystem is

[PATCH 4/7] drm/nouveau/pci: enable pcie link changes for pascal

2019-08-14 Thread Karol Herbst
Signed-off-by: Karol Herbst Reviewed-by: Lyude Paul CC: Alex Hung CC: Rafael J. Wysocki CC: Dave Airlie CC: Lyude Paul CC: Ben Skeggs --- drivers/gpu/drm/nouveau/nvkm/subdev/pci/gk104.c | 8 drivers/gpu/drm/nouveau/nvkm/subdev/pci/gp100.c | 10 ++

[PATCH 7/7] drm/nouveau: abort runtime suspend if we hit an error

2019-08-14 Thread Karol Herbst
Signed-off-by: Karol Herbst CC: Alex Hung CC: Rafael J. Wysocki CC: Dave Airlie CC: Lyude Paul CC: Ben Skeggs --- drivers/gpu/drm/nouveau/nouveau_drm.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c b/drivers/gpu/drm/nouveau/nouveau_drm.c

[PATCH 3/7] Revert "ACPI / OSI: Add OEM _OSI strings to disable NVidia RTD3"

2019-08-14 Thread Karol Herbst
This reverts commit 9251a71db62ca9cc7e7cf364218610b0f018c291. This was never discussed with anybody Nouveau related and we would have NACKed this change immediately. We have a better workaround, which makes it actually work with Nouveau. No idea why the comment mentions the Nvidia driver and

[PATCH 2/7] Revert "ACPI / OSI: Add OEM _OSI string to enable NVidia HDMI audio"

2019-08-14 Thread Karol Herbst
This reverts commit 887532ca7ca59fcf0547a79211756791128030a3. We have a better solution for this: b516ea586d717 And same as with the last commit: "NVidia Linux driver" that's Nouveau, any out of tree driver does _not_ matter. And with Nouveau all of this works even though it required a proper

[PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"

2019-08-14 Thread Karol Herbst
This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c. The original commit message didn't even make sense. AMD _does_ support it and it works with Nouveau as well. Also what was the issue being solved here? No references to any bugs and not even explaining any issue at all isn't the way

[PATCH 08/11] drm/msm/hdmi: silence -EPROBE_DEFER warning

2019-08-14 Thread Brian Masney
Silence a warning message due to an -EPROBE_DEFER error to help cleanup the system boot log. Signed-off-by: Brian Masney --- drivers/gpu/drm/msm/hdmi/hdmi_phy.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/msm/hdmi/hdmi_phy.c

[PATCH 07/11] ARM: qcom_defconfig: add CONFIG_DRM_ANALOGIX_ANX78XX

2019-08-14 Thread Brian Masney
Add CONFIG_DRM_ANALOGIX_ANX78XX as a module so that the external display can be used on the Nexus 5 phones. Signed-off-by: Brian Masney --- arch/arm/configs/qcom_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig index

[PATCH RFC 06/11] drm/bridge: analogix-anx78xx: add support for avdd33 regulator

2019-08-14 Thread Brian Masney
Add support for the avdd33 regulator to the analogix-anx78xx driver. Note that the regulator is currently enabled during driver probe and disabled when the driver is removed. This is currently how the downstream MSM kernel sources do this. Let's not merge this upstream for the mean time until I

[PATCH 03/11] drm/bridge: analogix-anx78xx: silence -EPROBE_DEFER warnings

2019-08-14 Thread Brian Masney
Silence two warning messages that occur due to -EPROBE_DEFER errors to help cleanup the system boot log. Signed-off-by: Brian Masney --- drivers/gpu/drm/bridge/analogix-anx78xx.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

[PATCH RFC 10/11] ARM: dts: qcom: msm8974: add HDMI nodes

2019-08-14 Thread Brian Masney
Add HDMI tx and phy nodes to support an external display that can be connected over the SlimPort. This is based on work from Jonathan Marek. Signed-off-by: Brian Masney --- The hdmi-tx node in the downstream MSM sources:

[PATCH 02/11] drm/bridge: analogix-anx78xx: add new variants

2019-08-14 Thread Brian Masney
Add support for the 7808 variant. While we're here, the of match table was missing support for the 7812 and 7818 variants, so add them as well. Signed-off-by: Brian Masney --- drivers/gpu/drm/bridge/analogix-anx78xx.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH 05/11] drm/bridge: analogix-anx78xx: correct value of TX_P0

2019-08-14 Thread Brian Masney
When attempting to configure this driver on a Nexus 5 phone (msm8974), setting up the dummy i2c bus for TX_P0 would fail due to an -EBUSY error. The downstream MSM kernel sources [1] shows that the proper value for TX_P0 is 0x78, not 0x70, so correct the value to allow device probing to succeed.

[PATCH 09/11] ARM: dts: qcom: pm8941: add 5vs2 regulator node

2019-08-14 Thread Brian Masney
pm8941 is missing the 5vs2 regulator node so let's add it since its needed to get the external display working. This regulator was already configured in the interrupts property on the parent node. Note that this regulator is referred to as mvs2 in the downstream MSM kernel sources.

[PATCH RFC 11/11] ARM: dts: qcom: msm8974-hammerhead: add support for external display

2019-08-14 Thread Brian Masney
Add HDMI nodes and other supporting infrastructure in order to support the external display. This is based on work from Jonathan Marek. Signed-off-by: Brian Masney --- The hdmi-tx node in the downstream MSM sources:

Re: [PATCH v3 hmm 02/11] mm/mmu_notifiers: do not speculatively allocate a mmu_notifier_mm

2019-08-14 Thread Ralph Campbell
On 8/6/19 4:15 PM, Jason Gunthorpe wrote: From: Jason Gunthorpe A prior commit e0f3c3f78da2 ("mm/mmu_notifier: init notifier if necessary") made an attempt at doing this, but had to be reverted as calling the GFP_KERNEL allocator under the i_mmap_mutex causes deadlock, see commit 35cfa2b0b491

[PATCH 5/7] drm/nouveau/pci: add nvkm_pcie_get_speed

2019-08-14 Thread Karol Herbst
v2: fixed compilation error Signed-off-by: Karol Herbst Reviewed-by: Lyude Paul CC: Alex Hung CC: Rafael J. Wysocki CC: Dave Airlie CC: Lyude Paul CC: Ben Skeggs --- drivers/gpu/drm/nouveau/include/nvkm/subdev/pci.h | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/pci/pcie.c| 8 2

[PATCH 6/7] drm/nouveau/pci: save the boot pcie link speed and restore it on fini

2019-08-14 Thread Karol Herbst
Apperantly things go south if we suspend the device with a different PCIE link speed set than it got booted with. Fixes runtime suspend on my gp107. This all looks like some bug inside the pci subsystem and I would prefer a fix there instead of nouveau, but maybe there is no real nice way of

[PATCH 0/7] Adding a proper workaround for fixing RTD3 issues with Nouveau

2019-08-14 Thread Karol Herbst
First three patches are removing ACPI workarounds which should have never landed. The last four are adding a workaround to nouveau which seem to help quite a lot with the RTD3 issues with Nouveau, so let's discuss and get wider testing of those and see if there is any fallout or laptops where the

[PATCH 0/6] drm+dma: cache support for arm, etc

2019-08-14 Thread Rob Clark
From: Rob Clark This is a replacement for a previous patches[1] that was adding arm64 support for drm_clflush. I've also added a patch to solve a similar cache issue in vgem. The first few patches just export arch_sync_dma_for_*(). Possibly instead the EXPORT_SYMBOL_GPL() should be somewere

Re: [PATCH 1/5] mm: Check if mmu notifier callbacks are allowed to fail

2019-08-14 Thread Andrew Morton
On Wed, 14 Aug 2019 22:20:23 +0200 Daniel Vetter wrote: > Just a bit of paranoia, since if we start pushing this deep into > callchains it's hard to spot all places where an mmu notifier > implementation might fail when it's not allowed to. > > Inspired by some confusion we had discussing i915

[PATCH 00/11] ARM: dts: qcom: msm8974: add support for external display

2019-08-14 Thread Brian Masney
This patch series begins to add support for the external display over HDMI that is supported on msm8974 SoCs. I'm testing this series on the Nexus 5, and I'm able to communicate with the HDMI bridge via the analogix-anx78xx driver, however the external display is not working yet. When I plug in

[PATCH 01/11] dt-bindings: drm/bridge: analogix-anx78xx: add new variants

2019-08-14 Thread Brian Masney
Add support for the analogix,anx7808, analogix,anx7812, and analogix,anx7818 variants. Signed-off-by: Brian Masney --- .../devicetree/bindings/display/bridge/anx7814.txt | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH 04/11] drm/bridge: analogix-anx78xx: convert to i2c_new_dummy_device

2019-08-14 Thread Brian Masney
The i2c_new_dummy() function is deprecated since it returns NULL on error. Change this to use the recommended replacement i2c_new_dummy_device() that returns an error code that can be read with PTR_ERR() and friends. Signed-off-by: Brian Masney --- drivers/gpu/drm/bridge/analogix-anx78xx.c | 15

[Bug 111244] amdgpu kernel 5.2 blank display after resume from suspend

2019-08-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111244 --- Comment #26 from mib...@gmx.at --- Created attachment 145065 --> https://bugs.freedesktop.org/attachment.cgi?id=145065=edit failed suspend log Attached full log -- You are receiving this mail because: You are the assignee for the

Re: [PATCH 3/5] mm, notifier: Catch sleeping/blocking for !blockable

2019-08-14 Thread Jason Gunthorpe
On Wed, Aug 14, 2019 at 10:20:25PM +0200, Daniel Vetter wrote: > We need to make sure implementations don't cheat and don't have a > possible schedule/blocking point deeply burried where review can't > catch it. > > I'm not sure whether this is the best way to make sure all the > might_sleep()

Re: [PATCH] dma-buf/sw_sync: Synchronize signal vs syncpt free

2019-08-14 Thread Sasha Levin
On Wed, Aug 14, 2019 at 07:24:15PM +0200, Daniel Vetter wrote: Hi Sasha, On Mon, Aug 12, 2019 at 07:05:47PM +, Sasha Levin wrote: Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking

Re: [PATCH v3 hmm 05/11] hmm: use mmu_notifier_get/put for 'struct hmm'

2019-08-14 Thread Ralph Campbell
On 8/6/19 4:15 PM, Jason Gunthorpe wrote: From: Jason Gunthorpe This is a significant simplification, it eliminates all the remaining 'hmm' stuff in mm_struct, eliminates krefing along the critical notifier paths, and takes away all the ugly locking and abuse of page_table_lock.

[PATCH 4/6] arm: add arch_sync_dma_for_*()

2019-08-14 Thread Rob Clark
From: Rob Clark Signed-off-by: Rob Clark --- arch/arm/Kconfig| 2 ++ arch/arm/mm/dma-mapping-nommu.c | 14 ++ arch/arm/mm/dma-mapping.c | 28 3 files changed, 44 insertions(+) diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig

Re: [PATCH 2/5] kernel.h: Add non_block_start/end()

2019-08-14 Thread Jason Gunthorpe
On Wed, Aug 14, 2019 at 10:20:24PM +0200, Daniel Vetter wrote: > In some special cases we must not block, but there's not a > spinlock, preempt-off, irqs-off or similar critical section already > that arms the might_sleep() debug checks. Add a non_block_start/end() > pair to annotate these. > >

Re: [PATCH 2/5] kernel.h: Add non_block_start/end()

2019-08-14 Thread Andrew Morton
On Wed, 14 Aug 2019 22:20:24 +0200 Daniel Vetter wrote: > In some special cases we must not block, but there's not a > spinlock, preempt-off, irqs-off or similar critical section already > that arms the might_sleep() debug checks. Add a non_block_start/end() > pair to annotate these. > > This

[PATCH 6/6] drm/vgem: fix cache synchronization on arm/arm64 (take two)

2019-08-14 Thread Rob Clark
From: Rob Clark drm_cflush_pages() is no-op on arm/arm64. But instead we can use arch_sync API. Fixes failures with vgem_test. Signed-off-by: Rob Clark --- drivers/gpu/drm/vgem/vgem_drv.c | 145 +--- 1 file changed, 98 insertions(+), 47 deletions(-) diff --git

Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"

2019-08-14 Thread Dave Airlie
On Thu, 15 Aug 2019 at 07:31, Karol Herbst wrote: > > This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c. > > The original commit message didn't even make sense. AMD _does_ support it and > it works with Nouveau as well. > > Also what was the issue being solved here? No references to

Re: [PATCH v2 0/2] drm/mediatek: make imported PRIME buffers contiguous

2019-08-14 Thread CK Hu
Hi, Alexandre: On Mon, 2019-07-29 at 14:33 +0900, Alexandre Courbot wrote: > The default DMA segment size was used when importing PRIME buffers, > which resulted in a chance of them not being contiguous in the virtual > IO space of the device and mtk_gem_prime_import_sg_table() complaining > that

[pull] amdgpu, scheduler drm-fixes-5.3

2019-08-14 Thread Alex Deucher
Hi Dave, Daniel, A few fixes for 5.3. Nothing major. The following changes since commit d45331b00ddb179e291766617259261c112db872: Linux 5.3-rc4 (2019-08-11 13:26:41 -0700) are available in the Git repository at: git://people.freedesktop.org/~agd5f/linux tags/drm-fixes-5.3-2019-08-14 for

[PATCH 1/6] arm64: export arch_sync_dma_for_*()

2019-08-14 Thread Rob Clark
From: Rob Clark Signed-off-by: Rob Clark --- arch/arm64/mm/dma-mapping.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/mm/dma-mapping.c b/arch/arm64/mm/dma-mapping.c index 1d3f0b5a9940..ea5ae11d07f7 100644 --- a/arch/arm64/mm/dma-mapping.c +++ b/arch/arm64/mm/dma-mapping.c

[PATCH 5/6] drm/msm: stop abusing DMA API

2019-08-14 Thread Rob Clark
From: Rob Clark Use arch_sync_dma_for_{device,cpu}() rather than abusing the DMA API to indirectly get at the arch_sync_dma code. Signed-off-by: Rob Clark --- drivers/gpu/drm/msm/msm_gem.c | 37 +++ 1 file changed, 11 insertions(+), 26 deletions(-) diff --git

Re: [PATCH 4/5] mm, notifier: Add a lockdep map for invalidate_range_start

2019-08-14 Thread Jason Gunthorpe
On Wed, Aug 14, 2019 at 10:20:26PM +0200, Daniel Vetter wrote: > This is a similar idea to the fs_reclaim fake lockdep lock. It's > fairly easy to provoke a specific notifier to be run on a specific > range: Just prep it, and then munmap() it. > > A bit harder, but still doable, is to provoke the

Re: turn hmm migrate_vma upside down v3

2019-08-14 Thread Ralph Campbell
On 8/14/19 12:59 AM, Christoph Hellwig wrote: Hi Jérôme, Ben and Jason, below is a series against the hmm tree which starts revamping the migrate_vma functionality. The prime idea is to export three slightly lower level functions and thus avoid the need for migrate_vma_ops callbacks.

Re: [PATCH 5/5] mm/hmm: WARN on illegal ->sync_cpu_device_pagetables errors

2019-08-14 Thread Jason Gunthorpe
On Wed, Aug 14, 2019 at 10:20:27PM +0200, Daniel Vetter wrote: > Similar to the warning in the mmu notifer, warning if an hmm mirror > callback gets it's blocking vs. nonblocking handling wrong, or if it > fails with anything else than -EAGAIN. > > Cc: Jason Gunthorpe > Cc: Ralph Campbell > Cc:

  1   2   3   >