From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Stone" <daniels@collabora.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Michel Dänzer" <michel.daenzer@mailbox.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org, kernel@collabora.com,
Derek Foreman <derek.foreman@collabora.com>,
Marius Vlad <marius.vlad@collabora.com>
Subject: Re: [PATCH v5 0/3] Add "link bpc" DRM property
Date: Tue, 24 Mar 2026 16:25:05 +0100 [thread overview]
Message-ID: <4265353.aeNJFYEL58@workhorse> (raw)
In-Reply-To: <eff61423-a854-44c1-8634-30e2bd61e005@mailbox.org>
On Monday, 23 March 2026 18:27:41 Central European Standard Time Michel Dänzer wrote:
> On 3/23/26 17:55, Nicolas Frattaroli wrote:
> >
> > "Someone might not understand its purpose" is, in my eyes, not a valid reason to
> > not have this property, [...]
> Per my previous posts, that's not my concern.
>
>
>
Then what is your concern? That the link-bpc property does not
consider DSC and dithering? Two things which the max-bpc property
also does not consider?
Please clearly state where your problem with this property is (and
not with how your understanding of the Weston MR uses it) so that
I can make forward progress here. If all you want is a clearer
description of the property in the comment that accompanies it,
then I can do that, and I said I agree with this point. But you
seem to be arguing from a position of not wanting the property to
exist at all, which is not something I can address. Userspace needs
a way to close the feedback loop here, or it won't be able to make
the right content-specific trade-offs.
Kind regards,
Nicolas Frattaroli
next prev parent reply other threads:[~2026-03-25 13:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 12:28 [PATCH v5 0/3] Add "link bpc" DRM property Nicolas Frattaroli
2026-03-19 12:28 ` [PATCH v5 1/3] drm/connector: Add a 'link bpc' property Nicolas Frattaroli
2026-03-19 12:28 ` [PATCH v5 2/3] drm/connector: hdmi: Add support for " Nicolas Frattaroli
2026-03-19 12:28 ` [PATCH v5 3/3] drm/amd/display: " Nicolas Frattaroli
2026-03-20 14:32 ` [PATCH v5 0/3] Add "link bpc" DRM property Michel Dänzer
2026-03-20 18:02 ` Nicolas Frattaroli
2026-03-21 2:33 ` Mario Kleiner
2026-03-23 11:44 ` Michel Dänzer
2026-03-23 10:55 ` Michel Dänzer
2026-03-23 12:05 ` Nicolas Frattaroli
2026-03-23 14:38 ` Michel Dänzer
2026-03-23 16:55 ` Nicolas Frattaroli
2026-03-23 17:27 ` Michel Dänzer
2026-03-24 15:25 ` Nicolas Frattaroli [this message]
2026-03-24 16:44 ` Michel Dänzer
2026-03-26 12:17 ` Nicolas Frattaroli
2026-03-30 16:57 ` Michel Dänzer
2026-03-30 18:52 ` Harry Wentland
2026-03-31 12:50 ` Pekka Paalanen
2026-03-31 17:47 ` Harry Wentland
2026-04-01 8:40 ` Daniel Stone
2026-04-01 11:10 ` Ville Syrjälä
2026-04-01 11:43 ` Daniel Stone
2026-04-01 12:46 ` Nicolas Frattaroli
2026-04-02 17:06 ` Harry Wentland
2026-04-01 13:57 ` Ville Syrjälä
2026-04-01 14:17 ` Daniel Stone
2026-04-02 2:55 ` Mario Kleiner
2026-04-02 17:01 ` Harry Wentland
2026-03-26 13:53 ` Pekka Paalanen
2026-03-30 19:01 ` Harry Wentland
2026-03-31 10:28 ` Pekka Paalanen
2026-03-31 17:37 ` Harry Wentland
2026-04-09 15:05 ` Nicolas Dufresne
2026-03-31 8:01 ` Michel Dänzer
2026-03-31 12:38 ` Pekka Paalanen
2026-03-31 12:56 ` Michel Dänzer
2026-03-31 14:21 ` Pekka Paalanen
2026-04-01 7:46 ` Michel Dänzer
2026-04-09 22:20 ` Dmitry Baryshkov
2026-04-01 11:57 ` Xaver Hugl
2026-04-01 12:11 ` Ville Syrjälä
2026-04-01 12:25 ` Daniel Stone
2026-04-01 12:56 ` Ville Syrjälä
2026-04-01 12:14 ` Nicolas Frattaroli
2026-04-03 10:23 ` Michel Dänzer
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=4265353.aeNJFYEL58@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniels@collabora.com \
--cc=derek.foreman@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marius.vlad@collabora.com \
--cc=michel.daenzer@mailbox.org \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.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.