From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/5] drm/i915/skl: use previous pll hw readout
Date: Mon, 25 Mar 2019 09:32:36 +0200 [thread overview]
Message-ID: <20190325073236.GR3888@intel.com> (raw)
In-Reply-To: <20190322223751.22089-2-lucas.demarchi@intel.com>
On Fri, Mar 22, 2019 at 03:37:47PM -0700, Lucas De Marchi wrote:
> By the time skl_ddi_clock_get() is called - and thus
> skl_calc_wrpll_link() - we've just got the hw state from the pll
> registers. We don't need to read them again: we can rather reuse what
> was cached in the dpll_hw_state.
>
> v2: rename state variable to pll_state, make argument const in
> skl_calc_wrpll_link() and remove not useful warning (from Ville)
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_ddi.c | 50 ++++++++++++++------------------
> 1 file changed, 21 insertions(+), 29 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> index 933df3a57a8a..15f143c2ed6e 100644
> --- a/drivers/gpu/drm/i915/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/intel_ddi.c
> @@ -1240,24 +1240,15 @@ static int hsw_ddi_calc_wrpll_link(struct drm_i915_private *dev_priv,
> return (refclk * n * 100) / (p * r);
> }
>
> -static int skl_calc_wrpll_link(struct drm_i915_private *dev_priv,
> - enum intel_dpll_id pll_id)
> +static int skl_calc_wrpll_link(const struct intel_dpll_hw_state *pll_state)
> {
> - i915_reg_t cfgcr1_reg, cfgcr2_reg;
> - u32 cfgcr1_val, cfgcr2_val;
> u32 p0, p1, p2, dco_freq;
>
> - cfgcr1_reg = DPLL_CFGCR1(pll_id);
> - cfgcr2_reg = DPLL_CFGCR2(pll_id);
> + p0 = pll_state->cfgcr2 & DPLL_CFGCR2_PDIV_MASK;
> + p2 = pll_state->cfgcr2 & DPLL_CFGCR2_KDIV_MASK;
>
> - cfgcr1_val = I915_READ(cfgcr1_reg);
> - cfgcr2_val = I915_READ(cfgcr2_reg);
> -
> - p0 = cfgcr2_val & DPLL_CFGCR2_PDIV_MASK;
> - p2 = cfgcr2_val & DPLL_CFGCR2_KDIV_MASK;
> -
> - if (cfgcr2_val & DPLL_CFGCR2_QDIV_MODE(1))
> - p1 = (cfgcr2_val & DPLL_CFGCR2_QDIV_RATIO_MASK) >> 8;
> + if (pll_state->cfgcr2 & DPLL_CFGCR2_QDIV_MODE(1))
> + p1 = (pll_state->cfgcr2 & DPLL_CFGCR2_QDIV_RATIO_MASK) >> 8;
> else
> p1 = 1;
>
> @@ -1292,10 +1283,11 @@ static int skl_calc_wrpll_link(struct drm_i915_private *dev_priv,
> break;
> }
>
> - dco_freq = (cfgcr1_val & DPLL_CFGCR1_DCO_INTEGER_MASK) * 24 * 1000;
> + dco_freq = (pll_state->cfgcr1 & DPLL_CFGCR1_DCO_INTEGER_MASK)
> + * 24 * 1000;
>
> - dco_freq += (((cfgcr1_val & DPLL_CFGCR1_DCO_FRACTION_MASK) >> 9) * 24 *
> - 1000) / 0x8000;
> + dco_freq += (((pll_state->cfgcr1 & DPLL_CFGCR1_DCO_FRACTION_MASK) >> 9)
> + * 24 * 1000) / 0x8000;
>
> if (WARN_ON(p0 == 0 || p1 == 0 || p2 == 0))
> return 0;
> @@ -1544,22 +1536,22 @@ static void cnl_ddi_clock_get(struct intel_encoder *encoder,
> }
>
> static void skl_ddi_clock_get(struct intel_encoder *encoder,
> - struct intel_crtc_state *pipe_config)
> + struct intel_crtc_state *pipe_config)
> {
> - struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
> - int link_clock = 0;
> - u32 dpll_ctl1;
> - enum intel_dpll_id pll_id;
> -
> - pll_id = intel_get_shared_dpll_id(dev_priv, pipe_config->shared_dpll);
> + struct intel_dpll_hw_state *pll_state;
> + int link_clock;
>
> - dpll_ctl1 = I915_READ(DPLL_CTRL1);
> + /*
> + * ctrl1 register is already shifted for each pll, just use 0 to get
> + * the internal shift for each field
> + */
> + pll_state = &pipe_config->dpll_hw_state;
This initialization seems a bit misplaced.
Series is
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> - if (dpll_ctl1 & DPLL_CTRL1_HDMI_MODE(pll_id)) {
> - link_clock = skl_calc_wrpll_link(dev_priv, pll_id);
> + if (pll_state->ctrl1 & DPLL_CTRL1_HDMI_MODE(0)) {
> + link_clock = skl_calc_wrpll_link(pll_state);
> } else {
> - link_clock = dpll_ctl1 & DPLL_CTRL1_LINK_RATE_MASK(pll_id);
> - link_clock >>= DPLL_CTRL1_LINK_RATE_SHIFT(pll_id);
> + link_clock = pll_state->ctrl1 & DPLL_CTRL1_LINK_RATE_MASK(0);
> + link_clock >>= DPLL_CTRL1_LINK_RATE_SHIFT(0);
>
> switch (link_clock) {
> case DPLL_CTRL1_LINK_RATE_810:
> --
> 2.20.1
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-25 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 22:37 [PATCH v2 0/5] Do not re-read dpll registers Lucas De Marchi
2019-03-22 22:37 ` [PATCH v2 1/5] drm/i915/skl: use previous pll hw readout Lucas De Marchi
2019-03-25 7:32 ` Ville Syrjälä [this message]
2019-03-25 23:15 ` [PATCH v3] " Lucas De Marchi
2019-03-22 22:37 ` [PATCH v2 2/5] drm/i915/bxt: make bxt_calc_pll_link() similar to skl Lucas De Marchi
2019-03-22 22:37 ` [PATCH v2 3/5] drm/i915/cnl: use previous pll hw readout Lucas De Marchi
2019-03-22 22:37 ` [PATCH v2 4/5] drm/i915/icl: " Lucas De Marchi
2019-03-22 22:37 ` [PATCH v2 5/5] drm/i915/icl: reduce pll_id scope and use enum type Lucas De Marchi
2019-03-22 23:20 ` ✓ Fi.CI.BAT: success for Do not re-read dpll registers (rev2) Patchwork
2019-03-24 4:51 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-26 13:44 ` ✓ Fi.CI.BAT: success for Do not re-read dpll registers (rev3) Patchwork
2019-03-26 18:45 ` ✗ Fi.CI.IGT: failure " 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=20190325073236.GR3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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