kernel/drm-i915-hush-check-crtc-state.patch

33 lines
1.3 KiB
Diff
Raw Normal View History

2015-09-08 12:34:33 +00:00
From 02f47b49ab1cdbe62ceb71b658e2c469799ae368 Mon Sep 17 00:00:00 2001
From: Adam Jackson <ajax@redhat.com>
Date: Wed, 13 Nov 2013 10:17:24 -0500
Subject: [PATCH] drm/i915: hush check crtc state
2013-11-13 15:17:24 +00:00
This is _by far_ the most common backtrace for i915 on retrace.fp.o, and
it's mostly useless noise. There's not enough context when it's generated
to know if something actually went wrong. Downgrade the message to
KMS debugging so we can still get it if we want it.
Bugzilla: 1027037 1028785
Upstream-status: http://lists.freedesktop.org/archives/intel-gfx/2013-November/035948.html
---
drivers/gpu/drm/i915/intel_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
2015-09-08 12:34:33 +00:00
index ca9278be49f7..308ac0539a87 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
2015-09-08 12:34:33 +00:00
@@ -12688,7 +12688,7 @@ check_crtc_state(struct drm_device *dev, struct drm_atomic_state *old_state)
sw_config = to_intel_crtc_state(crtc->state);
if (!intel_pipe_config_compare(dev, sw_config,
pipe_config, false)) {
- I915_STATE_WARN(1, "pipe state doesn't match!\n");
2013-11-13 15:17:24 +00:00
+ DRM_DEBUG_KMS("pipe state doesn't match!\n");
2015-09-08 12:34:33 +00:00
intel_dump_pipe_config(intel_crtc, pipe_config,
2013-11-13 15:17:24 +00:00
"[hw state]");
2015-09-08 12:34:33 +00:00
intel_dump_pipe_config(intel_crtc, sw_config,
--
2.4.3