From: Arun R Murthy <arun.r.murthy@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: animesh.manna@intel.com, ankit.k.nautiyal@intel.com,
jani.nikula@intel.com, jouni.hogander@intel.com,
Arun R Murthy <arun.r.murthy@intel.com>
Subject: [PATCHv2 1/2] drm/i915/dp: Read ALPM caps after DPCD init
Date: Mon, 2 Mar 2026 14:10:29 +0530 [thread overview]
Message-ID: <20260302084030.463284-1-arun.r.murthy@intel.com> (raw)
In-Reply-To: <20260302033630.428913-1-arun.r.murthy@intel.com>
For eDP read the ALPM DPCD caps after DPCD initalization and just before
the PSR init.
v2: Move intel_alpm_init to intel_edp_init_dpcd (Jouni)
Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 025e906b63a9..1544758c0bbc 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -4748,6 +4748,9 @@ intel_edp_init_dpcd(struct intel_dp *intel_dp, struct intel_connector *connector
*/
intel_dp_init_source_oui(intel_dp);
+ /* Read ALPM DPCD caps before reading the PSR CAPS */
+ intel_alpm_init(intel_dp);
+
/*
* This has to be called after intel_dp->edp_dpcd is filled, PSR checks
* for SET_POWER_CAPABLE bit in intel_dp->edp_dpcd[1]
@@ -6914,8 +6917,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);
--
2.25.1
next prev parent reply other threads:[~2026-03-02 8:42 UTC|newest]
Thread overview: 41+ 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 4:35 ` ✓ i915.CI.BAT: " Patchwork
2026-03-02 5:31 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-02 6:35 ` ✗ i915.CI.Full: " 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
2026-03-02 8:40 ` Arun R Murthy [this message]
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 5:02 ` ✗ i915.CI.BAT: " 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:07 ` ✓ i915.CI.BAT: success " 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 8:55 ` ✓ i915.CI.BAT: " 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:42 ` ✓ i915.CI.Full: success " Patchwork
2026-03-05 10:43 ` ✗ Xe.CI.FULL: failure " 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=20260302084030.463284-1-arun.r.murthy@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 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.