From: Ville Syrjälä <[email protected]> DRM_DEBUG_ATOMIC generates a lot of noise that no one normally cares about. However error paths everyone cares about, so hiding the error debugs under DRM_DEBUG_ATOMIC is a bad idea. Let's use DRM_DEBUG_KMS for those instead.
Signed-off-by: Ville Syrjälä <[email protected]> --- 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 index a08c4a45b8d3..4fe5c23f784a 100644 --- a/drivers/gpu/drm/i915/intel_display.c +++ b/drivers/gpu/drm/i915/intel_display.c @@ -13590,7 +13590,7 @@ static int intel_atomic_commit(struct drm_device *dev, ret = intel_atomic_prepare_commit(dev, state, nonblock); if (ret) { - DRM_DEBUG_ATOMIC("Preparing state failed with %i\n", ret); + DRM_DEBUG_KMS("Preparing state failed with %i\n", ret); return ret; } -- 2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
