summaryrefslogtreecommitdiff
path: root/scripts/git.orderFile
diff options
context:
space:
mode:
authorRoman Li <roman.li@amd.com>2024-06-25 20:23:36 +0300
committerAlex Deucher <alexander.deucher@amd.com>2024-07-24 00:07:09 +0300
commite8d77cfdd2698039667432b8569bac34d13508c1 (patch)
tree4aee8d4d7759323efd1490ba1f520d7bd677cc5e /scripts/git.orderFile
parent98579743c4561acc3b1c7d2f3fcd46b2160db5ba (diff)
downloadlinux-e8d77cfdd2698039667432b8569bac34d13508c1.tar.xz
drm/amd/display: Replace assert with error message in dp_retrieve_lttpr_cap()
[Why] When assert in dp_retrieve_lttpr_cap() is hit, dmesg has traces like: RIP: 0010:dp_retrieve_lttpr_cap+0xcc/0x1a0 [amdgpu] Call Trace: <TASK> dp_retrieve_lttpr_cap+0xcc/0x1a0 [amdgpu] report_bug+0x1e8/0x240 handle_bug+0x46/0x80 link_detect+0x35/0x580 [amdgpu] It happens when LTTPRs fail to increment dpcd repeater count. We have a recovery action in place for such cases. Assert is misleading, an indicative error in dmesg is more useful. [How] Remove ASSERT and use DC_LOG_ERROR instead. Reviewed-by: Michael Strauss <michael.strauss@amd.com> Signed-off-by: Jerry Zuo <jerry.zuo@amd.com> Signed-off-by: Roman Li <roman.li@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'scripts/git.orderFile')
0 files changed, 0 insertions, 0 deletions