From: Simon Ser <contact@emersion.fr>
To: Pekka Paalanen <ppaalanen@gmail.com>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
amd-gfx@lists.freedesktop.org, tzimmermann@suse.de,
intel-gfx@lists.freedesktop.org, sunpeng.li@amd.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
airlied@linux.ie, rodrigo.vivi@intel.com,
alexander.deucher@amd.com, christian.koenig@amd.com
Subject: Re: [PATCH v4 12/17] drm/uAPI: Add "preferred color format" drm property as setting for userspace
Date: Tue, 29 Jun 2021 08:12:54 +0000 [thread overview]
Message-ID: <jIDQ2rRRMWlhDDPf08Z8xZlEE8HTBx7fHsylFdK0joSSFVyES8D444Giyiji9zbIm7dU4QpbsXZLvIDTbGW0wEoUWKsMEI4evizn0UdGMvM=@emersion.fr> (raw)
In-Reply-To: <20210622101516.6a53831c@eldfell>
On Tuesday, June 22nd, 2021 at 09:15, Pekka Paalanen <ppaalanen@gmail.com> wrote:
> yes, I think this makes sense, even if it is a property that one can't
> tell for sure what it does before hand.
>
> Using a pair of properties, preference and active, to ask for something
> and then check what actually worked is good for reducing the
> combinatorial explosion caused by needing to "atomic TEST_ONLY commit"
> test different KMS configurations. Userspace has a better chance of
> finding a configuration that is possible.
>
> OTOH, this has the problem than in UI one cannot tell the user in
> advance which options are truly possible. Given that KMS properties are
> rarely completely independent, and in this case known to depend on
> several other KMS properties, I think it is good enough to know after
> the fact.
>
> If a driver does not use what userspace prefers, there is no way to
> understand why, or what else to change to make it happen. That problem
> exists anyway, because TEST_ONLY commits do not give useful feedback
> but only a yes/no.
By submitting incremental atomic reqs with TEST_ONLY (i.e. only changing one
property at a time), user-space can discover which property makes the atomic
commit fail.
I'm not a fan of this "preference" property approach. The only way to find out
whether it's possible to change the color format is to perform a user-visible
change (with a regular atomic commit) and check whether it worked
after-the-fact. This is unlike all other existing KMS properties.
I'd much rather see a more general approach to fix this combinatorial explosion
than to add special-cases like this.
next prev parent reply other threads:[~2021-06-29 8:13 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 9:10 [PATCH v4 00/17] New uAPI drm properties for color management Werner Sembach
2021-06-18 9:11 ` [PATCH v4 01/17] drm/amd/display: Remove unnecessary SIGNAL_TYPE_HDMI_TYPE_A check Werner Sembach
2021-06-18 9:11 ` [PATCH v4 02/17] drm/amd/display: Add missing cases convert_dc_color_depth_into_bpc Werner Sembach
2021-06-18 9:11 ` [PATCH v4 03/17] drm/uAPI: Add "active bpc" as feedback channel for "max bpc" drm property Werner Sembach
2021-06-22 6:46 ` Pekka Paalanen
2021-06-28 17:03 ` Werner Sembach
2021-06-29 11:02 ` Werner Sembach
2021-06-30 8:21 ` Pekka Paalanen
2021-06-30 9:42 ` Werner Sembach
2021-07-01 7:42 ` Pekka Paalanen
2021-07-01 11:30 ` Werner Sembach
2021-07-14 18:18 ` Werner Sembach
2021-07-15 9:10 ` Pekka Paalanen
2021-06-18 9:11 ` [PATCH v4 04/17] drm/amd/display: Add handling for new "active bpc" property Werner Sembach
2021-06-18 9:11 ` [PATCH v4 05/17] drm/i915/display: " Werner Sembach
2021-06-18 9:11 ` [PATCH v4 06/17] drm/uAPI: Add "active color format" drm property as feedback for userspace Werner Sembach
2021-06-22 6:48 ` Pekka Paalanen
2021-06-18 9:11 ` [PATCH v4 07/17] drm/amd/display: Add handling for new "active color format" property Werner Sembach
2021-06-18 9:11 ` [PATCH v4 08/17] drm/i915/display: " Werner Sembach
2021-06-18 9:11 ` [PATCH v4 09/17] drm/uAPI: Add "active color range" drm property as feedback for userspace Werner Sembach
2021-06-22 7:00 ` Pekka Paalanen
2021-06-22 9:50 ` Werner Sembach
2021-06-22 11:48 ` Simon Ser
2021-06-23 7:32 ` Pekka Paalanen
2021-06-23 10:17 ` Werner Sembach
2021-06-23 11:14 ` Pekka Paalanen
2021-06-23 11:19 ` Werner Sembach
2021-06-18 9:11 ` [PATCH v4 10/17] drm/amd/display: Add handling for new "active color range" property Werner Sembach
2021-06-18 9:11 ` [PATCH v4 11/17] drm/i915/display: " Werner Sembach
2021-06-18 9:11 ` [PATCH v4 12/17] drm/uAPI: Add "preferred color format" drm property as setting for userspace Werner Sembach
2021-06-22 7:15 ` Pekka Paalanen
2021-06-29 8:12 ` Simon Ser [this message]
2021-06-29 11:17 ` Pekka Paalanen
2021-06-29 11:39 ` Werner Sembach
2021-06-30 8:41 ` Pekka Paalanen
2021-06-30 9:20 ` Werner Sembach
2021-07-01 8:07 ` Pekka Paalanen
2021-07-01 12:50 ` Werner Sembach
2021-07-01 13:24 ` Pekka Paalanen
2021-07-05 15:49 ` Werner Sembach
2021-07-06 7:09 ` Pekka Paalanen
2021-07-14 17:59 ` Werner Sembach
2021-06-18 9:11 ` [PATCH v4 13/17] drm/amd/display: Add handling for new "preferred color format" property Werner Sembach
2021-06-18 9:11 ` [PATCH v4 14/17] drm/i915/display: " Werner Sembach
2021-06-18 9:11 ` [PATCH v4 15/17] drm/uAPI: Move "Broadcast RGB" property from driver specific to general context Werner Sembach
2021-06-22 7:25 ` Pekka Paalanen
2021-06-22 9:57 ` Werner Sembach
2021-06-23 7:48 ` Pekka Paalanen
2021-06-23 10:10 ` Werner Sembach
2021-06-23 11:26 ` Pekka Paalanen
2021-06-25 8:48 ` Werner Sembach
2021-06-18 9:11 ` [PATCH v4 16/17] drm/i915/display: Use the general "Broadcast RGB" implementation Werner Sembach
2021-06-18 9:11 ` [PATCH v4 17/17] drm/amd/display: Add handling for new "Broadcast RGB" property Werner Sembach
2021-06-22 7:29 ` Pekka Paalanen
2021-06-22 9:28 ` Werner Sembach
2021-06-23 8:01 ` Pekka Paalanen
2021-06-23 9:58 ` Werner Sembach
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='jIDQ2rRRMWlhDDPf08Z8xZlEE8HTBx7fHsylFdK0joSSFVyES8D444Giyiji9zbIm7dU4QpbsXZLvIDTbGW0wEoUWKsMEI4evizn0UdGMvM=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ppaalanen@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
--cc=wse@tuxedocomputers.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;
as well as URLs for NNTP newsgroup(s).