From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/8] drm/i915: Use cdclk_state->voltage on BDW
Date: Fri, 20 Oct 2017 19:14:45 +0300 [thread overview]
Message-ID: <20171020161445.GN10981@intel.com> (raw)
In-Reply-To: <20171019234434.z4gca6fnaepxzb3c@intel.com>
On Thu, Oct 19, 2017 at 04:44:34PM -0700, Rodrigo Vivi wrote:
> On Wed, Oct 18, 2017 at 08:48:21PM +0000, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Track the system agent voltage we request from pcode in the cdclk state
> > on BDW. Annoyingly we can't actually read out the current value since
> > there's no pcode command to do that, so we'll have to just assume that
> > it worked.
> >
> > Cc: Mika Kahola <mika.kahola@intel.com>
> > Cc: Manasi Navare <manasi.d.navare@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_cdclk.c | 36 ++++++++++++++++++++++++++----------
> > 1 file changed, 26 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_cdclk.c b/drivers/gpu/drm/i915/intel_cdclk.c
> > index df71667c9fd6..7442e9443ffa 100644
> > --- a/drivers/gpu/drm/i915/intel_cdclk.c
> > +++ b/drivers/gpu/drm/i915/intel_cdclk.c
> > @@ -648,6 +648,21 @@ static int bdw_calc_cdclk(int min_cdclk)
> > return 337500;
> > }
> >
> > +static u8 bdw_calc_voltage(int cdclk)
> > +{
> > + switch (cdclk) {
> > + default:
> > + case 337500:
> > + return 2;
> > + case 450000:
> > + return 0;
> > + case 540000:
> > + return 1;
> > + case 675000:
> > + return 3;
> > + }
> > +}
> > +
> > static void bdw_get_cdclk(struct drm_i915_private *dev_priv,
> > struct intel_cdclk_state *cdclk_state)
> > {
> > @@ -666,13 +681,19 @@ static void bdw_get_cdclk(struct drm_i915_private *dev_priv,
> > cdclk_state->cdclk = 337500;
> > else
> > cdclk_state->cdclk = 675000;
> > +
> > + /*
> > + * Can't read this out :( Let's assume it's
> > + * at least what the CDCLK frequency requires.
> > + */
> > + cdclk_state->voltage = bdw_calc_voltage(cdclk_state->cdclk);
> > }
> >
> > static void bdw_set_cdclk(struct drm_i915_private *dev_priv,
> > const struct intel_cdclk_state *cdclk_state)
> > {
> > int cdclk = cdclk_state->cdclk;
> > - uint32_t val, data;
> > + uint32_t val;
> > int ret;
> >
> > if (WARN((I915_READ(LCPLL_CTL) &
> > @@ -713,19 +734,15 @@ static void bdw_set_cdclk(struct drm_i915_private *dev_priv,
> > /* fall through */
> > case 337500:
> > val |= LCPLL_CLK_FREQ_337_5_BDW;
> > - data = 2;
> > break;
> > case 450000:
> > val |= LCPLL_CLK_FREQ_450;
> > - data = 0;
> > break;
> > case 540000:
> > val |= LCPLL_CLK_FREQ_54O_BDW;
> > - data = 1;
> > break;
> > case 675000:
> > val |= LCPLL_CLK_FREQ_675_BDW;
> > - data = 3;
> > break;
> > }
> >
> > @@ -740,16 +757,13 @@ static void bdw_set_cdclk(struct drm_i915_private *dev_priv,
> > DRM_ERROR("Switching back to LCPLL failed\n");
> >
> > mutex_lock(&dev_priv->pcu_lock);
> > - sandybridge_pcode_write(dev_priv, HSW_PCODE_DE_WRITE_FREQ_REQ, data);
> > + sandybridge_pcode_write(dev_priv, HSW_PCODE_DE_WRITE_FREQ_REQ,
> > + cdclk_state->voltage);
> > mutex_unlock(&dev_priv->pcu_lock);
> >
> > I915_WRITE(CDCLK_FREQ, DIV_ROUND_CLOSEST(cdclk, 1000) - 1);
> >
> > intel_update_cdclk(dev_priv);
> > -
> > - WARN(cdclk != dev_priv->cdclk.hw.cdclk,
> > - "cdclk requested %d kHz but got %d kHz\n",
> > - cdclk, dev_priv->cdclk.hw.cdclk);
>
> Why?
We don't have such a thing anywhere else either. It would be better
to stick something like that into a more central location. Probably
we should just go for a full cdclk state verification somewhere.
Apparently I forgot to split this out to a separate patch.
>
> > }
> >
> > static int skl_calc_cdclk(int min_cdclk, int vco)
> > @@ -1919,11 +1933,13 @@ static int bdw_modeset_calc_cdclk(struct drm_atomic_state *state)
> > cdclk = bdw_calc_cdclk(min_cdclk);
> >
> > intel_state->cdclk.logical.cdclk = cdclk;
> > + intel_state->cdclk.logical.voltage = bdw_calc_voltage(cdclk);
> >
> > if (!intel_state->active_crtcs) {
> > cdclk = bdw_calc_cdclk(0);
> >
> > intel_state->cdclk.actual.cdclk = cdclk;
> > + intel_state->cdclk.actual.voltage = bdw_calc_voltage(cdclk);
> > } else {
> > intel_state->cdclk.actual =
> > intel_state->cdclk.logical;
> > --
> > 2.13.6
> >
--
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-10-20 16:14 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:48 [PATCH 0/8] drm/i915: CNL DVFS thing Ville Syrjala
2017-10-18 20:48 ` [PATCH 1/8] drm/i915: Clean up some cdclk switch statements Ville Syrjala
2017-10-19 7:20 ` Mika Kahola
2017-10-18 20:48 ` [PATCH 2/8] drm/i915: Start tracking voltage level in the cdclk state Ville Syrjala
2017-10-19 23:32 ` Rodrigo Vivi
2017-10-20 14:01 ` Ville Syrjälä
2017-10-20 20:43 ` Rodrigo Vivi
2017-10-23 12:13 ` Ville Syrjälä
2017-10-23 17:14 ` Rodrigo Vivi
2017-10-18 20:48 ` [PATCH 3/8] drm/i915: USe cdclk_state->voltage on VLV/CHV Ville Syrjala
2017-10-19 17:43 ` [PATCH v2 3/8] drm/i915: Use " Ville Syrjala
2017-10-19 23:42 ` Rodrigo Vivi
2017-10-20 16:20 ` Ville Syrjälä
2017-10-20 17:03 ` [PATCH v3 " Ville Syrjala
2017-10-18 20:48 ` [PATCH 4/8] drm/i915: Use cdclk_state->voltage on BDW Ville Syrjala
2017-10-19 23:44 ` Rodrigo Vivi
2017-10-20 16:14 ` Ville Syrjälä [this message]
2017-10-20 17:03 ` [PATCH v2 " Ville Syrjala
2017-10-20 20:47 ` Rodrigo Vivi
2017-10-18 20:48 ` [PATCH 5/8] drm/i915: Use cdclk_state->voltage on SKL/KBL/CFL Ville Syrjala
2017-10-19 23:47 ` Rodrigo Vivi
2017-10-20 11:18 ` Ville Syrjälä
2017-10-20 20:45 ` Rodrigo Vivi
2017-10-18 20:48 ` [PATCH 6/8] drm/i915: Use cdclk_state->voltage on BXT/GLK Ville Syrjala
2017-10-20 20:51 ` Rodrigo Vivi
2017-10-18 20:48 ` [PATCH 7/8] drm/i915: Use cdclk_state->voltage on CNL Ville Syrjala
2017-10-18 21:50 ` Rodrigo Vivi
2017-10-18 22:43 ` Rodrigo Vivi
2017-10-19 10:48 ` Ville Syrjälä
2017-10-19 10:56 ` Mika Kahola
2017-10-19 12:19 ` Ville Syrjälä
2017-10-19 23:52 ` Rodrigo Vivi
2017-10-23 18:29 ` Rodrigo Vivi
2017-10-18 20:48 ` [PATCH 8/8] drm/i915: Adjust system agent voltage on CNL if required by DDI ports Ville Syrjala
2017-10-19 23:54 ` Rodrigo Vivi
2017-10-20 11:11 ` Ville Syrjälä
2017-10-20 17:48 ` Runyan, Arthur J
2017-10-20 20:07 ` Ville Syrjälä
2017-10-20 20:36 ` Rodrigo Vivi
2017-10-20 21:44 ` Runyan, Arthur J
2017-10-23 12:03 ` Ville Syrjälä
2017-10-23 11:48 ` Ville Syrjälä
2017-10-20 14:18 ` Ville Syrjälä
2017-10-20 16:11 ` Ville Syrjälä
2017-10-20 16:09 ` [PATCH v2 " Ville Syrjala
2017-10-20 16:52 ` Ville Syrjälä
2017-10-20 17:05 ` [PATCH v3 " Ville Syrjala
2017-10-23 18:39 ` Rodrigo Vivi
2017-10-18 21:07 ` ✗ Fi.CI.BAT: warning for drm/i915: CNL DVFS thing Patchwork
2017-10-19 17:31 ` Ville Syrjälä
2017-10-19 18:17 ` ✗ Fi.CI.BAT: failure for drm/i915: CNL DVFS thing (rev2) Patchwork
2017-10-19 18:52 ` Patchwork
2017-10-19 20:07 ` ✗ Fi.CI.BAT: warning " Patchwork
2017-10-19 23:27 ` ✓ Fi.CI.BAT: success " Patchwork
2017-10-20 0:22 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-20 16:28 ` ✓ Fi.CI.BAT: success for drm/i915: CNL DVFS thing (rev3) Patchwork
2017-10-20 17:48 ` ✓ Fi.CI.BAT: success for drm/i915: CNL DVFS thing (rev6) Patchwork
2017-10-20 19:19 ` ✓ Fi.CI.IGT: " 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=20171020161445.GN10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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