From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v1] drm/i915: Clamp min_cdclk to max_cdclk_freq to unblock 8K
Date: Wed, 1 Jul 2020 08:57:09 +0300 [thread overview]
Message-ID: <20200701055708.GA8477@intel.com> (raw)
In-Reply-To: <20200630162909.GR6112@intel.com>
On Tue, Jun 30, 2020 at 07:29:09PM +0300, Ville Syrjälä wrote:
> On Tue, Jun 30, 2020 at 02:26:09PM +0300, Stanislav Lisovskiy wrote:
> > We still need "Bump up CDCLK" workaround otherwise getting
> > underruns - however currently it blocks 8K as CDCLK = Pixel rate,
> > in 8K case would require CDCLK to be around 1 Ghz which is not
> > possible.
> >
> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_cdclk.c | 14 +++++++++++++-
> > 1 file changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c b/drivers/gpu/drm/i915/display/intel_cdclk.c
> > index 45f7f33d1144..01a5bc6b08c4 100644
> > --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> > +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> > @@ -2080,9 +2080,21 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)
> > * Explicitly stating here that this seems to be currently
> > * rather a Hack, than final solution.
> > */
> > - if (IS_TIGERLAKE(dev_priv))
> > + if (IS_TIGERLAKE(dev_priv)) {
> > min_cdclk = max(min_cdclk, (int)crtc_state->pixel_rate);
> >
> > + /*
> > + * Clamp to max_cdclk_freq in order not to break an 8K,
> > + * but still leave W/A at place.
> > + */
> > + min_cdclk = min(min_cdclk, (int)dev_priv->max_cdclk_freq);
> > +
> > + /*
> > + * max_cdclk_freq check obviously not needed - just return.
> > + */
> > + return min_cdclk;
>
> Pointless return. But I think we should actually keep the max_cdclk
> check. Something like:
>
> min_cdclk = max(min_cdclk,
> min(max_cdclk, pixel_rate));
>
> Also what's with the (int) casts? There is min_t() if you
> actually need casts. But not sure why we need them though.
Don't like the casts either. Aware of min_t. Just remember that smth
prevented me from using it in initial patch. Will check once again
to figure out why I did so last time.
Regarding the check we actually you are proposing to do the same thing
as initially I check min_cdclk = max(min_cdclk, pixel_rate) and then
it gets to min_cdclk = min(min_cdclk, max_cdclk_freq).
Just do it kind of in 2 steps in order not to change the
original Bump CDCLK patch.
I.e min_cdclk still has to be more or equal than pixel rate, but always less
than max_cdclk_freq.
Stan
>
> > + }
> > +
> > if (min_cdclk > dev_priv->max_cdclk_freq) {
> > drm_dbg_kms(&dev_priv->drm,
> > "required cdclk (%d kHz) exceeds max (%d kHz)\n",
> > --
> > 2.24.1.485.gad05a3d8e5
>
> --
> 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:[~2020-07-01 5:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 11:26 [Intel-gfx] [PATCH v1] drm/i915: Clamp min_cdclk to max_cdclk_freq to unblock 8K Stanislav Lisovskiy
2020-06-30 15:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-06-30 16:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-06-30 16:29 ` [Intel-gfx] [PATCH v1] " Ville Syrjälä
2020-06-30 20:27 ` Manasi Navare
2020-07-01 5:57 ` Lisovskiy, Stanislav [this message]
2020-06-30 21:17 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2020-07-01 12:20 ` [Intel-gfx] [PATCH v1] " Maarten Lankhorst
2020-07-01 18:44 ` Manasi Navare
2020-07-01 19:13 ` Lisovskiy, Stanislav
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=20200701055708.GA8477@intel.com \
--to=stanislav.lisovskiy@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