From: Jackie Dong <xy-jackie@139.com>
To: harry.wentland@amd.com, sunpeng.li@amd.com, siqueira@igalia.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@gmail.com, simona@ffwll.ch, alex.hung@amd.com,
ivan.lipski@amd.com, wenjing.liu@amd.com, robin.chen@amd.com,
superm1@kernel.org, meenakshikumar.somasundaram@amd.com,
Derek.Lai@amd.com, wei-guang.li@amd.com,
gaghik.khachatrian@amd.com, jack.chang@amd.com,
Duncan.Ma@amd.com, PeiChen.Huang@amd.com,
aurabindo.pillai@amd.com, zhao.xichao@vivo.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Jackie Dong <xy-jackie@139.com>
Subject: [PATCH] drm/amd/display:Check dp_128b_132b_supported_link_rates.raw before link_rate setting
Date: Tue, 30 Jun 2026 22:59:55 +0800 [thread overview]
Message-ID: <20260630145955.13994-1-xy-jackie@139.com> (raw)
[WHY]
In the evolution of displays from DP 1.4 to DP 2.0, due to considerations
some factors,such as cost, some displays support 128b/132b encoding but
do not support UHBR rate transmission. The values can be read from DPCD
register address as below.
0x00006 is 03
0x02215 is 00
For such displays, the current kernel reports the following error message.
[drm:dp_retrieve_lttpr_cap [amdgpu]] *ERROR* retrieve_link_cap: Invalid RX
128b_132b_supported_link_rates
[HOW]
Add new judgment: if all bits in dp_128b_132b_supported_link_rates.raw
are non-zero, then further determine the specific UHBR type; otherwise,
determine that the display does not support UHBR.
Signed-off-by: Jackie Dong <xy-jackie@139.com>
---
.../gpu/drm/amd/display/dc/link/protocols/link_dp_capability.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_capability.c b/drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_capability.c
index 47abb4066709..58cbb7ac8f9e 100644
--- a/drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_capability.c
+++ b/drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_capability.c
@@ -2079,7 +2079,8 @@ static bool retrieve_link_cap(struct dc_link *link)
if (!dpcd_read_sink_ext_caps(link))
link->dpcd_sink_ext_caps.raw = 0;
- if (link->dpcd_caps.channel_coding_cap.bits.DP_128b_132b_SUPPORTED) {
+ if (link->dpcd_caps.channel_coding_cap.bits.DP_128b_132b_SUPPORTED &&
+ link->dpcd_caps.dp_128b_132b_supported_link_rates.raw) {
DC_LOG_DP2("128b/132b encoding is supported at link %d", link->link_index);
/* Read 128b/132b suppoerted link rates */
--
2.43.0
next reply other threads:[~2026-06-30 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 14:59 Jackie Dong [this message]
2026-07-17 20:15 ` George Zhang
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=20260630145955.13994-1-xy-jackie@139.com \
--to=xy-jackie@139.com \
--cc=Derek.Lai@amd.com \
--cc=Duncan.Ma@amd.com \
--cc=PeiChen.Huang@amd.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gaghik.khachatrian@amd.com \
--cc=harry.wentland@amd.com \
--cc=ivan.lipski@amd.com \
--cc=jack.chang@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meenakshikumar.somasundaram@amd.com \
--cc=robin.chen@amd.com \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=superm1@kernel.org \
--cc=wei-guang.li@amd.com \
--cc=wenjing.liu@amd.com \
--cc=zhao.xichao@vivo.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