From: Mikko Perttunen <mperttunen@nvidia.com>
To: Thierry Reding <thierry.reding@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, Aaron Kling <webgeek1234@gmail.com>,
webgeek1234@gmail.com
Subject: Re: [PATCH v4 0/2] drm/tegra: Support YVU formats
Date: Wed, 28 Oct 2026 10:52:40 +0900 [thread overview]
Message-ID: <EUfz2J8BT1q-ycacwPVmVA@nvidia.com> (raw)
In-Reply-To: <20261025-tegra-drm-yvu420-v4-0-30b3bb0d0752@gmail.com>
On Monday, October 26, 2026 7:34 AM Aaron Kling via B4 Relay wrote:
> This is not directly supported by the display controller hardware.
> However, this can be handled efficiently on tegradc by just passing the
> chroma planes to the hardware backwards and reporting it as the yuv
> equivalent. Nvdisplay has a hardware flag to handle the swap in
> hardware.
>
> YVU420 is required by AOSP for software decoded video playback among
> other things. An attempt was made to handle this in gralloc by swapping
> the chroma planes there, but it wasn't working. This kernel
> implementation is working and is more generic anyways. This has been
> verified on a SHIELD TV 2019 Pro for the tegradc path and a Jetson TX2
> NX for the nvdisplay path.
>
> ---
> Changes in v4:
> - Drop yvu422 from the nvdisplay path. Yuv422 is not supported and will
> be removed separately
> - Link to v3: https://lore.kernel.org/r/20261020-tegra-drm-yvu420-v3-0-7f19a834ba98@gmail.com
>
> Changes in v3:
> - In patch 1, use the SWAP_UV window group flag instead of manually
> swapping for nvdisplay
> - In patch 2, support the chroma swapped variants of the other yuv types
> - Link to v2: https://lore.kernel.org/r/20261018-tegra-drm-yvu420-v2-0-512889103ab4@gmail.com
>
> Changes in v2:
> - In patch 1, simplify pre-nvdisplay path to a swap of the window base
> address
> - In patch 1, address sashiko report about failure to copy the new
> struct entry in duplicate_state
> - In patch 2, address sashiko report that yvu420 was missing from
> tegra20_overlays when the targets already support yuv420.
> - Link to v1: https://lore.kernel.org/r/20261008-tegra-drm-yvu420-v1-0-dc1c443c00f3@gmail.com
>
> ---
> Aaron Kling (2):
> drm/tegra: Support swapping chroma planes
> drm/tegra: Support YVU formats
>
> drivers/gpu/drm/tegra/dc.c | 13 ++++++++++++-
> drivers/gpu/drm/tegra/hub.c | 8 ++++++--
> drivers/gpu/drm/tegra/plane.c | 29 ++++++++++++++++++++++++++++-
> drivers/gpu/drm/tegra/plane.h | 3 ++-
> 4 files changed, 48 insertions(+), 5 deletions(-)
> ---
> base-commit: 20a33c6b6cbe7e4805dfb6cd68816937443aa148
> change-id: 20261008-tegra-drm-yvu420-1dbb7140e54a
>
> Best regards,
> --
> Aaron Kling <webgeek1234@gmail.com>
Series,
Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
Tested-by: Mikko Perttunen <mperttunen@nvidia.com> # Jetson AGX Xavier
Thank you!
prev parent reply other threads:[~2026-10-28 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 22:34 Aaron Kling via B4 Relay
2026-10-25 22:34 ` [PATCH v4 1/2] drm/tegra: Support swapping chroma planes Aaron Kling via B4 Relay
2026-10-25 22:34 ` [PATCH v4 2/2] drm/tegra: Support YVU formats Aaron Kling via B4 Relay
2026-10-28 1:52 ` Mikko Perttunen [this message]
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=EUfz2J8BT1q-ycacwPVmVA@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@kernel.org \
--cc=webgeek1234@gmail.com \
/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
all inboxes | Powered by JetHome®