From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "Conselvan De Oliveira,
Ander" <ander.conselvan.de.oliveira@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH v2 2/2] drm/i915: Implement cdclk restrictions based on Azalia BCLK
Date: Wed, 15 Mar 2017 20:16:51 +0200 [thread overview]
Message-ID: <20170315181651.GW31595@intel.com> (raw)
In-Reply-To: <1489602174.28483.13.camel@dk-H97M-D3H>
On Wed, Mar 15, 2017 at 06:03:58PM +0000, Pandiyan, Dhinakaran wrote:
> On Wed, 2017-03-15 at 11:32 +0200, Jani Nikula wrote:
> > On Tue, 14 Mar 2017, "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com> wrote:
> > > On Tue, 2017-03-14 at 17:47 -0300, Paulo Zanoni wrote:
> > >> Em Ter, 2017-03-07 às 16:12 -0800, Dhinakaran Pandiyan escreveu:
> > >> > According to BSpec, "The CD clock frequency must be at least twice
> > >> > the
> > >> > frequency of the Azalia BCLK." and BCLK is configured to 96 MHz by
> > >> > default. This check is needed because BXT and GLK support cdclk
> > >> > frequencies less than 192 MHz.
> > >> >
> > >> > Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > >> > ---
> > >> > drivers/gpu/drm/i915/intel_cdclk.c | 12 ++++++++++++
> > >> > 1 file changed, 12 insertions(+)
> > >> >
> > >> > diff --git a/drivers/gpu/drm/i915/intel_cdclk.c
> > >> > b/drivers/gpu/drm/i915/intel_cdclk.c
> > >> > index e8c1181..7b1ac1d 100644
> > >> > --- a/drivers/gpu/drm/i915/intel_cdclk.c
> > >> > +++ b/drivers/gpu/drm/i915/intel_cdclk.c
> > >> > @@ -1458,6 +1458,18 @@ static int
> > >> > bdw_adjust_min_pipe_pixel_rate(struct intel_crtc_state *crtc_state,
> > >> > pixel_rate = max(432000, pixel_rate);
> > >> > }
> > >> >
> > >> > + /* According to BSpec, "The CD clock frequency must be at
> > >> > least twice
> > >> > + * the frequency of the Azalia BCLK." and BCLK is 96 MHz by
> > >> > default.
> > >> > + * The check for GLK has to be adjusted as the platform can
> > >> > output
> > >> > + * two pixels per clock.
> > >> > + */
> > >> > + if (crtc_state->has_audio) {
> > >> > + if (IS_GEMINILAKE(dev_priv))
> > >> > + pixel_rate = max(2 * 2 * 96000, pixel_rate);
> > >> > + if (IS_BROXTON(dev_priv))
> > >>
> > >> SKL also documents this in the page that explains the cdclk freq change
> > >> sequences. The funny thing is that the minimum CDCLK for SKL seems to
> > >> be 308.57, so that's still bigger than 96*2... Anyway, having this for
> > >> completeness would probably be good, just in case I'm missing some
> > >> detail that's important here.
> > >>
> > >> I'd like to see the SKL addition, but I can live without it in case you
> > >> have some better argument, so if you don't send a new version, here's
> > >> it:
> > >>
> > >> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > >>
> > >>
> > >
> > > I did not include SKL as the lowest cdclk freq. it supports was higher
> > > than 2 * 96MHz. But, I agree it's good to include it for clarity. I'll
> > > send another version.
> > >
> > >
> > >> Perhaps it would also be interesting to have some sort of macro to
> > >> identify the platform(s) that need the magic *2 calculation. A more
> > >> confusion-proof version of this function would look like this:
> > >>
> > >> if (crtc_state->has_audio && INTEL_GEN(dev_priv) >= 9)
> > >> if (HAS_2_PIXELS_PER_CLOCK(dev_priv))
> >
> > I didn't check the spec (where's the fun in that?!) about the
> > terminology it uses, but isn't that just double data rate, or DDR?
> >
> > BR,
> > Jani.
> >
> >
>
> I found no reference to "DDR" in the spec., which thankfully avoids
> confusing this with the memory technology.
What this was called back in the gen2/3 days is "double wide pipe". We
could perhaps just keep using that name. Although the gen2/3 thing was
something you could enable/disable on demand.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-15 18:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 0:12 [PATCH v2 1/2] drm/i915/glk: Apply cdclk workaround for DP audio Dhinakaran Pandiyan
2017-03-08 0:12 ` [PATCH v2 2/2] drm/i915: Implement cdclk restrictions based on Azalia BCLK Dhinakaran Pandiyan
2017-03-14 20:47 ` Paulo Zanoni
2017-03-14 21:01 ` Pandiyan, Dhinakaran
2017-03-15 9:32 ` Jani Nikula
2017-03-15 18:03 ` Pandiyan, Dhinakaran
2017-03-15 18:16 ` Ville Syrjälä [this message]
2017-03-15 18:39 ` Paulo Zanoni
2017-03-15 19:30 ` Ville Syrjälä
2017-03-14 22:45 ` [PATCH v3 " Dhinakaran Pandiyan
2017-03-21 20:27 ` Paulo Zanoni
2017-03-29 8:50 ` [PATCH v2 " Ville Syrjälä
2017-03-29 21:16 ` Pandiyan, Dhinakaran
2017-03-30 11:42 ` Ville Syrjälä
2017-03-30 12:17 ` [Intel-gfx] " Takashi Iwai
2017-03-30 12:44 ` Ville Syrjälä
2017-03-30 18:14 ` Pandiyan, Dhinakaran
2017-03-08 0:48 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915/glk: Apply cdclk workaround for DP audio Patchwork
2017-03-14 20:24 ` [PATCH v2 1/2] " Paulo Zanoni
2017-03-15 8:33 ` ✗ Fi.CI.BAT: failure for series starting with [v2,1/2] drm/i915/glk: Apply cdclk workaround for DP audio (rev2) Patchwork
2017-03-15 8:47 ` ✓ Fi.CI.BAT: success " 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=20170315181651.GW31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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).