public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Todd Previte <tprevite@gmail.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Enable 5.4Ghz (HBR2) link rate for Displayport 1.2-capable devices
Date: Fri, 17 Jan 2014 08:22:31 -0700	[thread overview]
Message-ID: <52D94AB7.5000303@gmail.com> (raw)
In-Reply-To: <20140117150810.GC20988@strange.amr.corp.intel.com>

On 1/17/2014 8:08 AM, Damien Lespiau wrote:
> On Fri, Jan 17, 2014 at 07:58:58AM -0700, Todd Previte wrote:
>>>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>>>> index 7df5085..f92d1c0 100644
>>>> --- a/drivers/gpu/drm/i915/intel_dp.c
>>>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>>>> @@ -102,7 +102,10 @@ intel_dp_max_link_bw(struct intel_dp *intel_dp)
>>>>          case DP_LINK_BW_2_7:
>>>>                  break;
>>>>          case DP_LINK_BW_5_4: /* 1.2 capable displays may advertise higher bw */
>>>> -               max_link_bw = DP_LINK_BW_2_7;
>>>> +        if (intel_dp->dpcd[DP_DPCD_REV] == 0x12)
>>>> +            max_link_bw = DP_LINK_BW_5_4;
>>>> +        else
>>>> +            max_link_bw = DP_LINK_BW_2_7;
>>> Is this really required, i.e. do we have dp 1.1 machines in the wild
>>> which advertise 5.4 but can't? In any case you also need to have a
>>> IS_HSW || IS_BDW check here, since only those two platforms support
>>> 5.4 GHz.
>> I've not seen a case where a 1.1a capable device advertises HBR2,
>> no. I *have* seen the case where the sink reports that it only
>> supports RBR (1.62Ghz) but is in fact capable of 2.7Ghz. This is
>> more of a safety measure to eliminate potential training problems,
>> but is not strictly necessary to support HBR2. It does need the
>> IS_HSW || IS_BDW though, so I'll fix that and resend.
> Can we make it IS_HSW || INTEL_INFO(dev)->gen >= 8, we can't quite
> predict the future but new platforms supporting what old platforms do
> support is a bet we take elsewere.
>
Sounds like a better solution. I should have that integrated shortly.

-T

  reply	other threads:[~2014-01-17 15:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  3:06 [PATCH] drm/i915: Enable 5.4Ghz (HBR2) link rate for Displayport 1.2-capable devices Todd Previte
2014-01-17  6:30 ` Daniel Vetter
2014-01-17 14:58   ` Todd Previte
2014-01-17 15:08     ` Damien Lespiau
2014-01-17 15:22       ` Todd Previte [this message]
2014-01-17 11:55 ` Damien Lespiau
2014-01-17 13:32   ` Jani Nikula
2014-01-17 15:22     ` Todd Previte
2014-01-17 15:00   ` Todd Previte
2014-01-17 16:58 ` [PATCH V2] " Todd Previte
2014-01-17 16:58   ` [PATCH] " Todd Previte
2014-01-17 17:34     ` Daniel Vetter
2014-01-20 17:19 ` [PATCH v3] " Todd Previte
2014-01-20 17:19   ` Todd Previte
2014-01-21  9:26     ` Daniel Vetter

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=52D94AB7.5000303@gmail.com \
    --to=tprevite@gmail.com \
    --cc=damien.lespiau@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