From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Marc Herbert <Marc.Herbert@intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH V4] drm/i915/skl: SKL CDCLK change on modeset tracking VCO
Date: Fri, 12 Feb 2016 13:25:31 +0200 [thread overview]
Message-ID: <20160212112531.GI23290@intel.com> (raw)
In-Reply-To: <56BD3158.3070407@intel.com>
On Thu, Feb 11, 2016 at 05:11:52PM -0800, Marc Herbert wrote:
> [I'm cheating and doing this code review with the author watching over my shoulder]
>
> On 11/02/16 15:22, clinton.a.taylor@intel.com wrote:
> > From: Clint Taylor <clinton.a.taylor@intel.com>
> >
> > Track VCO frequency of SKL instead of the boot CDCLK and allow modeset
> > to set cdclk based on the max required pixel clock based on VCO
> > selected.
>
> Nit: the main point shouldn't come second.
>
> > The vco should be tracked at the atomic level and all CRTCs updated if
> > the required vco is changed. At this time the eDP pll is configured
> > inside the encoder which has no visibility into the atomic state.
>
> should be -> is
>
>
> > When eDP v1.4 panel that require the 8640 vco are available this may need
> > to be investigated.
>
> Just say that 8640 can't be tested yet.
>
> > V1: initial version
> > V2: add vco tracking in intel_dp_compute_config(), rename
> > skl_boot_cdclk.
> > V3: rebase, V2 feedback not possible as encoders are not aware of
> > atomic.
> > V4: track target vco is atomic state. modeset all CRTCs if vco changes
> >
> > Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
> > Cc: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_drv.h | 2 +-
> > drivers/gpu/drm/i915/intel_ddi.c | 2 +-
> > drivers/gpu/drm/i915/intel_display.c | 97 +++++++++++++++++++++++++++++-----
> > drivers/gpu/drm/i915/intel_dp.c | 10 ++--
> > drivers/gpu/drm/i915/intel_drv.h | 4 ++
> > 5 files changed, 97 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> > index 8216665..f65dd1a 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.h
> > +++ b/drivers/gpu/drm/i915/i915_drv.h
> > @@ -1822,7 +1822,7 @@ struct drm_i915_private {
> > int num_fence_regs; /* 8 on pre-965, 16 otherwise */
> >
> > unsigned int fsb_freq, mem_freq, is_ddr3;
> > - unsigned int skl_boot_cdclk;
> > + unsigned int skl_vco_freq;
> > unsigned int cdclk_freq, max_cdclk_freq, atomic_cdclk_freq;
> > unsigned int max_dotclk_freq;
> > unsigned int hpll_freq;
> > diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> > index 6d5b09f..285adab 100644
> > --- a/drivers/gpu/drm/i915/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/intel_ddi.c
> > @@ -2958,7 +2958,7 @@ void intel_ddi_pll_init(struct drm_device *dev)
> > int cdclk_freq;
> >
> > cdclk_freq = dev_priv->display.get_display_clock_speed(dev);
> > - dev_priv->skl_boot_cdclk = cdclk_freq;
> > + dev_priv->skl_vco_freq = skl_cdclk_get_vco(cdclk_freq);
>
> - skl_cdclk_get_vco() and skl_cdclk_frequencies[] should probably be renamed to:
> + skl_get_bios_cdclk_vco() and skl_bios_cdclk_frequencies[]
>
> to avoid confusion with the (different) mapping used in the new skl_modeset_calc_cdclk()
> function below.
Let's not. This stuff doesn't really have anything to do with the BIOS.
We just want to read out the current hardware state, nothing more.
--
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:[~2016-02-12 11:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 0:15 [PATCH] drm/i915/skl: SKL CDCLK change on modeset tracking VCO clinton.a.taylor
2015-12-09 20:53 ` Ville Syrjälä
2016-02-10 0:28 ` [PATCH V3] " clinton.a.taylor
2016-02-10 3:29 ` Thulasimani, Sivakumar
2016-02-10 22:58 ` Clint Taylor
2016-02-10 14:27 ` Ville Syrjälä
2016-02-11 1:37 ` Marc Herbert
2016-02-11 8:29 ` Daniel Vetter
2016-02-11 10:48 ` Ville Syrjälä
2016-02-10 9:43 ` ✗ Fi.CI.BAT: failure for drm/i915/skl: SKL CDCLK change on modeset tracking VCO (rev2) Patchwork
2016-02-11 23:22 ` [PATCH V4] drm/i915/skl: SKL CDCLK change on modeset tracking VCO clinton.a.taylor
2016-02-12 1:11 ` Marc Herbert
2016-02-12 11:25 ` Ville Syrjälä [this message]
2016-02-12 11:18 ` Ville Syrjälä
2016-02-12 18:51 ` Clint Taylor
2016-02-13 2:06 ` [PATCH V5] " clinton.a.taylor
2016-02-15 13:16 ` Ville Syrjälä
2016-02-16 2:44 ` Thulasimani, Sivakumar
2016-02-16 9:45 ` ✗ Fi.CI.BAT: warning for drm/i915/skl: SKL CDCLK change on modeset tracking VCO (rev4) Patchwork
2016-02-16 17:19 ` [PATCH V6] drm/i915/skl: SKL CDCLK change on modeset tracking VCO clinton.a.taylor
2016-02-16 17:44 ` [PATCH V7] " clinton.a.taylor
2016-02-17 16:56 ` Ville Syrjälä
2016-02-25 13:49 ` Ville Syrjälä
2016-02-25 23:52 ` Clint Taylor
2016-02-16 17:48 ` ✓ Fi.CI.BAT: success for drm/i915/skl: SKL CDCLK change on modeset tracking VCO (rev5) Patchwork
2016-03-09 21:58 ` [PATCH V8] drm/i915/skl: SKL CDCLK change on modeset tracking VCO clinton.a.taylor
2016-03-10 8:08 ` Maarten Lankhorst
2016-03-11 17:04 ` Clint Taylor
2016-03-10 13:35 ` Ville Syrjälä
2016-03-10 7:00 ` ✗ Fi.CI.BAT: warning for drm/i915/skl: SKL CDCLK change on modeset tracking VCO (rev7) Patchwork
2016-03-10 18:42 ` [PATCH V9] drm/i915/skl: SKL CDCLK change on modeset tracking VCO clinton.a.taylor
2016-03-10 21:43 ` [PATCH V10] " clinton.a.taylor
2016-03-11 7:09 ` ✗ Fi.CI.BAT: failure for drm/i915/skl: SKL CDCLK change on modeset tracking VCO (rev9) Patchwork
2016-03-15 21:34 ` [PATCH V11] drm/i915/skl: SKL CDCLK change on modeset tracking VCO clinton.a.taylor
2016-03-16 7:27 ` Daniel Vetter
2016-03-16 23:28 ` Clint Taylor
2016-03-17 21:18 ` Rodrigo Vivi
2016-03-17 21:38 ` Clint Taylor
2016-03-16 10:01 ` ✗ Fi.CI.BAT: failure for drm/i915/skl: SKL CDCLK change on modeset tracking VCO (rev10) 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=20160212112531.GI23290@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=Marc.Herbert@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).