From: Jani Nikula <jani.nikula@linux.intel.com>
To: Niko Tsirakis <ntsirakis@google.com>, dri-devel@lists.freedesktop.org
Cc: Niko Tsirakis <ntsirakis@google.com>,
Pablo Ceballos <pceballos@google.com>
Subject: Re: [PATCH v4] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
Date: Wed, 04 Oct 2023 18:35:36 +0300 [thread overview]
Message-ID: <87fs2qe6yf.fsf@intel.com> (raw)
In-Reply-To: <20231002204709.761089-1-ntsirakis@google.com>
On Mon, 02 Oct 2023, Niko Tsirakis <ntsirakis@google.com> wrote:
> This is to eliminate all cases of "*ERROR* LSPCON mode hasn't settled",
> followed by link training errors. Intel engineers recommended increasing
> this timeout and that does resolve the issue.
>
> On some CometLake-based device designs the Parade PS175 takes more than
> 400ms to settle in PCON mode. 100 reboot trials on one device resulted
> in a median settle time of 440ms and a maximum of 444ms. Even after
> increasing the timeout to 500ms, 2% of devices still had this error. So
> this increases the timeout to 800ms.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/9443
> Signed-off-by: Pablo Ceballos <pceballos@google.com>
> Signed-off-by: Niko Tsirakis <ntsirakis@google.com>
Thanks for the patch, pushed to drm-intel-next.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/display/intel_lspcon.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
> index dc1b35559afd..92536482e657 100644
> --- a/drivers/gpu/drm/i915/display/intel_lspcon.c
> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
> @@ -116,6 +116,18 @@ static enum drm_lspcon_mode lspcon_get_current_mode(struct intel_lspcon *lspcon)
> return current_mode;
> }
>
> +static int lspcon_get_mode_settle_timeout(struct intel_lspcon *lspcon)
> +{
> + /*
> + * On some CometLake-based device designs the Parade PS175 takes more
> + * than 400ms to settle in PCON mode. 100 reboot trials on one device
> + * resulted in a median settle time of 440ms and a maximum of 444ms.
> + * Even after increasing the timeout to 500ms, 2% of devices still had
> + * this error. So this sets the timeout to 800ms.
> + */
> + return lspcon->vendor == LSPCON_VENDOR_PARADE ? 800 : 400;
> +}
> +
> static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
> enum drm_lspcon_mode mode)
> {
> @@ -128,7 +140,8 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
> DRM_DEBUG_KMS("Waiting for LSPCON mode %s to settle\n",
> lspcon_mode_name(mode));
>
> - wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
> + wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode,
> + lspcon_get_mode_settle_timeout(lspcon));
> if (current_mode != mode)
> DRM_ERROR("LSPCON mode hasn't settled\n");
--
Jani Nikula, Intel
prev parent reply other threads:[~2023-10-04 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 4:56 [Intel-gfx] [PATCH v3] drm/i915/display/lspcon: Increase LSPCON mode settle timeout Pablo Ceballos
2023-08-16 4:56 ` Pablo Ceballos
2023-08-16 4:56 ` Pablo Ceballos
2023-08-16 6:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev4) Patchwork
2023-08-16 6:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-16 7:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-16 9:02 ` [Intel-gfx] [PATCH v3] drm/i915/display/lspcon: Increase LSPCON mode settle timeout Jani Nikula
2023-08-16 9:02 ` Jani Nikula
2023-08-16 9:02 ` Jani Nikula
2023-08-16 10:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev4) Patchwork
2023-10-02 10:00 ` [Intel-gfx] [PATCH v3] drm/i915/display/lspcon: Increase LSPCON mode settle timeout Jani Nikula
2023-10-02 10:00 ` Jani Nikula
2023-10-02 10:00 ` Jani Nikula
2023-10-02 20:47 ` [PATCH v4] " Niko Tsirakis
2023-10-04 15:35 ` Jani Nikula [this message]
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=87fs2qe6yf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ntsirakis@google.com \
--cc=pceballos@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.