98a08a4
From: Adam Jackson <ajax@redhat.com>
98a08a4
Date: Wed, 13 Nov 2013 10:17:24 -0500
98a08a4
Subject: [PATCH] drm/i915: hush check crtc state
98a08a4
98a08a4
This is _by far_ the most common backtrace for i915 on retrace.fp.o, and
98a08a4
it's mostly useless noise.  There's not enough context when it's generated
98a08a4
to know if something actually went wrong.  Downgrade the message to
98a08a4
KMS debugging so we can still get it if we want it.
98a08a4
98a08a4
Bugzilla: 1027037 1028785
98a08a4
Upstream-status: http://lists.freedesktop.org/archives/intel-gfx/2013-November/035948.html
98a08a4
---
98a08a4
 drivers/gpu/drm/i915/intel_display.c | 2 +-
98a08a4
 1 file changed, 1 insertion(+), 1 deletion(-)
98a08a4
98a08a4
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
a091e2f
index 2e2f6443fd53..2a0813e5ace9 100644
98a08a4
--- a/drivers/gpu/drm/i915/intel_display.c
98a08a4
+++ b/drivers/gpu/drm/i915/intel_display.c
98a08a4
@@ -10869,7 +10869,7 @@ check_crtc_state(struct drm_device *dev)
98a08a4
 
98a08a4
 		if (active &&
98a08a4
 		    !intel_pipe_config_compare(dev, &crtc->config, &pipe_config)) {
98a08a4
-			I915_STATE_WARN(1, "pipe state doesn't match!\n");
98a08a4
+			DRM_DEBUG_KMS("pipe state doesn't match!\n");
98a08a4
 			intel_dump_pipe_config(crtc, &pipe_config,
98a08a4
 					       "[hw state]");
98a08a4
 			intel_dump_pipe_config(crtc, &crtc->config,
98a08a4
-- 
98a08a4
2.1.0
98a08a4