From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
"Runyan, Arthur J" <arthur.j.runyan@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/dp: Wait more before rearming FIFO underrun during retrain
Date: Wed, 26 Jun 2024 11:13:09 -0400 [thread overview]
Message-ID: <ZnwwBZFFugbV7JPj@intel.com> (raw)
In-Reply-To: <20240626083624.4042544-1-ankit.k.nautiyal@intel.com>
On Wed, Jun 26, 2024 at 02:06:24PM +0530, Ankit Nautiyal wrote:
> During Link re-training reporting underrun is disabled and then
> renabled after re-training is completed. For BMG its seen that we get
> FIFO underrun just after the retraining is completed and the underrun
> reporting is re-enabled.
> Add one more intel_crtc_wait_for_next_vblank before re-arming the
> underruns.
Cc: Arthur Runyan <arthur.j.runyan@intel.com>
Art, any new workaround in BMG for this issue?
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 3903f6ead6e6..25af51499383 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -5325,7 +5325,12 @@ static int intel_dp_retrain_link(struct intel_encoder *encoder,
> const struct intel_crtc_state *crtc_state =
> to_intel_crtc_state(crtc->base.state);
>
> - /* Keep underrun reporting disabled until things are stable */
> + /*
> + * Keep underrun reporting disabled until things are stable.
> + * Wait for some more time, as we see (at least on BMG) that
> + * underrun gets reported just after the reporting is enabled.
> + */
> + intel_crtc_wait_for_next_vblank(crtc);
> intel_crtc_wait_for_next_vblank(crtc);
>
> intel_set_cpu_fifo_underrun_reporting(dev_priv, crtc->pipe, true);
> --
> 2.40.1
>
next prev parent reply other threads:[~2024-06-26 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 8:36 [PATCH] drm/i915/dp: Wait more before rearming FIFO underrun during retrain Ankit Nautiyal
2024-06-26 8:40 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-26 8:40 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-26 8:41 ` ✓ CI.KUnit: success " Patchwork
2024-06-26 8:53 ` ✓ CI.Build: " Patchwork
2024-06-26 8:56 ` ✓ CI.Hooks: " Patchwork
2024-06-26 8:58 ` ✗ CI.checksparse: warning " Patchwork
2024-06-26 9:21 ` ✓ CI.BAT: success " Patchwork
2024-06-26 10:35 ` ✗ CI.FULL: failure " Patchwork
2024-06-26 15:13 ` Rodrigo Vivi [this message]
2024-06-26 15:18 ` [PATCH] " Runyan, Arthur J
2024-06-26 15:43 ` Imre Deak
2024-07-03 6:27 ` Nautiyal, Ankit K
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=ZnwwBZFFugbV7JPj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arthur.j.runyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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