From: Thierry Reding <thierry.reding@gmail.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: airlied@redhat.com, daniel@ffwll.ch, jonathanh@nvidia.com,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/tegra: handle implicit scanout modifiers
Date: Tue, 24 Jan 2023 15:25:09 +0100 [thread overview]
Message-ID: <Y8/qRSBm715P3EnB@orome> (raw)
In-Reply-To: <20230120105858.214440-1-diogo.ivo@tecnico.ulisboa.pt>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
On Fri, Jan 20, 2023 at 10:58:56AM +0000, Diogo Ivo wrote:
> Hello!
>
> This patch series adds support for correctly displaying tiled
> framebuffers when no modifiers are reported by userspace.
>
> Patch 1 adds the sector_layout parameter to the SET/GET_TILING
> IOCTLs so that userspace can set this field appropriately.
>
> Patch 2 adds handling of the case where the buffer object
> passed to create a framebuffer is allocated with non-linear
> tiling but no modifier is reported.
>
> Diogo Ivo (2):
> drm/tegra: add sector layout to SET/GET_TILING IOCTLs
> drm/tegra: add scanout support for implicit tiling parameters
>
> drivers/gpu/drm/tegra/drm.c | 29 ++++++++++++++++++
> drivers/gpu/drm/tegra/fb.c | 59 ++++++++++++++++++++++++++++++++++--
> include/uapi/drm/tegra_drm.h | 16 ++++++----
> 3 files changed, 96 insertions(+), 8 deletions(-)
We really don't want to use SET_TILING and GET_TILING IOCTLs anymore.
These only exist for backwards compatibility with very old userspace.
New code should use standard DRM/KMS mechanisms to deal with
framebuffer modifiers.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-24 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:58 [PATCH 0/2] drm/tegra: handle implicit scanout modifiers Diogo Ivo
2023-01-20 10:58 ` [PATCH 1/2] drm/tegra: add sector layout to SET/GET_TILING IOCTLs Diogo Ivo
2023-01-20 10:58 ` [PATCH 2/2] drm/tegra: add scanout support for implicit tiling parameters Diogo Ivo
2023-01-30 19:43 ` kernel test robot
2023-01-24 14:25 ` Thierry Reding [this message]
2023-01-30 14:49 ` [PATCH 0/2] drm/tegra: handle implicit scanout modifiers Diogo Ivo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y8/qRSBm715P3EnB@orome \
--to=thierry.reding@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox