From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/cnl: Respect VBT max dp rate.
Date: Wed, 31 Jan 2018 21:22:18 -0800 [thread overview]
Message-ID: <20180201052218.vpnyecd4fhuqig7a@intel.com> (raw)
In-Reply-To: <1517454971.21203.24.camel@dk-H97M-D3H>
On Thu, Feb 01, 2018 at 02:53:20AM +0000, Pandiyan, Dhinakaran wrote:
>
>
>
> On Wed, 2018-01-31 at 13:20 -0800, Rodrigo Vivi wrote:
> > Since commit 'c4fb60b9aba9 ("drm/i915/bios: add DP max link
> > rate to VBT child device struct")' we have the new entry
> > defined for max dp rate that is in use for CNL.
> >
> > Let's start using it for all VBT 216+ and
> > also organize the cnl adjusted rates in terms of rate
> > and not array size.
> >
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_drv.h | 1 +
> > drivers/gpu/drm/i915/intel_bios.c | 3 +++
> > drivers/gpu/drm/i915/intel_dp.c | 37 +++++++++++++++++++++++++++++--------
> > 3 files changed, 33 insertions(+), 8 deletions(-)
>
> <snip>
>
> > +static int intel_dp_adjusted_max_rate(struct intel_dp *intel_dp)
> > +{
> > + struct intel_digital_port *dig_port = dp_to_dig_port(intel_dp);
> > + struct drm_i915_private *dev_priv = to_i915(dig_port->base.base.dev);
> > + const struct ddi_vbt_port_info *info =
> > + &dev_priv->vbt.ddi_port_info[dig_port->base.port];
> > +
> > + if (info->dp_max_link_rate)
> > + return info->dp_max_link_rate;
>
> What if this value is higher than cnl_adjusted_max_rate() ?
Then VBT knows something about that SKU that we don't?! *shrug*
My understanding is that the purpose of that new VBT field is
to workaround bugs they know for certain combination and limit
the max rate even more.
bugs like the one I had in a part here:
https://bugs.freedesktop.org/show_bug.cgi?id=103963
in this case flicker was gone by limiting the max rate.
But yeap, maybe vbt is bugged, so are you suggesting min(vbt, bspec) ?
>
> -DK
>
>
> > +
> > + if (IS_CANNONLAKE(dev_priv))
> > + return cnl_adjusted_max_rate(intel_dp);
> > +
> > + return INT_MAX; /* No adjusted limit */
> > }
> >
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-01 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 21:20 [PATCH] drm/i915/cnl: Respect VBT max dp rate Rodrigo Vivi
2018-01-31 22:14 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-31 23:51 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-01 2:53 ` [PATCH] " Pandiyan, Dhinakaran
2018-02-01 5:22 ` Rodrigo Vivi [this message]
2018-02-01 6:10 ` Pandiyan, Dhinakaran
2018-02-01 11:10 ` Jani Nikula
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=20180201052218.vpnyecd4fhuqig7a@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dhinakaran.pandiyan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox