From: Javier Martinez Canillas <javierm@redhat.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
Maxime Ripard <mripard@kernel.org>
Cc: tzimmermann@suse.de, dri-devel@lists.freedesktop.org,
ppaalanen@gmail.com, airlied@redhat.com
Subject: Re: [PATCH 1/1] drm/fourcc: Add documentation about software color conversion.
Date: Fri, 11 Aug 2023 18:12:57 +0200 [thread overview]
Message-ID: <87h6p5fth2.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <59344d6e-78f1-d691-7e38-0ffc33b6b078@redhat.com>
Jocelyn Falempe <jfalempe@redhat.com> writes:
Hello Jocelyn,
> On 10/08/2023 09:45, Maxime Ripard wrote:
>> Hi
>>
>> On Mon, Aug 07, 2023 at 03:45:15PM +0200, Jocelyn Falempe wrote:
>>> After discussions on IRC, the consensus is that the DRM drivers should
>>> not do software color conversion, and only advertise the supported formats.
>>> Update the doc accordingly so that the rule and exceptions are clear for
>>> everyone.
>>>
>>> Signed-off-by: Jocelyn Falempe <jfalempe@redhat.com>
>>> ---
>>> include/uapi/drm/drm_fourcc.h | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
>>> index 8db7fd3f743e..00a29152da9f 100644
>>> --- a/include/uapi/drm/drm_fourcc.h
>>> +++ b/include/uapi/drm/drm_fourcc.h
>>> @@ -38,6 +38,13 @@ extern "C" {
>>> * fourcc code, a Format Modifier may optionally be provided, in order to
>>> * further describe the buffer's format - for example tiling or compression.
>>> *
>>> + * DRM drivers should not do software color conversion, and only advertise the
>>> + * format they support in hardware. But there are two exceptions:
>>
>> I would do a bullet list here:
>> https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#lists-and-quote-like-blocks
>>
> ok, that would look better.
>
>>> + * The first is to support XRGB8888 if the hardware doesn't support it, because
>>> + * it's the de facto standard for userspace applications.
>>
>> We can also provide a bit more context here, something like:
>>
>> All drivers must support XRGB8888, even if the hardware cannot support
>> it. This has become the de-facto standard and a lot of user-space assume
>> it will be present.
>
> ok, I can add this before the first paragraph.
>>
Agreed with Maxime's suggestion but I would also mention that if XRGB8888
is not supported, the native formats should be the default and XRGB8888 be
only used as a fallback for user-space compatiblity. In other words, that
XRGB8888 must not be the default, e.g: mode_config.preferred_depth = 24 or
drm_fbdev_generic_setup(drm, 32) only if is a supported native format.
I agree with the general content of the patch, so if you post a v2 feel
free to add my
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-08-11 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 13:45 [PATCH 0/1] drm/fourcc: Add documentation about software color conversion Jocelyn Falempe
2023-08-07 13:45 ` [PATCH 1/1] " Jocelyn Falempe
2023-08-09 16:29 ` Simon Ser
2023-08-10 9:23 ` Jocelyn Falempe
2023-08-10 7:45 ` Maxime Ripard
2023-08-10 10:22 ` Jocelyn Falempe
2023-08-11 16:12 ` Javier Martinez Canillas [this message]
2023-08-18 13:24 ` Pekka Paalanen
2023-08-21 15:55 ` Maxime Ripard
2023-08-22 8:20 ` Pekka Paalanen
2023-08-22 15:49 ` Jocelyn Falempe
2023-08-23 8:11 ` Pekka Paalanen
2023-08-23 9:14 ` Jocelyn Falempe
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=87h6p5fth2.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=mripard@kernel.org \
--cc=ppaalanen@gmail.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