From: Jani Nikula <jani.nikula@linux.intel.com>
To: Shekhar Chauhan <shekhar.chauhan@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: matthew.d.roper@intel.com, clinton.a.taylor@intel.com,
shekhar.chauhan@intel.com
Subject: Re: [PATCH] drm/i915/lnl: Modeset sequence change for DP on LNL
Date: Thu, 29 Feb 2024 16:49:18 +0200 [thread overview]
Message-ID: <87zfvj72c1.fsf@intel.com> (raw)
In-Reply-To: <20240229025752.651864-1-shekhar.chauhan@intel.com>
On Thu, 29 Feb 2024, Shekhar Chauhan <shekhar.chauhan@intel.com> wrote:
> Currently, the driver is only waiting for 1ms for
> idle patterns. But starting from LNL and beyond,
> the MST wants the driver to wait for 1640us before
> timing out (which we round up to 2ms).
>
> BSpec: 68849
> Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
Replied in the other thread:
https://lore.kernel.org/r/878r338nhs.fsf@intel.com
> ---
> drivers/gpu/drm/i915/display/intel_ddi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
> index bea441590204..05ba3642d486 100644
> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> @@ -3680,7 +3680,7 @@ static void intel_ddi_set_idle_link_train(struct intel_dp *intel_dp,
>
> if (intel_de_wait_for_set(dev_priv,
> dp_tp_status_reg(encoder, crtc_state),
> - DP_TP_STATUS_IDLE_DONE, 1))
> + DP_TP_STATUS_IDLE_DONE, 2))
> drm_err(&dev_priv->drm,
> "Timed out waiting for DP idle patterns\n");
> }
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-29 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 2:57 [PATCH] drm/i915/lnl: Modeset sequence change for DP on LNL Shekhar Chauhan
2024-02-29 4:49 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-02-29 14:49 ` Jani Nikula [this message]
2024-03-01 2:15 ` ✓ Fi.CI.IGT: " 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=87zfvj72c1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=shekhar.chauhan@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