Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915/dp: Don't WARN on failed link-retrain modeset
Date: Fri, 12 Jul 2024 12:38:01 -0400	[thread overview]
Message-ID: <ZpFb6QpTV3LLFpIw@intel.com> (raw)
In-Reply-To: <20240712135724.660399-3-imre.deak@intel.com>

On Fri, Jul 12, 2024 at 04:57:24PM +0300, Imre Deak wrote:
> After a bad link state is detected, the sink capabilities with which the
> link was originally trained could have changed: for instance another
> sink got connected or the retraining was forced after the rate/lane count
> got decreased (as a fallback). In these cases the retraining modeset
> fails as expected also printing a debug message, so don't WARN on it.

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> 
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 0365fb1e77eae..1e43e32e05199 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -5282,14 +5282,11 @@ static int intel_dp_retrain_link(struct intel_encoder *encoder,
>  
>  void intel_dp_link_check(struct intel_encoder *encoder)
>  {
> -	struct drm_i915_private *i915 = to_i915(encoder->base.dev);
>  	struct drm_modeset_acquire_ctx ctx;
>  	int ret;
>  
>  	intel_modeset_lock_ctx_retry(&ctx, NULL, 0, ret)
>  		ret = intel_dp_retrain_link(encoder, &ctx);
> -
> -	drm_WARN_ON(&i915->drm, ret);
>  }
>  
>  void intel_dp_check_link_state(struct intel_dp *intel_dp)
> -- 
> 2.44.2
> 

  reply	other threads:[~2024-07-12 16:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 13:57 [PATCH 1/3] drm/i915/dp: Retrain SST links via a modeset commit Imre Deak
2024-07-12 13:57 ` [PATCH 2/3] drm/i915/dp: Require a valid atomic state for SST link training Imre Deak
2024-07-18  5:18   ` Kandpal, Suraj
2024-07-12 13:57 ` [PATCH 3/3] drm/i915/dp: Don't WARN on failed link-retrain modeset Imre Deak
2024-07-12 16:38   ` Rodrigo Vivi [this message]
2024-07-12 14:30 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/i915/dp: Retrain SST links via a modeset commit Patchwork
2024-07-12 14:46 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-07-12 15:30   ` Imre Deak
2024-07-15 13:10     ` Illipilli, TejasreeX
2024-07-15 13:06 ` ✓ Fi.CI.BAT: success " Patchwork
2024-07-16 10:21 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-07-22  8:21   ` Imre Deak
2024-07-18  5:17 ` [PATCH 1/3] " Kandpal, Suraj

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=ZpFb6QpTV3LLFpIw@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@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