diff options
| author | Lyude <[email protected]> | 2016-04-13 16:50:18 -0400 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2016-04-15 15:01:16 +0200 |
| commit | 1652fce65f70f104ffd0df0284b601d9103e1ebf (patch) | |
| tree | 976cf170b3cb8caa811091eea63e208b54fa0045 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | f6cd7daecff558fab2c45d15283d3e52f688342d (diff) | |
drm/dp/mst: Restore primary hub guid on resume
Some hubs are forgetful, and end up forgetting whatever GUID we set
previously after we do a suspend/resume cycle. This can lead to
hotplugging breaking (along with probably other things) since the hub
will start sending connection notifications with the wrong GUID. As
such, we need to check on resume whether or not the GUID the hub is
giving us is valid.
Signed-off-by: Lyude <[email protected]>
Signed-off-by: Dave Airlie <[email protected]>
Reviewed-by: Harry Wentland <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions