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

33 lines
1.3 KiB
Diff
Raw Normal View History

2019-07-16 12:59:21 +00:00
From 8f8f3ee1e3ae35df618761475293dc5d8285b6e0 Mon Sep 17 00:00:00 2001
From: Adam Jackson <ajax@redhat.com>
2017-07-10 15:40:53 +00:00
Date: Mon, 10 Jul 2017 08:11:48 -0700
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
---
2019-07-16 12:59:21 +00:00
drivers/gpu/drm/i915/display/intel_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
2019-07-16 12:59:21 +00:00
diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
index 8592a7d422de..e915cf6b0ba6 100644
--- a/drivers/gpu/drm/i915/display/intel_display.c
+++ b/drivers/gpu/drm/i915/display/intel_display.c
@@ -12982,7 +12982,7 @@ verify_crtc_state(struct drm_crtc *crtc,
2017-07-10 15:40:53 +00:00
sw_config = to_intel_crtc_state(new_crtc_state);
2019-07-16 12:59:21 +00:00
if (!intel_pipe_config_compare(sw_config, pipe_config, false)) {
- I915_STATE_WARN(1, "pipe state doesn't match!\n");
2019-07-16 12:59:21 +00:00
+ DRM_DEBUG_KMS(1, "pipe state doesn't match!\n");
intel_dump_pipe_config(pipe_config, NULL, "[hw state]");
intel_dump_pipe_config(sw_config, NULL, "[sw state]");
}
2015-09-08 12:34:33 +00:00
--
2019-07-16 12:59:21 +00:00
2.21.0
2015-09-08 12:34:33 +00:00