From: Jani Nikula <jani.nikula@linux.intel.com>
To: Pekka Paalanen <ppaalanen@gmail.com>, Simon Ser <contact@emersion.fr>
Cc: "Sebastian Wick" <sebastian.wick@redhat.com>,
"Michel Dänzer" <michel.daenzer@mailbox.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Jonas Ådahl" <jadahl@redhat.com>,
"Vitaly Prosyak" <vitaly.prosyak@amd.com>
Subject: Re: How should "max bpc" KMS property work?
Date: Mon, 30 May 2022 13:21:44 +0300 [thread overview]
Message-ID: <874k17tj5z.fsf@intel.com> (raw)
In-Reply-To: <20220525133647.052d09da@eldfell>
On Wed, 25 May 2022, Pekka Paalanen <ppaalanen@gmail.com> wrote:
> Use two separate KMS properties for reporting current vs.
> programming desired. The KMS property reporting the current value
> must be read-only (immutable). This preserves the difference between
> what userspace wanted and what it got, making it possible to read
> back both without confusing them. It also allows preserving driver behaviour
This seems like a common theme. Wondering if we should evolve helpers to
create a property pair like this in one go.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-05-30 10:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 8:35 How should "max bpc" KMS property work? Pekka Paalanen
2022-04-26 17:55 ` Ville Syrjälä
2022-04-27 10:52 ` Pekka Paalanen
2022-04-27 15:02 ` Michel Dänzer
2022-04-27 15:41 ` Harry Wentland
2022-04-27 21:29 ` Sebastian Wick
2022-04-28 7:50 ` Pekka Paalanen
2022-04-28 7:52 ` Simon Ser
2022-04-28 14:50 ` Ville Syrjälä
2022-04-28 19:00 ` Sebastian Wick
2022-05-20 15:20 ` Hans de Goede
2022-05-23 8:22 ` Pekka Paalanen
2022-05-23 11:54 ` Sebastian Wick
2022-05-24 9:36 ` Hans de Goede
2022-05-24 15:43 ` Ville Syrjälä
2022-05-24 22:03 ` Alex Deucher
2022-05-25 6:04 ` Simon Ser
2022-05-25 7:17 ` Pekka Paalanen
2022-05-25 8:42 ` Michel Dänzer
2022-05-25 7:28 ` Pekka Paalanen
2022-05-25 8:35 ` Michel Dänzer
2022-05-25 9:23 ` Simon Ser
2022-05-25 10:36 ` Pekka Paalanen
2022-05-30 10:21 ` Jani Nikula [this message]
2022-05-31 17:37 ` Ville Syrjälä
2022-06-01 7:21 ` How should "max bpc" and "Colorspace" " Pekka Paalanen
2022-06-01 7:26 ` Simon Ser
2022-06-01 14:06 ` Ville Syrjälä
2022-06-01 22:25 ` Sebastian Wick
2022-06-02 7:47 ` Pekka Paalanen
2022-06-02 16:40 ` Ville Syrjälä
2022-06-02 17:08 ` Sebastian Wick
2022-06-02 17:20 ` Ville Syrjälä
2022-06-03 7:19 ` Pekka Paalanen
2022-06-03 16:27 ` Ville Syrjälä
2022-04-26 19:38 ` How should "max bpc" " Alex Deucher
2022-04-26 19:55 ` Ville Syrjälä
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=874k17tj5z.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jadahl@redhat.com \
--cc=michel.daenzer@mailbox.org \
--cc=ppaalanen@gmail.com \
--cc=sebastian.wick@redhat.com \
--cc=vitaly.prosyak@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.