It's normal to receive one or two of these during mode setting activity, so just make the output debug only. We can change this in the future if we ever make our training sequences interrupt driven and properly handle the various types of interrupts.
Signed-off-by: Jesse Barnes <[email protected]> --- drivers/gpu/drm/i915/i915_irq.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c index 87951e3..d431fc4 100644 --- a/drivers/gpu/drm/i915/i915_irq.c +++ b/drivers/gpu/drm/i915/i915_irq.c @@ -427,8 +427,7 @@ static void pch_irq_handler(struct drm_device *dev) fdia = I915_READ(FDI_RXA_IIR); fdib = I915_READ(FDI_RXB_IIR); - DRM_ERROR("PCH FDI RX interrupt; FDI RXA IIR: 0x%08x, FDI RXB IIR: 0x%08x\n", - fdia, fdib); + DRM_DEBUG_DRIVER("PCH FDI RX interrupt; FDI RXA IIR: 0x%08x, FDI RXB IIR: 0x%08x\n", fdia, fdib); } if (pch_iir & (SDE_TRANSB_CRC_DONE | SDE_TRANSA_CRC_DONE)) -- 1.7.0.4 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
