All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dp: Tune down FEC detection timeout error message
Date: Mon, 13 Nov 2023 18:48:18 +0200	[thread overview]
Message-ID: <87fs19tx9p.fsf@intel.com> (raw)
In-Reply-To: <20231113142051.258864-1-imre.deak@intel.com>

On Mon, 13 Nov 2023, Imre Deak <imre.deak@intel.com> wrote:
> At least a Realtek DP branch device with the
>
> OUI 00-e0-4c dev-ID Dp1.4 HW-rev 1.0 SW-rev 131.1
>
> device identification doesn't report detecting the FEC decoding start
> symbol. Tune down the corresponding error to a debug message.
>
> Signed-off-by: Imre Deak <imre.deak@intel.com>

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  drivers/gpu/drm/i915/display/intel_ddi.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
> index 0712a5200ad35..f70af660dfcfa 100644
> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> @@ -2257,8 +2257,8 @@ static void wait_for_fec_detected(struct drm_dp_aux *aux, bool enabled)
>  		return;
>  
>  	if (err == -ETIMEDOUT)
> -		drm_err(&i915->drm, "Timeout waiting for FEC %s to get detected\n",
> -			str_enabled_disabled(enabled));
> +		drm_dbg_kms(&i915->drm, "Timeout waiting for FEC %s to get detected\n",
> +			    str_enabled_disabled(enabled));
>  	else
>  		drm_dbg_kms(&i915->drm, "FEC detected status read error: %d\n", status);
>  }

-- 
Jani Nikula, Intel

  reply	other threads:[~2023-11-13 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 14:20 [Intel-gfx] [PATCH] drm/i915/dp: Tune down FEC detection timeout error message Imre Deak
2023-11-13 16:48 ` Jani Nikula [this message]
2023-11-13 21:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-11-14  4:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-11-14 15:57   ` Imre Deak

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=87fs19tx9p.fsf@intel.com \
    --to=jani.nikula@linux.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 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.