All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Murthy, Arun R" <arun.r.murthy@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/display/dp: Remove UHBR13.5 for icl
Date: Wed, 8 May 2024 14:00:49 +0300	[thread overview]
Message-ID: <ZjtbYT_mrLj_XSyV@intel.com> (raw)
In-Reply-To: <87v83ok4kp.fsf@intel.com>

On Wed, May 08, 2024 at 12:58:46PM +0300, Jani Nikula wrote:
> On Wed, 08 May 2024, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
> > This is the limitation from the retimer hardware.
> 
> The commit message needs to reflect this.
> 
> Do all units have a retimer with the limitation? Or could you have a DG2
> without the limitation? Do we need to check for that instead of blanket
> removal of UHBR 13.5 for DG2?

And if we do remove it entirely then we should do it fully.
That is, don't leave behind unused PLL tables and whatnot.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-05-08 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  9:06 [PATCH] drm/i915/display/dp: Remove UHBR13.5 for icl Arun R Murthy
2024-05-06 10:00 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-05-06 12:05 ` [PATCH] " Ville Syrjälä
2024-05-06 12:15   ` Murthy, Arun R
2024-05-06 12:20     ` Ville Syrjälä
2024-05-08  3:15       ` Murthy, Arun R
2024-05-08  9:58         ` Jani Nikula
2024-05-08 11:00           ` Ville Syrjälä [this message]
2024-05-08 11:43           ` Murthy, Arun R
2024-05-08 11:47             ` Jani Nikula
2024-05-08 12:02               ` PATCH] " Murthy, Arun R
2024-05-08 12:22                 ` Jani Nikula
2024-05-06 12:53 ` ✗ Fi.CI.IGT: failure for " 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=ZjtbYT_mrLj_XSyV@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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.