From: Thierry Reding <thierry.reding@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
dri-devel@lists.freedesktop.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v3 7/8] drm/simpledrm: Support the XB24/AB24 format
Date: Fri, 18 Nov 2022 16:44:56 +0100 [thread overview]
Message-ID: <Y3eoeLLOxHaruPOV@orome> (raw)
In-Reply-To: <7018f094-e1f8-d82d-f4b2-b1ae833d1c47@suse.de>
[-- Attachment #1: Type: text/plain, Size: 3021 bytes --]
On Fri, Nov 18, 2022 at 04:08:23PM +0100, Thomas Zimmermann wrote:
> Hi
>
> Am 17.11.22 um 19:40 schrieb Thierry Reding:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Add XB24 and AB24 to the list of supported formats. The format helpers
> > support conversion to these formats and they are documented in the
> > simple-framebuffer device tree bindings.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Changes in v2:
> > - treat AB24 as XB24 and support both at the same time
> >
> > drivers/gpu/drm/tiny/simpledrm.c | 2 ++
> > include/linux/platform_data/simplefb.h | 1 +
> > 2 files changed, 3 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/tiny/simpledrm.c b/drivers/gpu/drm/tiny/simpledrm.c
> > index 7f39bc58da52..ba1c2057fc65 100644
> > --- a/drivers/gpu/drm/tiny/simpledrm.c
> > +++ b/drivers/gpu/drm/tiny/simpledrm.c
> > @@ -483,6 +483,8 @@ static int simpledrm_device_init_regulators(struct simpledrm_device *sdev)
> > static const uint32_t simpledrm_primary_plane_formats[] = {
> > DRM_FORMAT_XRGB8888,
> > DRM_FORMAT_ARGB8888,
> > + DRM_FORMAT_XBGR8888,
> > + DRM_FORMAT_ABGR8888,
>
> Does the hardware *really* support AB42 on its primary plane?
Yes, Tegra display hardware supports this format on the primary plane.
> We recently had a discussion about the exported formats and the consensus is
> that we only want the hardware's native formats plus XRGB888. That's not
> implemented yet in simpledrm, but this format list will soon see a larger
> cleanup.
>
> So I think ARGB8888 likely shouldn't be on the list here.
This is for consistency with the list below. If a device tree claims
that the framebuffer is ABGR8888 using the "a8b8g8r8" string, then
shouldn't we support it?
Thierry
>
> Best regards
> Thomas
>
> > DRM_FORMAT_RGB565,
> > //DRM_FORMAT_XRGB1555,
> > //DRM_FORMAT_ARGB1555,
> > diff --git a/include/linux/platform_data/simplefb.h b/include/linux/platform_data/simplefb.h
> > index 27ea99af6e1d..4f94d52ac99f 100644
> > --- a/include/linux/platform_data/simplefb.h
> > +++ b/include/linux/platform_data/simplefb.h
> > @@ -22,6 +22,7 @@
> > { "r8g8b8", 24, {16, 8}, {8, 8}, {0, 8}, {0, 0}, DRM_FORMAT_RGB888 }, \
> > { "x8r8g8b8", 32, {16, 8}, {8, 8}, {0, 8}, {0, 0}, DRM_FORMAT_XRGB8888 }, \
> > { "a8r8g8b8", 32, {16, 8}, {8, 8}, {0, 8}, {24, 8}, DRM_FORMAT_ARGB8888 }, \
> > + { "x8b8g8r8", 32, {0, 8}, {8, 8}, {16, 8}, {0, 0}, DRM_FORMAT_XBGR8888 }, \
> > { "a8b8g8r8", 32, {0, 8}, {8, 8}, {16, 8}, {24, 8}, DRM_FORMAT_ABGR8888 }, \
> > { "x2r10g10b10", 32, {20, 10}, {10, 10}, {0, 10}, {0, 0}, DRM_FORMAT_XRGB2101010 }, \
> > { "a2r10g10b10", 32, {20, 10}, {10, 10}, {0, 10}, {30, 2}, DRM_FORMAT_ARGB2101010 }, \
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Ivo Totev
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-18 15:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 18:40 [PATCH v3 0/8] drm/simpledrm: Support system memory framebuffers Thierry Reding
2022-11-17 18:40 ` [PATCH v3 1/8] dt-bindings: display: simple-framebuffer: " Thierry Reding
2022-11-17 18:40 ` [PATCH v3 2/8] dt-bindings: display: simple-framebuffer: Document 32-bit BGR format Thierry Reding
2022-11-17 18:40 ` [PATCH v3 3/8] dt-bindings: reserved-memory: Support framebuffer reserved memory Thierry Reding
2022-11-17 18:40 ` [PATCH v3 4/8] drm/simpledrm: Use struct iosys_map consistently Thierry Reding
2022-11-18 13:56 ` Thomas Zimmermann
2022-11-17 18:40 ` [PATCH v3 5/8] drm/simpledrm: Add support for system memory framebuffers Thierry Reding
2022-11-18 14:11 ` Thomas Zimmermann
2022-11-18 14:21 ` Thomas Zimmermann
2022-11-18 15:38 ` Thierry Reding
2022-11-18 15:54 ` Thomas Zimmermann
2022-11-18 16:28 ` Thierry Reding
2022-11-17 18:40 ` [PATCH v3 6/8] drm/format-helper: Support the XB24 format Thierry Reding
2022-11-18 15:00 ` Thomas Zimmermann
2022-11-17 18:40 ` [PATCH v3 7/8] drm/simpledrm: Support the XB24/AB24 format Thierry Reding
2022-11-18 15:08 ` Thomas Zimmermann
2022-11-18 15:44 ` Thierry Reding [this message]
2022-11-18 16:10 ` Thomas Zimmermann
2022-11-18 16:34 ` Thierry Reding
2022-11-17 18:40 ` [PATCH v3 8/8] arm64: tegra: Add simple framebuffer on Jetson Xavier NX Thierry Reding
2023-01-17 14:55 ` Thomas Zimmermann
2023-01-19 15:10 ` Thierry Reding
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=Y3eoeLLOxHaruPOV@orome \
--to=thierry.reding@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).