From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"Manna, Animesh" <animesh.manna@intel.com>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH] drm/i915/dp: ALPM init to be done after DPCD init
Date: Mon, 2 Mar 2026 13:41:05 +0530 [thread overview]
Message-ID: <da60a6a4-7fab-42d5-b806-942cab4bde62@intel.com> (raw)
In-Reply-To: <1bec280e94efd93069cf807703a41f5c631341d3.camel@intel.com>
On 02-03-2026 13:30, Hogander, Jouni wrote:
> On Mon, 2026-03-02 at 12:50 +0530, Murthy, Arun R wrote:
>> On 02-03-2026 12:14, Hogander, Jouni wrote:
>>> On Mon, 2026-03-02 at 09:06 +0530, Arun R Murthy wrote:
>>>> In ALPM init, the DPCD register ALPM_CAPABILITIES are to be read.
>>>> This
>>>> read has to happen after the DPCD init.
>>>>
>>>> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
>>>> ---
>>>> drivers/gpu/drm/i915/display/intel_dp.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
>>>> b/drivers/gpu/drm/i915/display/intel_dp.c
>>>> index 613559d11133..e60802b0b8c9 100644
>>>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>>>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>>>> @@ -6948,8 +6948,6 @@ static bool intel_edp_init_connector(struct
>>>> intel_dp *intel_dp,
>>>> */
>>>> intel_hpd_enable_detection(encoder);
>>>>
>>>> - intel_alpm_init(intel_dp);
>>>> -
>>>> /* Cache DPCD and EDID for edp. */
>>>> has_dpcd = intel_edp_init_dpcd(intel_dp, connector);
>>>>
>>>> @@ -6961,6 +6959,8 @@ static bool intel_edp_init_connector(struct
>>>> intel_dp *intel_dp,
>>>> goto out_vdd_off;
>>>> }
>>>>
>>>> + intel_alpm_init(intel_dp);
>>> This will cause problems to PSR/Panel Replay. intel_psr_init_dpcd
>>> is
>>> relying on ALPM dpcd init is done first.
>>>
>>> BR,
>>> Jouni Högander
>> I think this will also have to be moved down.
>>
>> For eDP intel_psr_init_dpcd() is called in intel_edp_init_dpcd.
>> So can
>> we move intel_alpm_init inside intel_edp_init_dpcd() ? Just before
>> calling intel_psr_init_dpcd !
>> Also rename intel_alpm_init() to intel_alpm_init_dpcd() ?
> Animesh has some ongoing work related:
>
> https://patchwork.freedesktop.org/patch/687711/?series=156417&rev=4
I think we can still go ahead with those. The one that I am trying to
fix is move alpm_init inside intel_edp_init_dpcd() just before
intel_psr_init_dpcd().
Will float a patch with the said changes.
Thanks for the review.
Thanks and Regards,
Arun R Murthy
--------------------
>
> I think it should be ok to move and rename it. That mutex_init within
> should be handled somehow.
>
> BR,
> Jouni Högander
>
>> Thanks and Regards,
>> Arun R Murthy
>> --------------------
>>
>>>> +
>>>> /*
>>>> * VBT and straps are liars. Also check HPD as that
>>>> seems
>>>> * to be the most reliable piece of information
>>>> available.
next prev parent reply other threads:[~2026-03-02 8:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 3:36 [PATCH] drm/i915/dp: ALPM init to be done after DPCD init Arun R Murthy
2026-03-02 3:44 ` ✓ CI.KUnit: success for " Patchwork
2026-03-02 4:27 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-02 5:31 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-02 6:44 ` [PATCH] " Hogander, Jouni
2026-03-02 7:20 ` Murthy, Arun R
2026-03-02 8:00 ` Hogander, Jouni
2026-03-02 8:11 ` Murthy, Arun R [this message]
2026-03-02 8:40 ` [PATCHv2 1/2] drm/i915/dp: Read ALPM caps " Arun R Murthy
2026-03-02 8:40 ` [PATCHv2 2/2] drm/i915/dp: Rename alpm_init to alpm_init_dpcd Arun R Murthy
2026-03-02 14:58 ` Dibin Moolakadan Subrahmanian
2026-03-03 4:10 ` Murthy, Arun R
2026-03-03 11:30 ` Hogander, Jouni
2026-03-04 4:05 ` [PATCHv4] drm/i915/dp: Read ALPM caps after DPCD init Arun R Murthy
2026-03-04 6:05 ` Manna, Animesh
2026-03-04 6:17 ` Hogander, Jouni
2026-03-04 6:22 ` Hogander, Jouni
2026-03-04 6:24 ` Murthy, Arun R
2026-03-04 4:13 ` ✓ CI.KUnit: success for drm/i915/dp: ALPM init to be done after DPCD init (rev4) Patchwork
2026-03-04 4:56 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-04 6:38 ` [PATCHv5] drm/i915/dp: Read ALPM caps after DPCD init Arun R Murthy
2026-03-04 6:53 ` Hogander, Jouni
2026-03-04 6:46 ` ✓ CI.KUnit: success for drm/i915/dp: ALPM init to be done after DPCD init (rev5) Patchwork
2026-03-04 7:21 ` [PATCHv6] drm/i915/dp: Read ALPM caps after DPCD init Arun R Murthy
2026-03-09 9:38 ` Manna, Animesh
2026-03-12 11:43 ` Jani Nikula
2026-03-04 7:34 ` ✗ Xe.CI.BAT: failure for drm/i915/dp: ALPM init to be done after DPCD init (rev5) Patchwork
2026-03-04 8:20 ` ✓ CI.KUnit: success for drm/i915/dp: ALPM init to be done after DPCD init (rev6) Patchwork
2026-03-04 9:00 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-05 6:06 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-05 9:40 ` ✗ Xe.CI.BAT: " Patchwork
2026-03-05 10:43 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-06 4:49 ` ✓ CI.KUnit: success for drm/i915/dp: ALPM init to be done after DPCD init (rev7) Patchwork
2026-03-06 5:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-07 4:01 ` ✗ Xe.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=da60a6a4-7fab-42d5-b806-942cab4bde62@intel.com \
--to=arun.r.murthy@intel.com \
--cc=animesh.manna@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@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