MST has its unique sequence that may get failed due to no stream
in atomic check in some cases, e.g., hotplug, S3 resume.

Remove the ERROR message in the stream create routine, and leave
its caller to decide if additional action is required.

Signed-off-by: Jerry (Fangzhi) Zuo <[email protected]>
---
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 53c49c901a6a..a9ed225d2ae0 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -3052,10 +3052,8 @@ create_stream_for_sink(struct amdgpu_dm_connector 
*aconnector,
 
        stream = dc_create_stream_for_sink(sink);
 
-       if (stream == NULL) {
-               DRM_ERROR("Failed to create stream for sink!\n");
+       if (stream == NULL)
                goto finish;
-       }
 
        stream->dm_stream_context = aconnector;
 
-- 
2.14.1

_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Reply via email to