Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: imre.deak@intel.com, Arun R Murthy <arun.r.murthy@intel.com>
Subject: Re: [PATCH v3 1/2] drm/i915/display/dp: Remove UHBR13.5 for icl
Date: Wed, 02 Apr 2025 13:29:41 +0300	[thread overview]
Message-ID: <87zfgy26wa.fsf@intel.com> (raw)
In-Reply-To: <8734eq3lic.fsf@intel.com>

On Wed, 02 Apr 2025, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 02 Apr 2025, Arun R Murthy <arun.r.murthy@intel.com> wrote:
>> Per Bspec display 14+ has uhbr13.5 Due to the retimer constraint none of
>> the Intel platforms support uhbr13.5.
>
> Those two sentences together make no sense.
>
> The subject makes no sense, because icl never supported UHBR.
>
>> This has been removed for mtl
>> by the commit caf3d748f646 ("drm/i915/dp: Remove support for UHBR13.5")
>> This patch will remove the support for DG2.
>
> "This patch" and "will" are unnecessary fillers. And once a patch is
> committed, "this patch" is meaningless.
>
> Just "Remove ..." is fine.
>
> dg2_max_source_rate() *still* refers to 1350000 as max rate, and that's
> arguably more important than the rates array. And you can just remove
> the entire function because it becomes a constant.

Except of course not, because that would drop UHBR support
completely. You just need to adjust the rate in the function to reflect
reality.

>
> BR,
> Jani.
>
>>
>> v2: Reframed the commit msg (Jani)
>>
>> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
>> ---
>>  drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index f21f9b441fc2a4e644c69410e6ec6b3d37907478..d7955351dd43ff61ebfd57e5b6a4ba99c1c7a2b2 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -550,7 +550,7 @@ intel_dp_set_source_rates(struct intel_dp *intel_dp)
>>  	};
>>  	static const int icl_rates[] = {
>>  		162000, 216000, 270000, 324000, 432000, 540000, 648000, 810000,
>> -		1000000, 1350000,
>> +		1000000,
>>  	};
>>  	static const int bxt_rates[] = {
>>  		162000, 216000, 243000, 270000, 324000, 432000, 540000

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-04-02 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  8:56 [PATCH v3 0/2] Remove UHBR13.5 for ICL, DG2 Arun R Murthy
2025-04-02  8:56 ` [PATCH v3 1/2] drm/i915/display/dp: Remove UHBR13.5 for icl Arun R Murthy
2025-04-02 10:28   ` Jani Nikula
2025-04-02 10:29     ` Jani Nikula [this message]
2025-04-02 10:39     ` Murthy, Arun R
2025-04-02  8:56 ` [PATCH v3 2/2] drm/i915/display/dp: Remove the uhbr13.5 pll state values Arun R Murthy
2025-04-02  9:53 ` ✗ Fi.CI.SPARSE: warning for Remove UHBR13.5 for ICL, DG2 Patchwork
2025-04-02 10:25 ` ✗ i915.CI.BAT: failure " Patchwork

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=87zfgy26wa.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.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