aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorRoman Li <[email protected]>2024-06-25 13:23:36 -0400
committerAlex Deucher <[email protected]>2024-07-23 17:07:09 -0400
commite8d77cfdd2698039667432b8569bac34d13508c1 (patch)
tree4aee8d4d7759323efd1490ba1f520d7bd677cc5e /tools/perf/scripts/python/export-to-postgresql.py
parent98579743c4561acc3b1c7d2f3fcd46b2160db5ba (diff)
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 <[email protected]> Signed-off-by: Jerry Zuo <[email protected]> Signed-off-by: Roman Li <[email protected]> Tested-by: Daniel Wheeler <[email protected]> Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions