Blob Blame History Raw
From: Andrew Jiang <Andrew.Jiang@amd.com>
Date: Fri, 6 Oct 2017 18:02:23 -0400
Subject: drm/amd/display: Don't set cursor address is 0 logging as errors
Git-commit: b0f8d4e963de8cd77c237a8ea37799f6f5ce995a
Patch-mainline: v4.15-rc1
References: FATE#326289 FATE#326079 FATE#326049 FATE#322398 FATE#326166

This actually happens quite a bit, and having it as an error causes
false positive messages when running tests.

Signed-off-by: Andrew Jiang <Andrew.Jiang@amd.com>
Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
Acked-by: Harry Wentland <Harry.Wentland@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Acked-by: Petr Tesarik <ptesarik@suse.com>
---
 drivers/gpu/drm/amd/display/dc/core/dc_stream.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
+++ b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
@@ -190,7 +190,7 @@ bool dc_stream_set_cursor_attributes(
 	}
 
 	if (attributes->address.quad_part == 0) {
-		dm_error("DC: Cursor address is 0!\n");
+		dm_output_to_console("DC: Cursor address is 0!\n");
 		return false;
 	}