From: Jani Nikula <jani.nikula@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915/display/dp: Remove UHBR13.5 for icl
Date: Wed, 08 May 2024 14:47:58 +0300 [thread overview]
Message-ID: <87le4kjzip.fsf@intel.com> (raw)
In-Reply-To: <IA0PR11MB7307289257C865A660C59A73BAE52@IA0PR11MB7307.namprd11.prod.outlook.com>
On Wed, 08 May 2024, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
>> -----Original Message-----
>> From: Nikula, Jani <jani.nikula@intel.com>
>> Sent: Wednesday, May 8, 2024 3:29 PM
>> To: Murthy, Arun R <arun.r.murthy@intel.com>; Ville Syrjälä
>> <ville.syrjala@linux.intel.com>
>> Cc: intel-gfx@lists.freedesktop.org
>> Subject: RE: [PATCH] drm/i915/display/dp: Remove UHBR13.5 for icl
>>
>> 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?
>>
> Changed the commit msg as below
>
> Display 12+ hardware supports UHBR13.5
Not true.
> but due to the retimer constraints platform doesn't support UHBR13.5.
Which platform?
> This is the same for mtl and UHBR13.5 is removed as part of the commit caf3d748f646 ("drm/i915/dp: Remove support for UHBR13.5")
> This patch removes UHBR13.5 support for icl/dg2.
ICL does not support UHBR 13.5.
BR,
Jani.
>
> Thanks and Regards,
> Arun R Murthy
> --------------------
>> BR,
>> Jani.
>>
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-05-08 11:48 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ä
2024-05-08 11:43 ` Murthy, Arun R
2024-05-08 11:47 ` Jani Nikula [this message]
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=87le4kjzip.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).