Commit 245524d9 authored by Hersen Wu's avatar Hersen Wu Committed by Alex Deucher

drm/amd/display: dp debugfs allow link rate lane count greater than dp rx reported caps

[Why]
when hw team does phy parameters tuning, there is need to force dp
link rate or lane count grater than the values from dp receiver to
check dp tx. current debufs limit link rate, lane count no more
than rx caps.

[How] remove force settings less than rx caps check

v2: Fix typo in title
Signed-off-by: default avatarHersen Wu <hersenxs.wu@amd.com>
Reviewed-by: default avatarCharlene Liu <Charlene.Liu@amd.com>
Acked-by: default avatarHarry Wentland <harry.wentland@amd.com>
Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
parent aca3e9a4
...@@ -214,8 +214,7 @@ static ssize_t dp_link_settings_write(struct file *f, const char __user *buf, ...@@ -214,8 +214,7 @@ static ssize_t dp_link_settings_write(struct file *f, const char __user *buf,
break; break;
} }
if (!valid_input || (param[0] > link->reported_link_cap.lane_count) || if (!valid_input) {
(param[1] > link->reported_link_cap.link_rate)) {
kfree(wr_buf); kfree(wr_buf);
DRM_DEBUG_DRIVER("Invalid Input value No HW will be programmed\n"); DRM_DEBUG_DRIVER("Invalid Input value No HW will be programmed\n");
return bytes_from_user; return bytes_from_user;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment