From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Bump GLK CDCLK frequency when driving multiple pipes
Date: Thu, 02 Nov 2023 16:07:58 +0200 [thread overview]
Message-ID: <8734xo2qpt.fsf@intel.com> (raw)
In-Reply-To: <20231031160800.18371-1-ville.syrjala@linux.intel.com>
On Tue, 31 Oct 2023, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> On GLK CDCLK frequency needs to be at least 2*96 MHz when accessing
> the audio hardware. Currently we bump the CDCLK frequency up
> temporarily (if not high enough already) whenever audio hardware
> is being accessed, and drop it back down afterwards.
>
> With a single active pipe this works just fine as we can switch
> between all the valid CDCLK frequencies by changing the cd2x
> divider, which doesn't require a full modeset. However with
> multiple active pipes the cd2x divider trick no longer works,
> and thus we end up blinking all displays off and back on.
>
> To avoid this let's just bump the CDCLK frequency to >=2*96MHz
> whenever multiple pipes are active. The downside is slightly
> higher power consumption, but that seems like an acceptable
> tradeoff. With a single active pipe we can stick to the current
> more optiomal (from power comsumption POV) behaviour.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/9599
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_cdclk.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c b/drivers/gpu/drm/i915/display/intel_cdclk.c
> index 6d7ba4d0f130..3ddf4201e224 100644
> --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> @@ -2750,6 +2750,18 @@ static int intel_compute_min_cdclk(struct intel_cdclk_state *cdclk_state)
> for_each_pipe(dev_priv, pipe)
> min_cdclk = max(cdclk_state->min_cdclk[pipe], min_cdclk);
>
> + /*
> + * Avoid glk_force_audio_cdclk() causing excessive screen
> + * blinking when multiple pipes are active by making sure
> + * cdclk frequency is always high enough for audio. With a
> + * single active pipe we can always change CDCLK frequency
> + * by changing the cd2x divider (see glk_cdclk_table[]) and
> + * thus a full modeset won't be needed then.
> + */
> + if (DISPLAY_VER(dev_priv) == 10 && cdclk_state->active_pipes &&
> + !is_power_of_2(cdclk_state->active_pipes))
> + min_cdclk = max(2 * 96000, min_cdclk);
For consistency with glk_force_audio_cdclk(), maybe
s/DISPLAY_VER(dev_priv) == 10/IS_GEMINILAKE()/?
There's a bit of duplication with the frequencies, but I guess the
comment is enough to alleviate the concern.
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> +
> if (min_cdclk > dev_priv->display.cdclk.max_cdclk_freq) {
> drm_dbg_kms(&dev_priv->drm,
> "required cdclk (%d kHz) exceeds max (%d kHz)\n",
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-11-02 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:08 [Intel-gfx] [PATCH] drm/i915: Bump GLK CDCLK frequency when driving multiple pipes Ville Syrjala
2023-10-31 23:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-11-02 11:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-02 14:07 ` Jani Nikula [this message]
2023-11-02 16:17 ` [Intel-gfx] [PATCH] " Ville Syrjälä
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=8734xo2qpt.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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