Lyude Paul fe7553bef8 drm/amdgpu: Don't ignore rc from drm_dp_mst_topology_mgr_resume()
drm_dp_mst_topology_mgr_resume() returns whether or not it managed to
find the topology in question after a suspend resume cycle, and the
driver is supposed to check this value and disable MST accordingly if
it's gone-in addition to sending a hotplug in order to notify userspace
that something changed during suspend.

Currently, amdgpu just makes the mistake of ignoring the return code
from drm_dp_mst_topology_mgr_resume() which means that if a topology was
removed in suspend, amdgpu never notices and assumes it's still
connected which leads to all sorts of problems.

So, fix this by actually checking the rc from
drm_dp_mst_topology_mgr_resume(). Also, reformat the rest of the
function while we're at it to fix the over-indenting.

Signed-off-by: Lyude Paul <lyude@redhat.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Cc: Jerry Zuo <Jerry.Zuo@amd.com>
Cc: <stable@vger.kernel.org> # v4.15+
Link: https://patchwork.freedesktop.org/patch/msgid/20190108211133.32564-2-lyude@redhat.com
2019-01-08 17:58:24 -05:00
..
2018-12-19 09:40:13 +01:00
2019-01-02 18:47:56 -08:00
2018-12-31 17:32:35 -08:00
2018-12-29 08:20:44 -07:00
2018-12-27 10:43:24 -08:00
2018-12-27 10:43:24 -08:00
2019-01-05 11:28:39 -08:00
2018-12-28 20:54:57 -08:00
2018-12-29 13:03:29 -08:00
2018-12-28 13:19:59 -08:00
2019-01-01 15:55:29 -08:00
2018-12-29 09:40:40 -08:00
2018-12-25 14:52:50 -08:00
2019-01-05 11:30:37 -08:00
2018-12-28 16:52:18 -08:00
2018-12-28 16:52:18 -08:00
2018-12-29 12:03:17 -08:00
2019-01-05 17:57:34 -08:00
2019-01-05 11:23:17 -08:00
2018-12-29 13:03:29 -08:00
2018-12-28 20:54:57 -08:00
2018-12-24 12:06:56 +01:00
2019-01-01 13:24:31 -08:00
2018-12-31 17:32:35 -08:00
2018-12-25 14:43:54 -08:00
2018-12-28 14:48:06 -08:00
2018-12-31 13:06:30 -08:00
2019-01-05 11:30:37 -08:00
2018-12-28 20:54:57 -08:00
2019-01-05 17:57:34 -08:00
2019-01-01 15:55:29 -08:00
2019-01-05 18:15:37 -08:00
2019-01-01 13:16:45 -08:00
2018-12-29 13:40:29 -08:00