Intel-XE 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 v5 1/2] drm/i915/display/dp: Remove support for UHBR13.5
Date: Fri, 04 Apr 2025 15:34:34 +0300	[thread overview]
Message-ID: <87r028yujp.fsf@intel.com> (raw)
In-Reply-To: <20250404-dprates-v5-1-c93f561a095e@intel.com>

On Fri, 04 Apr 2025, Arun R Murthy <arun.r.murthy@intel.com> wrote:
> The retimer issue for UHBR13.5 is fixed in BMG.

As I said before, I don't even know what "the retimer issue" was. It's
never been explained anywhere. Please explain it to me. And don't send a
new version of the patch.

BR,
Jani.


> So for all platforms lesser than BMG(XE2_HPD/DISPLAY_VERx100 1401)
> disable UHBR13.5.
> commit caf3d748f646 ("drm/i915/dp: Remove support for UHBR13.5")
> removes UHBR13.5 for MTL.
>
> v2: Reframed the commit msg (Jani)
> v4: Reframed the commit msg & update the max rate supported (Jani)
> v5: Reframed the commit msg (Jani)
>
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index f21f9b441fc2a4e644c69410e6ec6b3d37907478..92bca701a989b03e2ad4b3d9e7d0a9ef12567e5a 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -481,7 +481,7 @@ bool intel_dp_has_joiner(struct intel_dp *intel_dp)
>  
>  static int dg2_max_source_rate(struct intel_dp *intel_dp)
>  {
> -	return intel_dp_is_edp(intel_dp) ? 810000 : 1350000;
> +	return intel_dp_is_edp(intel_dp) ? 810000 : 1000000;
>  }
>  
>  static int icl_max_source_rate(struct intel_dp *intel_dp)
> @@ -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-04 12:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04  4:55 [PATCH v5 0/2] Remove support for UHBR13.5 Arun R Murthy
2025-04-04  4:55 ` [PATCH v5 1/2] drm/i915/display/dp: " Arun R Murthy
2025-04-04 12:34   ` Jani Nikula [this message]
2025-04-14  5:37   ` Murthy, Arun R
2025-04-14  9:46     ` Jani Nikula
2025-04-04  4:55 ` [PATCH v5 2/2] drm/i915/display/dp: Remove the uhbr13.5 pll state values Arun R Murthy
2025-04-14  9:49   ` Jani Nikula
2025-04-04  7:11 ` ✓ CI.Patch_applied: success for Remove support for UHBR13.5 Patchwork
2025-04-04  7:11 ` ✓ CI.checkpatch: " Patchwork
2025-04-04  7:12 ` ✓ CI.KUnit: " Patchwork
2025-04-04  7:29 ` ✓ CI.Build: " Patchwork
2025-04-04  7:31 ` ✓ CI.Hooks: " Patchwork
2025-04-04  7:33 ` ✓ CI.checksparse: " Patchwork
2025-04-04  8:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-04 18:35 ` ✗ Xe.CI.Full: 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=87r028yujp.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