From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Lisovskiy\, Stanislav" <stanislav.lisovskiy@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] Revert "drm/i915: Remove unneeded hack now for CDCLK"
Date: Mon, 08 Jun 2020 12:37:05 +0300 [thread overview]
Message-ID: <878sgxyk3i.fsf@intel.com> (raw)
In-Reply-To: <20200608083540.GA22223@intel.com>
On Mon, 08 Jun 2020, "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com> wrote:
> On Mon, Jun 08, 2020 at 11:21:14AM +0300, Jani Nikula wrote:
>> On Mon, 08 Jun 2020, Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> wrote:
>> > This reverts commit 82ea174dc5425d4e85e25d0c4ba961a2e494392a.
>> >
>>
>> Please explain why. What's going on, why we need the revert.
>>
>> It's fine to reply here, the commit message can be amended by whoever
>> applies the patch.
>
> Yes,
>
> Unfortunately according to our recent findings there is still some
> unidentified factor, requiring CDCLK to be set higher - otherwise we
> still get underruns on some multipipe configurations, despite CDCLK being set
> according to BSpec formula. So getting again back into debug mode to
> indentify the cause, meanwhile setting CDCLK=Pixel rate back in order
> to remove regression in 10% of the cases due to FIFO underruns.
Thanks, pushed.
BR,
Jani.
>
> Stan
>
>>
>> BR,
>> Jani.
>>
>>
>> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>> > Fixes: cd1915460861 ("drm/i915: Adjust CDCLK accordingly to our DBuf bw needs")
>> > ---
>> > 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 08468b121d02..45f7f33d1144 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
>> > +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
>> > @@ -2071,6 +2071,18 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)
>> > /* Account for additional needs from the planes */
>> > min_cdclk = max(intel_planes_min_cdclk(crtc_state), min_cdclk);
>> >
>> > + /*
>> > + * HACK. Currently for TGL platforms we calculate
>> > + * min_cdclk initially based on pixel_rate divided
>> > + * by 2, accounting for also plane requirements,
>> > + * however in some cases the lowest possible CDCLK
>> > + * doesn't work and causing the underruns.
>> > + * Explicitly stating here that this seems to be currently
>> > + * rather a Hack, than final solution.
>> > + */
>> > + if (IS_TIGERLAKE(dev_priv))
>> > + min_cdclk = max(min_cdclk, (int)crtc_state->pixel_rate);
>> > +
>> > if (min_cdclk > dev_priv->max_cdclk_freq) {
>> > drm_dbg_kms(&dev_priv->drm,
>> > "required cdclk (%d kHz) exceeds max (%d kHz)\n",
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-06-08 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 6:55 [Intel-gfx] [PATCH] Revert "drm/i915: Remove unneeded hack now for CDCLK" Stanislav Lisovskiy
2020-06-08 7:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-08 8:21 ` [Intel-gfx] [PATCH] " Jani Nikula
2020-06-08 8:35 ` Lisovskiy, Stanislav
2020-06-08 9:37 ` Jani Nikula [this message]
2020-06-08 8:30 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=878sgxyk3i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stanislav.lisovskiy@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