public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: "Kannan, Vandana" <vandana.kannan@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Adjust BXT HDMI port clock limits
Date: Fri, 10 Jul 2015 16:11:14 +0300	[thread overview]
Message-ID: <1436533874.28493.34.camel@intel.com> (raw)
In-Reply-To: <559CEF50.8060400@intel.com>

On ke, 2015-07-08 at 15:07 +0530, Kannan, Vandana wrote:
> 
> On 7/6/2015 5:14 PM, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Since
> >   commit e62925567c7926e78bc8ca976cde5c28ea265a49
> >   Author: Vandana Kannan <vandana.kannan@intel.com>
> >   Date:   Wed Jul 1 17:02:57 2015 +0530
> >
> >      drm/i915/bxt: BUNs related to port PLL
> >
> > BXT DPLL can now generate frequencies in the 216-223 MHz range.
> > Adjust the HDMI port clock checks to account for the reduced range
> > of invalid frequencies.
> >
> > Cc: Vandana Kannan <vandana.kannan@intel.com>
> > Cc: Imre Deak <imre.deak@intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >   drivers/gpu/drm/i915/intel_hdmi.c | 9 ++++++---
> >   1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> > index c7e912b..70bad5b 100644
> > --- a/drivers/gpu/drm/i915/intel_hdmi.c
> > +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> > @@ -1174,9 +1174,12 @@ hdmi_port_clock_valid(struct intel_hdmi *hdmi,
> >   	if (clock > hdmi_port_clock_limit(hdmi, respect_dvi_limit))
> >   		return MODE_CLOCK_HIGH;
> >
> > -	/* CHV/BXT DPLL can't generate 216-240 MHz */
> > -	if ((IS_CHERRYVIEW(dev) || IS_BROXTON(dev)) &&
> > -	    clock > 216000 && clock < 240000)
> > +	/* BXT DPLL can't generate 223-240 MHz */
> > +	if (IS_BROXTON(dev) && clock > 223333 && clock < 240000)
> > +		return MODE_CLOCK_RANGE;
> > +
> BSpec needs an update based on this ?
> It shows
> "
> HDMI/DVI link rates: 0.2 to 3.0 GHz Non-SSC*
> 
> *2.17 - 2.4 GHz not supported
> "

Yes, this needs updating. Could you file a change request for it?

--Imre

> 
> - Vandana
> > +	/* CHV DPLL can't generate 216-240 MHz */
> > +	if (IS_CHERRYVIEW(dev) && clock > 216000 && clock < 240000)
> >   		return MODE_CLOCK_RANGE;
> >
> >   	return MODE_OK;
> >


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-07-10 13:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 11:44 [PATCH] drm/i915: Adjust BXT HDMI port clock limits ville.syrjala
2015-07-08  9:37 ` Kannan, Vandana
2015-07-10 13:11   ` Imre Deak [this message]
2015-07-10 13:09 ` Imre Deak
2015-07-10 13:18   ` Damien Lespiau
2015-07-10 13:21     ` Ville Syrjälä
2015-07-10 13:27       ` Damien Lespiau
2015-07-13  9:05         ` Daniel Vetter
2015-07-13 17:32           ` Bish, Jim
2015-07-14  7:53             ` Daniel Vetter
2015-07-13  9:10   ` Daniel Vetter
2015-07-10 20:22 ` shuang.he

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=1436533874.28493.34.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vandana.kannan@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