[RESEND PATCH v6 13/14] drm/atomic: Use debug category printer for atomic state printer
Sean Paul
sean at poorly.run
Wed Jul 21 17:55:20 UTC 2021
From: Sean Paul <seanpaul at chromium.org>
The atomic state is printed if the DRM_UT_STATE is active, but it's
printed at INFO level. This patch converts it to use the debug
category printer so:
a- it's consistent with other DRM_UT_STATE logging
b- it's properly routed through drm_trace when introduced
Signed-off-by: Sean Paul <seanpaul at chromium.org>
Changes in v6:
-Added to the set
---
drivers/gpu/drm/drm_atomic_uapi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_atomic_uapi.c b/drivers/gpu/drm/drm_atomic_uapi.c
index 7e48d40600ff..7615ded60195 100644
--- a/drivers/gpu/drm/drm_atomic_uapi.c
+++ b/drivers/gpu/drm/drm_atomic_uapi.c
@@ -1322,7 +1322,7 @@ int drm_mode_atomic_ioctl(struct drm_device *dev,
struct drm_out_fence_state *fence_state;
int ret = 0;
unsigned int i, j, num_fences;
- struct drm_printer p = drm_info_printer(dev->dev);
+ struct drm_printer p = drm_debug_category_printer(DRM_UT_STATE, "commit_state");
/* disallow for drivers not supporting atomic: */
if (!drm_core_check_feature(dev, DRIVER_ATOMIC))
--
Sean Paul, Software Engineer, Google / Chromium OS
More information about the dri-devel
mailing list