Commit 7f2be468 authored by Lyude Paul's avatar Lyude Paul Committed by Alex Deucher
Browse files

drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages 



These are some very loud debug statements that get printed on every
vblank when driver level debug printing is enabled in DRM, and doesn't
really tell us anything that isn't related to vblanks. So let's move
this over to the proper debug flag to be a little less spammy with our
debug output.

Reviewed-by: default avatarHarry Wentland <harry.wentland@amd.com>
Signed-off-by: default avatarLyude Paul <lyude@redhat.com>
Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
parent 9543a9c3

drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c

+8 −6
Original line number Diff line number Diff line
@@ -410,7 +410,8 @@ static void dm_vupdate_high_irq(void *interrupt_params) 
	if (acrtc) {

		acrtc_state = to_dm_crtc_state(acrtc->base.state);



		DRM_DEBUG_DRIVER("crtc:%d, vupdate-vrr:%d\n", acrtc->crtc_id,

		DRM_DEBUG_VBL("crtc:%d, vupdate-vrr:%d\n",

			      acrtc->crtc_id,

			      amdgpu_dm_vrr_active(acrtc_state));



		/* Core vblank handling is done here after end of front-porch in
@@ -461,7 +462,8 @@ static void dm_crtc_high_irq(void *interrupt_params) 
	if (acrtc) {

		acrtc_state = to_dm_crtc_state(acrtc->base.state);



		DRM_DEBUG_DRIVER("crtc:%d, vupdate-vrr:%d\n", acrtc->crtc_id,

		DRM_DEBUG_VBL("crtc:%d, vupdate-vrr:%d\n",

			      acrtc->crtc_id,

			      amdgpu_dm_vrr_active(acrtc_state));



		/* Core vblank handling at start of front-porch is only possible
@@ -525,7 +527,7 @@ static void dm_dcn_crtc_high_irq(void *interrupt_params) 


	acrtc_state = to_dm_crtc_state(acrtc->base.state);



	DRM_DEBUG_DRIVER("crtc:%d, vupdate-vrr:%d\n", acrtc->crtc_id,

	DRM_DEBUG_VBL("crtc:%d, vupdate-vrr:%d\n", acrtc->crtc_id,

		      amdgpu_dm_vrr_active(acrtc_state));



	amdgpu_dm_crtc_handle_crc_irq(&acrtc->base);

CRA Git | Maintained and supported by SUSTech CRA and CCSE