[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240116114522.5b83d8b6@eldfell>
Date: Tue, 16 Jan 2024 11:45:22 +0200
From: Pekka Paalanen <ppaalanen@...il.com>
To: André Almeida <andrealmeid@...lia.com>
Cc: dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, kernel-dev@...lia.com,
alexander.deucher@....com, christian.koenig@....com, Simon Ser
<contact@...rsion.fr>, daniel@...ll.ch, Daniel Stone
<daniel@...ishbar.org>, 'Marek Olšák' <maraeo@...il.com>,
Dave Airlie <airlied@...il.com>, ville.syrjala@...ux.intel.com, Xaver Hugl
<xaver.hugl@...il.com>
Subject: Re: [PATCH 0/2] drm/atomic: Allow drivers to write their own plane
check for async
On Tue, 16 Jan 2024 01:51:57 -0300
André Almeida <andrealmeid@...lia.com> wrote:
> Hi,
>
> AMD hardware can do more on the async flip path than just the primary plane, so
> to lift up the current restrictions, this patchset allows drivers to write their
> own check for planes for async flips.
Hi,
what's the userspace story for this, how could userspace know it could do more?
What kind of userspace would take advantage of this and in what situations?
Or is this not meant for generic userspace?
Thanks,
pq
> I'm not sure if adding something new to drm_plane_funcs is the right way to do,
> because if we want to expand the other object types (crtc, connector) we would
> need to add their own drm_XXX_funcs, so feedbacks are welcome!
>
> André
>
> André Almeida (2):
> drm/atomic: Allow drivers to write their own plane check for async
> flips
> drm/amdgpu: Implement check_async_props for planes
>
> .../amd/display/amdgpu_dm/amdgpu_dm_plane.c | 30 +++++++++
> drivers/gpu/drm/drm_atomic_uapi.c | 62 ++++++++++++++-----
> include/drm/drm_atomic_uapi.h | 12 ++++
> include/drm/drm_plane.h | 5 ++
> 4 files changed, 92 insertions(+), 17 deletions(-)
>
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists