Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display/dp: Remove support for UHBR13.5
Date: Tue, 27 Jun 2023 11:00:26 +0300	[thread overview]
Message-ID: <87ilb9tjvp.fsf@intel.com> (raw)
In-Reply-To: <DM6PR11MB3177476669BDEAA7C0096C80BA27A@DM6PR11MB3177.namprd11.prod.outlook.com>

On Tue, 27 Jun 2023, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
>> -----Original Message-----
>> From: Nikula, Jani <jani.nikula@intel.com>
>> Sent: Monday, June 26, 2023 6:02 PM
>> To: Murthy, Arun R <arun.r.murthy@intel.com>; intel-
>> gfx@lists.freedesktop.org
>> Cc: Deak, Imre <imre.deak@intel.com>; Kahola, Mika
>> <mika.kahola@intel.com>
>> Subject: RE: [PATCH] drm/i915/display/dp: Remove support for UHBR13.5
>>
>> On Thu, 22 Jun 2023, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
>> >> -----Original Message-----
>> >> From: Nikula, Jani <jani.nikula@intel.com>
>> >> Sent: Wednesday, June 21, 2023 2:27 PM
>> >> To: Murthy, Arun R <arun.r.murthy@intel.com>; intel-
>> >> gfx@lists.freedesktop.org
>> >> Cc: Deak, Imre <imre.deak@intel.com>; Kahola, Mika
>> >> <mika.kahola@intel.com>; Murthy, Arun R <arun.r.murthy@intel.com>
>> >> Subject: Re: [PATCH] drm/i915/display/dp: Remove support for UHBR13.5
>> >>
>> >> On Tue, 20 Jun 2023, Arun R Murthy <arun.r.murthy@intel.com> wrote:
>> >> > As per the DP2.1 Spec support for UHBR13.5 is optional. Hence
>> >> > removing the support for UHBR13.5
>> >>
>> >> That's just not a proper rationale. Please explain.
>> >>
>> > Programming for UHBR10 and UHBR20 is similar compared to UHBR13.5 As
>> > of now we have validated 10Gbps and 20Gbps. The spec also points out
>> > when 20Gbps is supported 13.5Gbps is optional so we have not
>> validated/implemented the UHBR13.5 Now we have the DP2.1 compatible
>> panel is market, expecting users can come up with UHBR13.5 not working.
>> Hence removing the support for 13.5Gbps for now.
>> > Maybe once we have support for UHBR13.5 in the driver we can enable
>> this.
>>
>> What's missing?
>>
> Port clock programming, pll values differs.
> This table has been in place but some corrections/recheck required.

Can we do that instead please?

I accidentally stumbled on the relevant gitlab issue [1] (please add
this kind of information up front in the future), so we have a reporter
that could test the fixes.

BR,
Jani.


[1] https://gitlab.freedesktop.org/drm/intel/-/issues/8686

>
> Thanks and Regards,
> Arun R Murthy
> --------------------

-- 
Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2023-06-27  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20  2:52 [Intel-gfx] [PATCH] drm/i915/display/dp: Remove support for UHBR13.5 Arun R Murthy
2023-06-20  3:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-20 10:31 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-06-21  8:49 ` [Intel-gfx] [PATCH] " Kandpal, Suraj
2023-06-21  9:01   ` Jani Nikula
2023-06-21  8:57 ` Jani Nikula
2023-06-22  4:44   ` Murthy, Arun R
2023-06-26 12:32     ` Jani Nikula
2023-06-27  7:30       ` Murthy, Arun R
2023-06-27  8:00         ` Jani Nikula [this message]

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=87ilb9tjvp.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@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