diff options
| author | Wayne Lin <[email protected]> | 2022-04-13 15:52:48 +0800 |
|---|---|---|
| committer | Alex Deucher <[email protected]> | 2022-06-21 18:17:22 -0400 |
| commit | 10a36226157035e84aaa58e1699a32b3de2755af (patch) | |
| tree | a40f5fb42edc0b083c5101a8c118df63fca8a5be /tools/perf/scripts/python/bin | |
| parent | 4dd905fd9429626937107ca13770aa836c8a7e6e (diff) | |
drm/amd/display: Revert "drm/amd/display: Add flag to detect dpms force off during HPD"
This reverts commit 035f54969bb2c1a5ced52f43e4ef393e0c0f6bfa.
The reverted commit was trying to fix side effect brought by
commit 3c4d55c9b9be ("drm/amd/display: turn DPMS off on connector unplug")
However,
* This reverted commit will have mst case never call dm_set_dpms_off()
which conflicts the idea of original commit 3c4d55c9b9be ("drm/amd/display: turn DPMS off on connector unplug")
That's due to dm_crtc_state is always null since the input parameter
aconnector is the root device (source) of mst topology. It's not an
end stream sink within the mst topology.
* Setting dpms off should be triggered by usermode. Besdies, it seems
usermode does release relevant resource for mst & non-mst case when
unplug connecotr now. Which means we no longer need both commits now:
commit 3c4d55c9b9be ("drm/amd/display: turn DPMS off on connector unplug")
commit 035f54969bb2 ("drm/amd/display: Add flag to detect dpms force off during HPD")
Tested-by: Daniel Wheeler <[email protected]>
Reviewed-by: Aurabindo Jayamohanan Pillai <[email protected]>
Acked-by: Rodrigo Siqueira <[email protected]>
Acked-by: Lyude Paul <[email protected]>
Signed-off-by: Wayne Lin <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions