Re: [PATCH 19/20] lib: image-formats: Add more functions

Hi Maxime, On Wed, Apr 17, 2019 at 09:54:45AM +0200, Maxime Ripard wrote: > V4L2 drivers typically need a few more helpers compared to DRM drivers, so > let's add them. > > Signed-off-by: Maxime Ripard > --- > include/linux/image-formats.h | 42 - > 1 file ch

Re: [PATCH] drm/amdgpu: fix drm leases being broken on radv

Am 17.04.19 um 14:35 schrieb Daniel Vetter: On Wed, Apr 17, 2019 at 12:06:32PM +, Koenig, Christian wrote: Am 17.04.19 um 14:00 schrieb Daniel Vetter: On Wed, Apr 17, 2019 at 11:18:35AM +, Koenig, Christian wrote: Am 17.04.19 um 13:06 schrieb Daniel Vetter: On Wed, Apr 17, 2019 at 12:

Re: [PATCH 06/20] lib: Add video format information library

Hi, On Wed, Apr 17, 2019 at 02:34:54PM +0200, Paul Kocialkowski wrote: > > +struct image_format_info { > > + union { > > + /** > > +* @drm_fmt: > > +* > > +* DRM 4CC format identifier (DRM_FORMAT_*) > > +*/ > > + u32 drm_fmt; >

Re: [Intel-gfx] [PATCH 1/2] drm/i915: remove DRM_AUTH from IOCTLs which also have DRM_RENDER_ALLOW

On Wed, Apr 17, 2019 at 01:25:24PM +0200, Christian König wrote: > This is to work around problems with libva and vainfo. > > Signed-off-by: Christian König I don't think this is a good idea since it leaves the core ioctl out, and it leaves all other drivers out (and inconsistency in these winsy

Re: [PATCH -next] drm/lima: Make lima_sched_ops static

Pushed to drm-misc-next. Thanks, Qiang On Tue, Apr 16, 2019 at 10:44 PM Yue Haibing wrote: > > From: YueHaibing > > Fix sparse warning: > > drivers/gpu/drm/lima/lima_sched.c:356:36: warning: > symbol 'lima_sched_ops' was not declared. Should it be static? > > Reported-by: Hulk Robot > Signed-

Re: [PATCH 2/2] drm/dp_mst: Register aux-dev nodes for MST ports

On Tue, Apr 16, 2019 at 06:22:33PM -0400, Lyude Paul wrote: > On Fri, 2019-04-12 at 12:05 -0400, sunpeng...@amd.com wrote: > > From: Ville Syrjälä > > > > Expose AUX devices for MST ports, similar to how they are exposed for > > SST. > > > > The registered device will have it's MST port path app

Re: [PATCH 04/20] drm/fourcc: Pass the format_info pointer to drm_format_plane_width/height

On Wed, Apr 17, 2019 at 01:10:33PM +0200, Maarten Lankhorst wrote: > Op 17-04-2019 om 13:01 schreef Maxime Ripard: > > On Wed, Apr 17, 2019 at 12:47:48PM +0200, Maarten Lankhorst wrote: > >>> +/** > >>> + * drm_format_info_plane_width - width of the plane given the first plane > >>> + * @format: pi

Re: [PATCH v2 02/12] drm/fb-helper: Avoid race with DRM userspace

On Tue, Apr 16, 2019 at 08:46:24PM +0200, Noralf Trønnes wrote: > > > Den 16.04.2019 09.59, skrev Daniel Vetter: > > On Sun, Apr 07, 2019 at 06:52:33PM +0200, Noralf Trønnes wrote: > >> drm_fb_helper_is_bound() is used to check if DRM userspace is in control. > >> This is done by looking at the f

Re: [PATCH v2 02/12] drm/fb-helper: Avoid race with DRM userspace

On Wed, Apr 17, 2019 at 03:24:00PM +0200, Daniel Vetter wrote: > On Tue, Apr 16, 2019 at 08:46:24PM +0200, Noralf Trønnes wrote: > > > > > > Den 16.04.2019 09.59, skrev Daniel Vetter: > > > On Sun, Apr 07, 2019 at 06:52:33PM +0200, Noralf Trønnes wrote: > > >> drm_fb_helper_is_bound() is used to

Re: [PATCH 02/20] drm: Remove users of drm_format_(horz|vert)_chroma_subsampling

On Wed, 2019-04-17 at 09:54 +0200, Maxime Ripard wrote: > drm_format_horz_chroma_subsampling and drm_format_vert_chroma_subsampling > are basically a lookup in the drm_format_info table plus an access to the > hsub and vsub fields of the appropriate entry. > > Most drivers are using this function

[PATCH] drm/drv: Fix incorrect resolution of merge conflict

Commit f06ddb53096b ("BackMerge v5.1-rc5 into drm-next") incorrectly resolved a merge conflict related to a patch having been merged twice: - commit 3f04e0a6cfeb ("drm: Fix drm_release() and device unplug") introduced as a standalone fix via drm-fixes branch, - commit 1ee57d4d75fb ("drm: Fix drm_

Re: [PATCH] drm/amdgpu: fix drm leases being broken on radv

On Wed, Apr 17, 2019 at 02:46:06PM +0200, Christian König wrote: > Am 17.04.19 um 14:35 schrieb Daniel Vetter: > > On Wed, Apr 17, 2019 at 12:06:32PM +, Koenig, Christian wrote: > > > Am 17.04.19 um 14:00 schrieb Daniel Vetter: > > > > On Wed, Apr 17, 2019 at 11:18:35AM +, Koenig, Christian

Re: [PATCH v4 2/3] dt-bindings: backlight: add lm3630a bindings

On Tue, Apr 16, 2019 at 6:54 PM Brian Masney wrote: > > Add new backlight bindings for the TI LM3630A dual-string white LED. > > Signed-off-by: Brian Masney > --- > Rob: Since the common bindings aren't converted to the new JSON schema > yet, I'm not sure how to do led-sources here. I would expec

Re: [PATCH v3 2/3] dt-bindings: Add header for the ingenic-drm driver bindings

On Sun, Apr 14, 2019 at 3:08 PM Paul Cercueil wrote: > > Add macros that can be used with the ingenic,lcd-mode property in the > devicetree node that corresponds to the ingenic-drm driver. DRM is a Linuxism. > > Signed-off-by: Paul Cercueil > Tested-by: Artur Rojek > --- > > Notes: > v2: N

Re: [PATCH v3 1/3] dt-bindings: Add doc for the ingenic-drm driver

On Sun, Apr 14, 2019 at 3:08 PM Paul Cercueil wrote: > > Add documentation for the devicetree bindings of the DRM driver for the DRM is a Linuxism. What is the LCD controller h/w block called? > JZ47xx family of SoCs from Ingenic. > > Signed-off-by: Paul Cercueil > Tested-by: Artur Rojek > ---

[PATCH v2 0/8] per-process address spaces for MMUv2

Hi all, v1 cover letter: the following patches finally implement one of the longstanding TODO items in the etnaviv driver: per-process address spaces. They are only enabled for MMUv2, as switching the MMU context on MMUv1 would require a full stop of the FE, which I deemed too expensive to do on

[PATCH v2 7/8] drm/etnaviv: implement per-process address spaces on MMUv2

MMUv2 allows for proper switching of the MMU context through the command stream. Use this to give each process it's own GPU address space. MMU contexts are switched lazily, which means there is no dedicated kernel MMU context, but the kernel ringbuffer is mapped into each user MMU context. This way

[PATCH v2 4/8] drm/etnaviv: rework MMU handling

This reworks the MMU handling to make it possible to have multiple MMU contexts, not one per GPU. This commit doesn't actually do anything with those contexts, aside from giving one of them to each GPU. The code changes are pretty invasive, but there is no sane way to split this into smaller chang

[PATCH v2 3/8] drm/etnaviv: replace MMU flush marker with flush sequence

If a MMU is shared between multiple GPUs, all of them need to flush their TLBs, so a single marker that gets reset on the first flush won't do. Replace the flush marker with a sequence number, so that it's possible to check if the TLB is in sync with the current page table state for each GPU. Sign

[PATCH v2 5/8] drm/etnaviv: split out starting of FE idle loop

Move buffer setup and starting of the FE loop in the kernel ringbuffer into a separate function. This is a preparation to start the FE later in the submit process. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 26 -- 1 file changed, 16 insertions(

[PATCH v2 6/8] drm/etnaviv: provide MMU context to etnaviv_gem_mapping_get

In preparation to having a context per process, etnaviv_gem_mapping_get should not use the current GPU context, but needs to be told which context to use. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gem.c| 20 drivers/gpu/drm/etnaviv/etnaviv_gem.h

[PATCH v2 1/8] drm/etnaviv: split out cmdbuf mapping into address space

This allows to decouple the cmdbuf suballocator create and mapping the region into the GPU address space. Allowing multiple AS to share a single cmdbuf suballoc. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_buffer.c | 23 --- drivers/gpu/drm/etnaviv/etnaviv_cmdbuf.c | 42 ++

[PATCH v2 2/8] drm/etnaviv: share a single cmdbuf suballoc region across all GPUs

There is no need for each GPU to have it's own cmdbuf suballocation region. Only allocate a single one for the the etnaviv virtual device and share it across all GPUs. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_cmdbuf.c | 14 ++-- drivers/gpu/drm/etnaviv/etnaviv_c

[PATCH v2 8/8] drm/etnaviv: dump only failing submit

Due to the tracking provided by the scheduler we know which submit is failing. Only dump this single submit and the required auxiliary information. This cuts down the size of the devcoredumps by only including relevant information. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_d

Re: dynamic DMA-buf sharing between devices

Thanks Christian, great job. I will verify it this week when I finish my current work on hand. -David 在 2019/4/17 2:38, Christian König wrote: > Hi everybody, > > core idea in this patch set is that DMA-buf importers can now provide an > optional invalidate callback. Using this callback and the

Re: [PATCH v3 2/3] dt-bindings: Add header for the ingenic-drm driver bindings

Paul, This mail bounced for me, but the other one on patch 1 didn't. On Wed, Apr 17, 2019 at 8:47 AM Rob Herring wrote: > > On Sun, Apr 14, 2019 at 3:08 PM Paul Cercueil wrote: > > > > Add macros that can be used with the ingenic,lcd-mode property in the > > devicetree node that corresponds to t

Re: dynamic DMA-buf sharing between devices

On top of those I have 6 more patches in the pipeline to enable VRAM P2P with DMA-buf. So that is not the end of the patch set :) Christian. Am 17.04.19 um 15:52 schrieb Chunming Zhou: Thanks Christian, great job. I will verify it this week when I finish my current work on hand. -David 在 20

Re: [PATCH 2/4 v2] drm/mcde: Add device tree bindings

On Tue, Apr 16, 2019 at 9:28 AM Linus Walleij wrote: > > This adds the device tree bindings for the ST-Ericsson > Multi Channel Display Engine MCDE as found in the U8500 > SoCs. > > Cc: devicet...@vger.kernel.org > Signed-off-by: Linus Walleij > --- > ChangeLog v1->v2: > - Drop the graph represen

Re: [PATCH 04/12] dma-buf: add optional invalidate_mappings callback v5

On Tue, Apr 16, 2019 at 08:38:33PM +0200, Christian König wrote: > Each importer can now provide an invalidate_mappings callback. > > This allows the exporter to provide the mappings without the need to pin > the backing store. > > v2: don't try to invalidate mappings when the callback is NULL, >

Re: [PATCH 06/20] lib: Add video format information library

Hi, On Wed, 2019-04-17 at 14:48 +0200, Maxime Ripard wrote: > Hi, > > On Wed, Apr 17, 2019 at 02:34:54PM +0200, Paul Kocialkowski wrote: > > > +struct image_format_info { > > > + union { > > > + /** > > > + * @drm_fmt: > > > + * > > > + * DRM 4CC format identifi

Re: [PATCH v2 4/5] drm/modes: Parse overscan properties

Hi Noralf, On Tue, Apr 16, 2019 at 04:52:20PM +0200, Noralf Trønnes wrote: > Den 11.04.2019 15.22, skrev Maxime Ripard: > > Properly configuring the overscan properties might be needed for the > > initial setup of the framebuffer for display that still have overscan. > > Let's allow for more prope

Re: [PATCH 03/12] dma-buf: lock the reservation object during (un)map_dma_buf v3

On Tue, Apr 16, 2019 at 08:38:32PM +0200, Christian König wrote: > Make it mandatory for dynamic dma-buf callbacks to be called with the > reservation lock held. > > For static dma-buf exporters we still have the fallback of using cached sgt. > > v2: reordered > v3: rebased on sgt caching > v4: u

Re: dynamic DMA-buf sharing between devices

I like you do somethings step by step, you can ping me when they are ready. -David 在 2019/4/17 21:59, Christian König 写道: > On top of those I have 6 more patches in the pipeline to enable VRAM > P2P with DMA-buf. > > So that is not the end of the patch set :) > > Christian. > > Am 17.04.19 um 15

Re: [PATCH 03/12] dma-buf: lock the reservation object during (un)map_dma_buf v3

Am 17.04.19 um 16:08 schrieb Daniel Vetter: On Tue, Apr 16, 2019 at 08:38:32PM +0200, Christian König wrote: Make it mandatory for dynamic dma-buf callbacks to be called with the reservation lock held. For static dma-buf exporters we still have the fallback of using cached sgt. v2: reordered v

Re: [PATCH 05/12] dma-buf: add explicit buffer pinning

On Tue, Apr 16, 2019 at 08:38:34PM +0200, Christian König wrote: > Add optional explicit pinning callbacks instead of implicitly assume the > exporter pins the buffer when a mapping is created. > > Signed-off-by: Christian König Don't we need this together with the invalidate callback and the dy

[Bug 102646] Screen flickering under amdgpu-experimental [buggy auto power profile]

https://bugs.freedesktop.org/show_bug.cgi?id=102646 --- Comment #81 from tempel.jul...@gmail.com --- I really hope this bug is not just not occurring with Vega because it uses HBM2, so that we won't see it again with Navi GPUs which probably will use GDDR5/6. -- You are receiving this mail becau

Re: [PATCH 03/12] dma-buf: lock the reservation object during (un)map_dma_buf v3

On Wed, Apr 17, 2019 at 04:14:32PM +0200, Christian König wrote: > Am 17.04.19 um 16:08 schrieb Daniel Vetter: > > On Tue, Apr 16, 2019 at 08:38:32PM +0200, Christian König wrote: > > > Make it mandatory for dynamic dma-buf callbacks to be called with the > > > reservation lock held. > > > > > > F

[PATCH] drm/etnaviv: request pages from DMA32 zone when needed

Some Vivante GPUs are found in systems that have interconnects restricted to 32 address bits, but may have system memory mapped above the 4GB mark. As this region isn't accessible to the GPU via DMA any GPU memory allocated in the upper part needs to go through SWIOTLB bounce buffering. This kills

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

On Wed, Apr 17, 2019 at 09:15:52AM +, Thomas Hellstrom wrote: > On Tue, 2019-04-16 at 10:46 -0400, Jerome Glisse wrote: > > On Sat, Apr 13, 2019 at 08:34:02AM +, Thomas Hellstrom wrote: > > > Hi, Jérôme > > > > > > On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote: > > > > On Fri, Apr

Re: [PATCH v2 3/5] drm/modes: Allow to specify rotation and reflection on the commandline

Hi Noralf, On Tue, Apr 16, 2019 at 04:50:00PM +0200, Noralf Trønnes wrote: > Den 11.04.2019 15.22, skrev Maxime Ripard: > > Rotations and reflections setup are needed in some scenarios to initialise > > properly the initial framebuffer. Some drivers already had a bunch of > > quirks to deal with t

Re: [PATCH 05/12] dma-buf: add explicit buffer pinning

On Wed, Apr 17, 2019 at 04:20:02PM +0200, Daniel Vetter wrote: > On Tue, Apr 16, 2019 at 08:38:34PM +0200, Christian König wrote: > > Add optional explicit pinning callbacks instead of implicitly assume the > > exporter pins the buffer when a mapping is created. > > > > Signed-off-by: Christian Kö

Re: [PATCH 04/12] dma-buf: add optional invalidate_mappings callback v5

On Wed, Apr 17, 2019 at 04:01:16PM +0200, Daniel Vetter wrote: > On Tue, Apr 16, 2019 at 08:38:33PM +0200, Christian König wrote: > > Each importer can now provide an invalidate_mappings callback. > > > > This allows the exporter to provide the mappings without the need to pin > > the backing stor

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

Ping on this patch and patch 5. The rest already RBed. Andrey On 4/16/19 2:23 PM, Andrey Grodzovsky wrote: > From: Christian König > > We now destroy finished jobs from the worker thread to make sure that > we never destroy a job currently in timeout processing. > By this we avoid holding lock a

Re: [PATCH] drm/nouveau: Fix DEVICE_PRIVATE dependencies

On Wed, Apr 17, 2019 at 10:26:32PM +0800, Yue Haibing wrote: > From: YueHaibing > > During randconfig builds, I occasionally run into an invalid configuration > > WARNING: unmet direct dependencies detected for DEVICE_PRIVATE > Depends on [n]: ARCH_HAS_HMM_DEVICE [=n] && ZONE_DEVICE [=n] > S

Re: [PATCH 05/12] dma-buf: add explicit buffer pinning

On Wed, Apr 17, 2019 at 04:30:51PM +0200, Daniel Vetter wrote: > On Wed, Apr 17, 2019 at 04:20:02PM +0200, Daniel Vetter wrote: > > On Tue, Apr 16, 2019 at 08:38:34PM +0200, Christian König wrote: > > > Add optional explicit pinning callbacks instead of implicitly assume the > > > exporter pins the

Re: [PATCH v2 02/12] drm/fb-helper: Avoid race with DRM userspace

Den 17.04.2019 15.26, skrev Daniel Vetter: > On Wed, Apr 17, 2019 at 03:24:00PM +0200, Daniel Vetter wrote: >> On Tue, Apr 16, 2019 at 08:46:24PM +0200, Noralf Trønnes wrote: >>> >>> >>> Den 16.04.2019 09.59, skrev Daniel Vetter: On Sun, Apr 07, 2019 at 06:52:33PM +0200, Noralf Trønnes wrote

[Bug 109281] [CI][SHARDS] igt@gem_ctx_isolation@* - skip - WARNING: GEN not recognized!

https://bugs.freedesktop.org/show_bug.cgi?id=109281 --- Comment #5 from Martin Peres --- (In reply to Chris Wilson from comment #4) > commit 67c72249d963a30a681c204b5aad1563dc98d92c > Author: Dale B Stimson > Date: Mon Mar 4 17:03:08 2019 -0800 > > gem_ctx_isolation.c - Gen11 enabling for

[Bug 109281] [CI][SHARDS] igt@gem_ctx_isolation@* - skip - WARNING: GEN not recognized!

https://bugs.freedesktop.org/show_bug.cgi?id=109281 --- Comment #6 from CI Bug Log --- The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. -- You are receiving this mail because: You are the assignee

Re: [PATCH v2 3/5] drm/modes: Allow to specify rotation and reflection on the commandline

Den 17.04.2019 16.30, skrev Maxime Ripard: > Hi Noralf, > > On Tue, Apr 16, 2019 at 04:50:00PM +0200, Noralf Trønnes wrote: >> Den 11.04.2019 15.22, skrev Maxime Ripard: >>> Rotations and reflections setup are needed in some scenarios to initialise >>> properly the initial framebuffer. Some driv

Re: [PATCH v2 4/5] drm/modes: Parse overscan properties

Den 17.04.2019 16.07, skrev Maxime Ripard: > Hi Noralf, > > On Tue, Apr 16, 2019 at 04:52:20PM +0200, Noralf Trønnes wrote: >> Den 11.04.2019 15.22, skrev Maxime Ripard: >>> Properly configuring the overscan properties might be needed for the >>> initial setup of the framebuffer for display that

Re: [PATCH v2 4/5] drm/modes: Parse overscan properties

Den 17.04.2019 17.30, skrev Noralf Trønnes: > > > Den 17.04.2019 16.07, skrev Maxime Ripard: >> Hi Noralf, >> >> On Tue, Apr 16, 2019 at 04:52:20PM +0200, Noralf Trønnes wrote: >>> Den 11.04.2019 15.22, skrev Maxime Ripard: Properly configuring the overscan properties might be needed for t

Re: [PATCH 00/20] drm: Split out the formats API and move it to a common place

On Wed, Apr 17, 2019 at 09:54:26AM +0200, Maxime Ripard wrote: > Hi, > > DRM comes with an extensive format support to retrieve the various > parameters associated with a given format (such as the subsampling, or the > bits per pixel), as well as some helpers and utilities to ease the driver > dev

Applied "spi: Add spi_is_bpw_supported()" to the spi tree

The patch spi: Add spi_is_bpw_supported() has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus dur

Re: [PATCH v2 09/12] drm/fb-helper: Remove drm_fb_helper_connector

Hi, On Tue, Apr 16, 2019 at 04:57:58PM +0200, Noralf Trønnes wrote: > Den 16.04.2019 11.42, skrev Maxime Ripard: > > Hi, > > > > On Sun, Apr 07, 2019 at 06:52:40PM +0200, Noralf Trønnes wrote: > >> All drivers add all their connectors so there's no need to keep around an > >> array of available co

Re: [PATCH -next] drm/sun4i: Make some symbols static

On Tue, Apr 16, 2019 at 10:58:55PM +0800, Yue Haibing wrote: > From: YueHaibing > > Fix sparse warnings: > > drivers/gpu/drm/sun4i/sun8i_tcon_top.c:271:36: warning: symbol > 'sun8i_r40_tcon_top_quirks' was not declared. Should it be static? > drivers/gpu/drm/sun4i/sun8i_tcon_top.c:276:36: warning

Re: [PATCH 03/12] dma-buf: lock the reservation object during (un)map_dma_buf v3

Am 17.04.19 um 16:26 schrieb Daniel Vetter: On Wed, Apr 17, 2019 at 04:14:32PM +0200, Christian König wrote: Am 17.04.19 um 16:08 schrieb Daniel Vetter: On Tue, Apr 16, 2019 at 08:38:32PM +0200, Christian König wrote: Make it mandatory for dynamic dma-buf callbacks to be called with the reserv

[Bug 109060] android-x86 64bit builds crashes due to android/gralloc_handle.h

https://bugs.freedesktop.org/show_bug.cgi?id=109060 Emil Velikov changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

I can't review this patch, since I'm one of the authors of it, but in general your changes look good to me now. For patch #5 I think it might be cleaner if we move incrementing of the hw_rq_count while starting the scheduler again. Regards, Christian. Am 17.04.19 um 16:36 schrieb Grodzovsky,

Re: [PATCH] drm/amdgpu: fix drm leases being broken on radv

Am 17.04.19 um 17:51 schrieb Emil Velikov: > Hi guys, > > On 2019/04/17, Daniel Vetter wrote: >> On Wed, Apr 17, 2019 at 02:46:06PM +0200, Christian König wrote: >>> Am 17.04.19 um 14:35 schrieb Daniel Vetter: On Wed, Apr 17, 2019 at 12:06:32PM +, Koenig, Christian wrote: > Am 17.04.19

Re: [PATCH] drm: support gpu aliases defined in DT data

Hi Tomi, On Fri, 18 Jan 2019 at 08:29, Tomi Valkeinen wrote: > > On 18/01/19 00:04, Rob Herring wrote: > > > Mesa/libdrm already has lots of code to open the correct devices and > > not care about minor numbers. What's the problem here? > > Well, maybe the problem is that I don't know how to do t

Re: [PATCH] android: libdrm_platform: add liblog shared dependency

On Mon, 18 Mar 2019 at 13:32, Tapani Pälli wrote: > On 3/18/19 3:25 PM, Robert Foss wrote: > > Hey, > > > > On 3/18/19 2:11 PM, Mauro Rossi wrote: > >> Hi, > >> > >> On Mon, Mar 18, 2019 at 10:58 AM Robert Foss > >> wrote: > >>> > >>> Hey Mauro, > >>> > >>> On 3/18/19 9:38 AM, Mauro Rossi wrote:

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

On 4/17/19 1:17 PM, Christian König wrote: > I can't review this patch, since I'm one of the authors of it, but in > general your changes look good to me now. > > For patch #5 I think it might be cleaner if we move incrementing of > the hw_rq_count while starting the scheduler again. But the i

Re: [PATCH v2 08/12] drm/fb-helper: Move out commit code

Den 16.04.2019 10.38, skrev Daniel Vetter: > On Sun, Apr 07, 2019 at 06:52:39PM +0200, Noralf Trønnes wrote: >> Move the modeset commit code to drm_client_modeset. >> No changes except exporting API. >> >> v2: Move to drm_client_modeset.c instead of drm_client.c >> >> Signed-off-by: Noralf Trønne

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

Am 17.04.19 um 19:53 schrieb Grodzovsky, Andrey: On 4/17/19 1:17 PM, Christian König wrote: I can't review this patch, since I'm one of the authors of it, but in general your changes look good to me now. For patch #5 I think it might be cleaner if we move incrementing of the hw_rq_count while s

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

Am 17.04.19 um 19:59 schrieb Christian König: > Am 17.04.19 um 19:53 schrieb Grodzovsky, Andrey: >> On 4/17/19 1:17 PM, Christian König wrote: >>> I can't review this patch, since I'm one of the authors of it, but in >>> general your changes look good to me now. >>> >>> For patch #5 I think it migh

Re: [RFC][PATCH] libdrm: tests: Add planetest test from AOSP sources

On Wed, 17 Apr 2019 at 12:41, Benjamin Gaignard wrote: > > Le mar. 16 avr. 2019 à 20:48, John Stultz a écrit : > > > > On Tue, Apr 16, 2019 at 11:29 AM Sean Paul wrote: > > > On Tue, Apr 16, 2019 at 09:43:49AM -0700, John Stultz wrote: > > > > In trying to further align the AOSP libdrm branch wi

Re: [PATCH 3/3] virtio-gpu api: VIRTIO_GPU_F_RESSOURCE_V2

On Wed, Apr 17, 2019 at 2:57 AM Gerd Hoffmann wrote: > > On Fri, Apr 12, 2019 at 04:34:20PM -0700, Chia-I Wu wrote: > > Hi, > > > > I am still new to virgl, and missed the last round of discussion about > > resource_create_v2. > > > > From the discussion below, semantically resource_create_v2 crea

Re: [PATCH v2 00/12] drm/fb-helper: Move modesetting code to drm_client

Den 16.04.2019 10.41, skrev Daniel Vetter: > On Sun, Apr 07, 2019 at 06:52:31PM +0200, Noralf Trønnes wrote: >> This moves the modesetting code from drm_fb_helper to drm_client so it >> can be shared by all internal clients. >> >> The main change this time is to attach the modeset array to >> drm

Support for 2D engines/blitters in V4L2 and DRM

Hi Nicolas, I'm detaching this thread from our V4L2 stateless decoding spec since it has drifted off and would certainly be interesting to DRM folks as well! For context: I was initially talking about writing up support for the Allwinner 2D engine as a DRM render driver, where I'd like to be able

Re: [PATCH libdrm] fix various typos

On Wed, 19 Dec 2018 at 16:25, Daniel Vetter wrote: > > On Wed, Dec 19, 2018 at 04:26:04PM +0100, Daniel Vetter wrote: > > On Wed, Dec 19, 2018 at 02:55:45PM +, Eric Engestrom wrote: > > > Saw a couple of typos fixes in the patch DragonFlyBSD carries [1], so > > > I ran codespell (a spell check

Re: [PATCH -next] drm/meson: Make some functions static

On 16/04/2019 13:23, Neil Armstrong wrote: > > > Le 13/04/2019 16:14, Yue Haibing a écrit : >> From: YueHaibing >> >> Fix sparse warnings: >> >> drivers/gpu/drm/meson/meson_viu.c:93:6: warning: symbol >> 'meson_viu_set_g12a_osd1_matrix' was not declared. Should it be static? >> drivers/gpu/drm/

Re: [PATCH libdrm] amdgpu/tests: drop unused local vars

On Wed, 19 Dec 2018 at 16:23, Eric Engestrom wrote: > > Signed-off-by: Eric Engestrom > --- > tests/amdgpu/vce_tests.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > Reviewed-by: Emil Velikov and pushed to master. Thanks -Emil ___ dri

Re: [PATCH libdrm] tests/modetest: add QCOM_COMPRESSED to supported modifiers list

On Fri, 1 Mar 2019 at 22:41, Fritz Koenig wrote: > > Signed-off-by: Fritz Koenig > --- > tests/modetest/modetest.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c > index 975dcbcd..9c85c07b 100644 > --- a/tests/modetest/modetest.c

Re: [PATCH libdrm] libdrm: Fix issue about differrent domainID but same BDF

On Mon, 25 Feb 2019 at 19:53, Deucher, Alexander wrote: > > > -Original Message- > > From: amd-gfx On Behalf Of Emil > > Velikov > > Sent: Monday, February 25, 2019 8:09 AM > > To: Alex Deucher > > Cc: Deng, Emily ; Maling list - DRI developers > de...@lists.freedesktop.org>; amd-gfx li

Re: [PATCH libdrm] tests/util: Add armada-drm driver

On Sun, 24 Mar 2019 at 21:04, Lubomir Rintel wrote: > > This makes the test utilities work with the Armada driver without the > necessity of using the -M argument. > > Signed-off-by: Lubomir Rintel > --- > tests/util/kms.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tests/util/kms.c

Re: [PATCH] drm/meson: add size and alignment requirements for dumb buffers

On 16/04/2019 12:20, Sky Zhou wrote: > > On 2019/4/8 17:01, Neil Armstrong wrote: >> The Amlogic SoCs Canvas buffers stride must be aligned on 64bytes >> and overall size should be aligned on PAGE width. >> >> Adds a custom dumb_create op to adds these requirements. >> >> Fixes: bbbe775ec5b5 ("drm

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

On 4/17/19 2:01 PM, Koenig, Christian wrote: > Am 17.04.19 um 19:59 schrieb Christian König: >> Am 17.04.19 um 19:53 schrieb Grodzovsky, Andrey: >>> On 4/17/19 1:17 PM, Christian König wrote: I can't review this patch, since I'm one of the authors of it, but in general your changes look

[PATCH libdrm] amdgpu: Add context priority override function.

This way we can override the priority of a single context using a master fd. Since we cannot usefully create an amdgpu device of a master fd without the fd deduplication kicking in this takes a plain fd. This can be used by e.g. radv to get high priority contexts using a master fd from the primar

Re: [PATCH 05/12] dma-buf: add explicit buffer pinning

On Wed, Apr 17, 2019 at 04:40:11PM +0200, Daniel Vetter wrote: > On Wed, Apr 17, 2019 at 04:30:51PM +0200, Daniel Vetter wrote: > > On Wed, Apr 17, 2019 at 04:20:02PM +0200, Daniel Vetter wrote: > > > On Tue, Apr 16, 2019 at 08:38:34PM +0200, Christian König wrote: > > > > Add optional explicit pin

Re: [PATCH 04/12] dma-buf: add optional invalidate_mappings callback v5

On Tue, Apr 16, 2019 at 08:38:33PM +0200, Christian König wrote: > Each importer can now provide an invalidate_mappings callback. > > This allows the exporter to provide the mappings without the need to pin > the backing store. > > v2: don't try to invalidate mappings when the callback is NULL, >

Re: [PATCH v4 3/5] drm/scheduler: rework job destruction

Am 17.04.19 um 20:29 schrieb Grodzovsky, Andrey: > On 4/17/19 2:01 PM, Koenig, Christian wrote: >> Am 17.04.19 um 19:59 schrieb Christian König: >>> Am 17.04.19 um 19:53 schrieb Grodzovsky, Andrey: On 4/17/19 1:17 PM, Christian König wrote: > I can't review this patch, since I'm one of the

Re: [PATCH 04/12] dma-buf: add optional invalidate_mappings callback v5

Am 17.04.19 um 21:07 schrieb Daniel Vetter: On Tue, Apr 16, 2019 at 08:38:33PM +0200, Christian König wrote: Each importer can now provide an invalidate_mappings callback. This allows the exporter to provide the mappings without the need to pin the backing store. v2: don't try to invalidate ma

Re: [PATCH libdrm] amdgpu: Add context priority override function.

Reviewed-by: Samuel Pitoiset On 4/17/19 8:33 PM, Bas Nieuwenhuizen wrote: This way we can override the priority of a single context using a master fd. Since we cannot usefully create an amdgpu device of a master fd without the fd deduplication kicking in this takes a plain fd. This can be use

Re: [PATCH libdrm] amdgpu: Add context priority override function.

On 2019-04-17 2:33 p.m., Bas Nieuwenhuizen wrote: This way we can override the priority of a single context using a master fd. Since we cannot usefully create an amdgpu device of a master fd without the fd deduplication kicking in this takes a plain fd. This can be used by e.g. radv to get hi

Re: [PATCH libdrm] amdgpu: Add context priority override function.

On Wed, Apr 17, 2019 at 9:21 PM Andres Rodriguez wrote: > > > > On 2019-04-17 2:33 p.m., Bas Nieuwenhuizen wrote: > > This way we can override the priority of a single context using a > > master fd. > > > > Since we cannot usefully create an amdgpu device of a master fd > > without the fd deduplic

Re: [Intel-gfx] [PATCH v5 0/2] drm: Add detection of changing of edid on between suspend and resume

On Mon, 2019-04-15 at 18:32 +0200, Daniel Vetter wrote: > On Thu, Apr 11, 2019 at 05:36:30PM +0300, Gwan-gyeong Mun wrote: > > This patch series fix missed detection of changing of edid on > > between > > suspend and resume. > > First patch fixes drm_helper_hdp_irq_event() in order to fix a > > bel

Re: [PATCH] drm/amdgpu: fix drm leases being broken on radv

On Thu, 18 Apr 2019 at 03:30, Koenig, Christian wrote: > > Am 17.04.19 um 17:51 schrieb Emil Velikov: > > Hi guys, > > > > On 2019/04/17, Daniel Vetter wrote: > >> On Wed, Apr 17, 2019 at 02:46:06PM +0200, Christian König wrote: > >>> Am 17.04.19 um 14:35 schrieb Daniel Vetter: > On Wed, Apr

Re: [PATCH 1/2] dt-bindings: drm/panel: simple: add lg, acx467akm-7 panel

On Wed, Mar 20, 2019 at 10:17 AM Brian Masney wrote: > On Tue, Mar 05, 2019 at 11:42:15PM +0100, Linus Walleij wrote: > > On Sat, Nov 24, 2018 at 9:06 PM Brian Masney wrote: > > > > > Add binding for the LG ACX467AKM-7 4.95" 1080×1920 LCD panel that is > > > found on the LG Nexus 5 (hammerhead) p

Re: [PATCH v3 1/5] drm/scheduler: rework job destruction

On 4/16/19 12:00 PM, Koenig, Christian wrote: > Am 16.04.19 um 17:42 schrieb Grodzovsky, Andrey: >> On 4/16/19 10:58 AM, Grodzovsky, Andrey wrote: >>> On 4/16/19 10:43 AM, Koenig, Christian wrote: Am 16.04.19 um 16:36 schrieb Grodzovsky, Andrey: > On 4/16/19 5:47 AM, Christian König wrote

[Bug 110214] radeonsi: xterm scrollback buffer disappears while Shift+PgUp and Shift+PgDn

https://bugs.freedesktop.org/show_bug.cgi?id=110214 --- Comment #79 from Diego Viola --- I found that a workaround for this issue is to add the following to my Xresources: XTerm.vt100.scaleHeight: 0.9 The default is 1.0 (which creates the problem), a value of 1.5 also makes it work (although fo

linux-next: Fixes tag needs some work in the drm-fixes tree

Hi all, In commit 453393369dc9 ("drm/ttm: fix incrementing the page pointer for huge pages") Fixes tag Fixes: e16858a7e6e7 drm/ttm: fix start page for huge page check in ttm_put_pages() has these problem(s): - Target SHA1 does not exist Did you mean Fixes: ac1e516d5a4c ("drm/ttm: fix

Re: [PATCH v2 3/5] drm/v3d: Add support for compute shader dispatch.

Eric Anholt writes: > The compute shader dispatch interface is pretty simple -- just pass in > the regs that userspace has passed us, with no CLs to run. However, > with no CL to run it means that we need to do manual cache flushing of > the L2 after the HW execution completes (for SSBO, atomic,

Re: [PATCH] drm: increase drm mmap_range size to 1TB

Adding dri-devel On 2019-04-17 6:15 p.m., Yang, Philip wrote: > After patch "drm: Use the same mmap-range offset and size for GEM and > TTM", application failed to create bo of system memory because drm > mmap_range size decrease to 64GB from original 1TB. This is not big > enough for applications

[Bug 110355] radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)

https://bugs.freedesktop.org/show_bug.cgi?id=110355 --- Comment #10 from Marek Olšák --- The bug has nothing to do with compute. The compute blit removed gfx-based blits from the gfx pipeline, which uncovered a bug in the driver. -- You are receiving this mail because: You are the assignee for

Re: [PATCH 1/2] drm/dp_aux: Use non-cyclic idr, add suffix option for aux device

On 2019-04-16 6:16 p.m., Lyude Paul wrote: > Sorry for the slow response, I've been really busy ;_; No worries :) > > On Fri, 2019-04-12 at 12:05 -0400, sunpeng...@amd.com wrote: >> From: Leo Li >> >> In preparation for adding aux devices for DP MST: >> >> 1. A non-cyclic idr is used for the

[Bug 102646] Screen flickering under amdgpu-experimental [buggy auto power profile]

https://bugs.freedesktop.org/show_bug.cgi?id=102646 --- Comment #82 from kyrotti...@yahoo.com --- My solution, well more of a workaround and since I had this problem even with default MESA that comes packaged with Kernel 5.05.XX, was to retune my monitor to my GPU instead of letting my GPU try to

RE: [PATCH libdrm] amdgpu: Add context priority override function.

Reviewed-by: Chunming Zhou > -Original Message- > From: dri-devel On Behalf Of Bas > Nieuwenhuizen > Sent: Thursday, April 18, 2019 2:34 AM > To: dri-devel@lists.freedesktop.org > Subject: [PATCH libdrm] amdgpu: Add context priority override function. > > This way we can override the pr

[git pull] drm fixes for 5.1-rc6

Hi Linus, Since Easter is looming for me, I'm just pushing whatever is in my tree, I'll see what else turns up and maybe I'll send another pull early next week if there is anything. tegra: - stream id programming fix - avoid divide by 0 for bad hdmi audio setup code ttm: - Hugepages fix - refcou

[PATCH 1/4] drm/amd/display: Add some debug output for VRR BTR.

Helps with debugging issues with low framerate compensation. Signed-off-by: Mario Kleiner --- .../amd/display/modules/freesync/freesync.c| 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c b/drivers/gpu/drm/amd/disp

Improvements to VRR below-the-range/low framerate compensation.

Hi This patch-series tries to improve amdgpu's below-the-range behaviour with Freesync, hopefully not only for my use case, but also for games etc. Patch 1/4 adds a bit of debug output i found very useful, so maybe worth adding? Patch 2/4 fixes a bug i found when reading over the freesync code.

<    1   2   3   >