From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: <imre.deak@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <stable@vger.kernel.org>,
Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH v2 1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR
Date: Tue, 10 Feb 2026 11:44:33 +0530 [thread overview]
Message-ID: <90e05e50-dcc9-4516-8525-601821a09dab@intel.com> (raw)
In-Reply-To: <aYn_5pIAIq2C5Ezc@ideak-desk.lan>
On 2/9/2026 9:10 PM, Imre Deak wrote:
>>> - Don't print the 30 BPP-outside of valid BPP range debug message if
>>> the min BPP is already > 30 (and so a target BPP >= 30 required
>>> for HDR is ensured).
>> Does this match the current implementation?
> If you mean the logic that, after the point where the min/max pipe BPP
> based on the source/sink caps has been determined, constrains when the
> minimum pipe BPP is increased due to the requested HDR, then yes.
I was pointing to the last bullet but I got it now. Thank you.
==
Chaitanya
next prev parent reply other threads:[~2026-02-10 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 13:38 [PATCH v2 1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR Imre Deak
2026-02-09 13:38 ` [PATCH v2 2/2] drm/i915/dp: Verify valid pipe BPP range Imre Deak
2026-02-09 13:44 ` ✓ CI.KUnit: success for series starting with [v2,1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR Patchwork
2026-02-09 14:18 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-09 14:28 ` [PATCH v2 1/2] " Borah, Chaitanya Kumar
2026-02-09 15:40 ` Imre Deak
2026-02-10 6:14 ` Borah, Chaitanya Kumar [this message]
2026-02-09 17:17 ` ✗ Xe.CI.FULL: failure for series starting with [v2,1/2] " Patchwork
[not found] ` <177067695572.239579.15984876432204423723@a3b018990fe9>
2026-02-10 9:55 ` ✗ i915.CI.Full: " Imre Deak
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=90e05e50-dcc9-4516-8525-601821a09dab@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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