Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<intel-gfx@lists.freedesktop.org>,
	<dibin.moolakadan.subrahmanian@intel.com>,
	<ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH] drm/xe/display: read PCON capability only when present
Date: Wed, 18 Jun 2025 21:43:00 +0300	[thread overview]
Message-ID: <aFMItK__ToPsUTz2@ideak-desk> (raw)
In-Reply-To: <20250618114553.3974479-1-chaitanya.kumar.borah@intel.com>

On Wed, Jun 18, 2025 at 05:15:53PM +0530, Chaitanya Kumar Borah wrote:
> Read PCON capabilities only when it is present. This will prevent
> spurious DCPD read failures.
> 
> [drm] *ERROR* Failed to read DPCD register 0x92

The above read failure is due to the sink not being connected during the
read access (in some Chamelium HPD test), not because PCON not being
present in the sink. If sink is connected and its HPD is asserted the
read would not fail, just return all 0s. So the commit message should
just say stg like "avoid reading the PCON capabilities redundantly on
non-branch devices".

> 
> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 277b40b13948..8a1c2a37a56b 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -5681,7 +5681,8 @@ intel_dp_update_dfp(struct intel_dp *intel_dp,
>  		    intel_dp->dfp.max_tmds_clock,
>  		    intel_dp->dfp.pcon_max_frl_bw);
>  
> -	intel_dp_get_pcon_dsc_cap(intel_dp);
> +	if (drm_dp_is_branch(intel_dp->dpcd))
> +		intel_dp_get_pcon_dsc_cap(intel_dp);

Clearing intel_dp->pcon_dsc_dpcd should still happen, you could move the
above check after that happens in intel_dp_get_pcon_dsc_cap().

>  }
>  
>  static bool
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2025-06-18 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 11:45 [PATCH] drm/xe/display: read PCON capability only when present Chaitanya Kumar Borah
2025-06-18 12:52 ` ✓ i915.CI.BAT: success for " Patchwork
2025-06-18 18:43 ` Imre Deak [this message]
2025-06-19  3:08 ` ✗ i915.CI.Full: failure " 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=aFMItK__ToPsUTz2@ideak-desk \
    --to=imre.deak@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=dibin.moolakadan.subrahmanian@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