Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: <imre.deak@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>, <suraj.kandpal@intel.com>
Subject: Re: [PATCH] drm/i915/display/dp: On dpcd init/caps wake the dprx
Date: Thu, 19 Feb 2026 14:39:25 +0530	[thread overview]
Message-ID: <23735591-84d4-44ef-8d42-5c664c6b82bb@intel.com> (raw)
In-Reply-To: <aZbPT-bcZlvl2Jc-@ideak-desk.lan>

On 19-02-2026 14:22, Imre Deak wrote:
> On Thu, Feb 19, 2026 at 02:02:19PM +0530, Arun R Murthy wrote:
>> Before reading the dpcd caps for eDP wake the sink device and for DP
>> after reading the lttpr caps and before reading the dpcd caps wake up
>> the sink device.
>>
>> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_dp.c       | 28 +++++++++++++++++++
>>   drivers/gpu/drm/i915/display/intel_dp.h       |  1 +
>>   .../drm/i915/display/intel_dp_link_training.c |  3 ++
>>   3 files changed, 32 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index 454e6144ee4e..4d86826dba1b 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -4705,6 +4705,32 @@ intel_edp_set_sink_rates(struct intel_dp *intel_dp)
>>   	intel_edp_set_data_override_rates(intel_dp);
>>   }
>>   
>> +void intel_dp_wake_sink(struct intel_dp *intel_dp)
>> +{
>> +	u8 value = 0;
>> +	int ret = 0, try = 0;
>> +
>> +	intel_dp_dpcd_set_probe(intel_dp, false);
>> +
>> +	/*
>> +	 * Wake the sink device
>> +	 * Spec section 2.3.1.2 if AUX CH is powered down by writing 0x02 to
>> +	 * DP_SET_POWER dpcd reg, 1ms time would be required to wake it up
>> +	 */
>> +	while (try < 10 && ret < 0) {
>> +		ret = drm_dp_dpcd_readb(&intel_dp->aux, DP_SET_POWER, &value);
>> +		if (value)
>> +			break;
>> +		fsleep(1000);
>> +		try++;
>> +	}
>> +	/* After setting to D0 need a min of 1ms to wake(Spec sec 2.3.1.2) */
>> +	drm_dp_dpcd_writeb(&intel_dp->aux, DP_SET_POWER, DP_SET_POWER_D0);
>> +	fsleep(1000);
>> +
>> +	intel_dp_dpcd_set_probe(intel_dp, true);
>> +}
>> +
>>   static bool
>>   intel_edp_init_dpcd(struct intel_dp *intel_dp, struct intel_connector *connector)
>>   {
>> @@ -4713,6 +4739,8 @@ intel_edp_init_dpcd(struct intel_dp *intel_dp, struct intel_connector *connector
>>   	/* this function is meant to be called only once */
>>   	drm_WARN_ON(display->drm, intel_dp->dpcd[DP_DPCD_REV] != 0);
>>   
>> +	intel_dp_wake_sink(intel_dp);
>> +
>>   	if (drm_dp_read_dpcd_caps(&intel_dp->aux, intel_dp->dpcd) != 0)
>>   		return false;
>>   
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.h b/drivers/gpu/drm/i915/display/intel_dp.h
>> index b0bbd5981f57..3f16077c0cc7 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.h
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.h
>> @@ -232,6 +232,7 @@ bool intel_dp_dotclk_valid(struct intel_display *display,
>>   bool intel_dp_joiner_candidate_valid(struct intel_connector *connector,
>>   				     int hdisplay,
>>   				     int num_joined_pipes);
>> +void intel_dp_wake_sink(struct intel_dp *intel_dp);
>>   
>>   #define for_each_joiner_candidate(__connector, __mode, __num_joined_pipes) \
>>   	for ((__num_joined_pipes) = 1; (__num_joined_pipes) <= (I915_MAX_PIPES); (__num_joined_pipes)++) \
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp_link_training.c b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> index 54c585c59b90..cbb712ea9f60 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> @@ -270,6 +270,9 @@ int intel_dp_init_lttpr_and_dprx_caps(struct intel_dp *intel_dp)
>>   		lttpr_count = intel_dp_init_lttpr(intel_dp, dpcd);
>>   	}
>>   
>> +	/* After reading LTTPR wake up the sink before reading DPRX caps */
>> +	intel_dp_wake_sink(intel_dp);
> Not sure if this is correct or needed. The D0 state you're waking up the
> device into is a requirement for the main lanes, not for the AUX / DPCD
> register accesses as this change implies.
Without this change when there is a AUX transaction failure, 
irrespective of increasing the retry to even 1000 times failure still 
exists.
Which means that sink is an unknown/sleep state and due to which there 
is no ACK.
> Setting D0 here will also
> leave the sink in D0 even if the output - i.e. what would require the
> the main lane to be functional - is left disabled, thus wasting power.

After setting to D0 we can again set to D3/D3_AUX_ON which helps in 
keeping AUX active.

Thanks and Regards,
Arun R Murthy
--------------------

>> +
>>   	/*
>>   	 * The DPTX shall read the DPRX caps after LTTPR detection, so re-read
>>   	 * it here.
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2026-02-19  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  8:32 [PATCH] drm/i915/display/dp: On dpcd init/caps wake the dprx Arun R Murthy
2026-02-19  8:52 ` Imre Deak
2026-02-19  9:09   ` Murthy, Arun R [this message]
2026-02-19  8:57 ` Kandpal, Suraj
2026-02-19  8:59 ` ✓ CI.KUnit: success for " Patchwork
2026-02-19  9:35 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-19 11:13 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-23 16:47 ` [PATCH] " Jani Nikula
2026-02-24  2:27   ` Murthy, Arun R

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=23735591-84d4-44ef-8d42-5c664c6b82bb@intel.com \
    --to=arun.r.murthy@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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