All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-01-24  1:07 ` Lyude Paul
  0 siblings, 0 replies; 9+ messages in thread
From: Lyude Paul @ 2020-01-24  1:07 UTC (permalink / raw)
  To: amd-gfx
  Cc: Harry Wentland, Leo Li, Alex Deucher, Christian König,
	David (ChunMing) Zhou, David Airlie, Daniel Vetter,
	Nicholas Kazlauskas, Bhawanpreet Lakha, David Francis,
	Mario Kleiner, dri-devel, linux-kernel

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.

Signed-off-by: Lyude Paul <lyude@redhat.com>
---
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 9402374d2466..3675e1c32707 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -407,8 +407,9 @@ 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,
-				 amdgpu_dm_vrr_active(acrtc_state));
+		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
 		 * vrr mode, as vblank timestamping will give valid results
@@ -458,8 +459,9 @@ 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,
-				 amdgpu_dm_vrr_active(acrtc_state));
+		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
 		 * in non-vrr mode, as only there vblank timestamping will give
@@ -522,8 +524,8 @@ 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,
-				amdgpu_dm_vrr_active(acrtc_state));
+	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);
 	drm_crtc_handle_vblank(&acrtc->base);
-- 
2.24.1


^ permalink raw reply related	[flat|nested] 9+ messages in thread
* [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-01-24  1:07 ` Lyude Paul
  0 siblings, 0 replies; 9+ messages in thread
From: Lyude Paul @ 2020-01-24  1:07 UTC (permalink / raw)
  To: amd-gfx
  Cc: Leo Li, Bhawanpreet Lakha, David Francis, linux-kernel,
	dri-devel, Nicholas Kazlauskas, David Airlie, Alex Deucher,
	Christian König

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.

Signed-off-by: Lyude Paul <lyude@redhat.com>
---
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 9402374d2466..3675e1c32707 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -407,8 +407,9 @@ 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,
-				 amdgpu_dm_vrr_active(acrtc_state));
+		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
 		 * vrr mode, as vblank timestamping will give valid results
@@ -458,8 +459,9 @@ 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,
-				 amdgpu_dm_vrr_active(acrtc_state));
+		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
 		 * in non-vrr mode, as only there vblank timestamping will give
@@ -522,8 +524,8 @@ 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,
-				amdgpu_dm_vrr_active(acrtc_state));
+	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);
 	drm_crtc_handle_vblank(&acrtc->base);
-- 
2.24.1

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply related	[flat|nested] 9+ messages in thread
* [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-01-24  1:07 ` Lyude Paul
  0 siblings, 0 replies; 9+ messages in thread
From: Lyude Paul @ 2020-01-24  1:07 UTC (permalink / raw)
  To: amd-gfx
  Cc: David (ChunMing) Zhou, Mario Kleiner, Leo Li, Bhawanpreet Lakha,
	David Francis, linux-kernel, dri-devel, Nicholas Kazlauskas,
	David Airlie, Daniel Vetter, Alex Deucher, Harry Wentland,
	Christian König

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.

Signed-off-by: Lyude Paul <lyude@redhat.com>
---
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 9402374d2466..3675e1c32707 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -407,8 +407,9 @@ 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,
-				 amdgpu_dm_vrr_active(acrtc_state));
+		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
 		 * vrr mode, as vblank timestamping will give valid results
@@ -458,8 +459,9 @@ 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,
-				 amdgpu_dm_vrr_active(acrtc_state));
+		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
 		 * in non-vrr mode, as only there vblank timestamping will give
@@ -522,8 +524,8 @@ 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,
-				amdgpu_dm_vrr_active(acrtc_state));
+	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);
 	drm_crtc_handle_vblank(&acrtc->base);
-- 
2.24.1

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply related	[flat|nested] 9+ messages in thread
* Re: [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
  2020-01-24  1:07 ` Lyude Paul
  (?)
@ 2020-01-24 14:48   ` Harry Wentland
  -1 siblings, 0 replies; 9+ messages in thread
From: Harry Wentland @ 2020-01-24 14:48 UTC (permalink / raw)
  To: Lyude Paul, amd-gfx
  Cc: Harry Wentland, Leo Li, Alex Deucher, Christian König,
	David (ChunMing) Zhou, David Airlie, Daniel Vetter,
	Nicholas Kazlauskas, Bhawanpreet Lakha, David Francis,
	Mario Kleiner, dri-devel, linux-kernel

On 2020-01-23 8:07 p.m., Lyude Paul wrote:
> 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.
> 
> Signed-off-by: Lyude Paul <lyude@redhat.com>

Thanks. Great change.

Reviewed-by: Harry Wentland <harry.wentland@amd.com>

Harry

> ---
>  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 9402374d2466..3675e1c32707 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -407,8 +407,9 @@ 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,
> -				 amdgpu_dm_vrr_active(acrtc_state));
> +		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
>  		 * vrr mode, as vblank timestamping will give valid results
> @@ -458,8 +459,9 @@ 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,
> -				 amdgpu_dm_vrr_active(acrtc_state));
> +		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
>  		 * in non-vrr mode, as only there vblank timestamping will give
> @@ -522,8 +524,8 @@ 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,
> -				amdgpu_dm_vrr_active(acrtc_state));
> +	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);
>  	drm_crtc_handle_vblank(&acrtc->base);
> 

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-01-24 14:48   ` Harry Wentland
  0 siblings, 0 replies; 9+ messages in thread
From: Harry Wentland @ 2020-01-24 14:48 UTC (permalink / raw)
  To: Lyude Paul, amd-gfx
  Cc: Leo Li, Bhawanpreet Lakha, David Francis, linux-kernel,
	dri-devel, Nicholas Kazlauskas, David Airlie, Alex Deucher,
	Christian König

On 2020-01-23 8:07 p.m., Lyude Paul wrote:
> 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.
> 
> Signed-off-by: Lyude Paul <lyude@redhat.com>

Thanks. Great change.

Reviewed-by: Harry Wentland <harry.wentland@amd.com>

Harry

> ---
>  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 9402374d2466..3675e1c32707 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -407,8 +407,9 @@ 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,
> -				 amdgpu_dm_vrr_active(acrtc_state));
> +		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
>  		 * vrr mode, as vblank timestamping will give valid results
> @@ -458,8 +459,9 @@ 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,
> -				 amdgpu_dm_vrr_active(acrtc_state));
> +		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
>  		 * in non-vrr mode, as only there vblank timestamping will give
> @@ -522,8 +524,8 @@ 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,
> -				amdgpu_dm_vrr_active(acrtc_state));
> +	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);
>  	drm_crtc_handle_vblank(&acrtc->base);
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-01-24 14:48   ` Harry Wentland
  0 siblings, 0 replies; 9+ messages in thread
From: Harry Wentland @ 2020-01-24 14:48 UTC (permalink / raw)
  To: Lyude Paul, amd-gfx
  Cc: David (ChunMing) Zhou, Mario Kleiner, Leo Li, Bhawanpreet Lakha,
	David Francis, linux-kernel, dri-devel, Nicholas Kazlauskas,
	David Airlie, Daniel Vetter, Alex Deucher, Harry Wentland,
	Christian König

On 2020-01-23 8:07 p.m., Lyude Paul wrote:
> 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.
> 
> Signed-off-by: Lyude Paul <lyude@redhat.com>

Thanks. Great change.

Reviewed-by: Harry Wentland <harry.wentland@amd.com>

Harry

> ---
>  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 9402374d2466..3675e1c32707 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -407,8 +407,9 @@ 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,
> -				 amdgpu_dm_vrr_active(acrtc_state));
> +		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
>  		 * vrr mode, as vblank timestamping will give valid results
> @@ -458,8 +459,9 @@ 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,
> -				 amdgpu_dm_vrr_active(acrtc_state));
> +		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
>  		 * in non-vrr mode, as only there vblank timestamping will give
> @@ -522,8 +524,8 @@ 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,
> -				amdgpu_dm_vrr_active(acrtc_state));
> +	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);
>  	drm_crtc_handle_vblank(&acrtc->base);
> 
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
  2020-01-24 14:48   ` Harry Wentland
  (?)
@ 2020-03-12 14:28     ` Alex Deucher
  -1 siblings, 0 replies; 9+ messages in thread
From: Alex Deucher @ 2020-03-12 14:28 UTC (permalink / raw)
  To: Harry Wentland
  Cc: Lyude Paul, amd-gfx list, Leo Li, Bhawanpreet Lakha,
	David Francis, LKML, Maling list - DRI developers,
	Nicholas Kazlauskas, David Airlie, Alex Deucher,
	Christian König

Applied.  thanks!

Alex

On Fri, Jan 24, 2020 at 9:48 AM Harry Wentland <hwentlan@amd.com> wrote:
>
> On 2020-01-23 8:07 p.m., Lyude Paul wrote:
> > 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.
> >
> > Signed-off-by: Lyude Paul <lyude@redhat.com>
>
> Thanks. Great change.
>
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>
> Harry
>
> > ---
> >  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
> >  1 file changed, 8 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > index 9402374d2466..3675e1c32707 100644
> > --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > @@ -407,8 +407,9 @@ 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,
> > -                              amdgpu_dm_vrr_active(acrtc_state));
> > +             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
> >                * vrr mode, as vblank timestamping will give valid results
> > @@ -458,8 +459,9 @@ 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,
> > -                              amdgpu_dm_vrr_active(acrtc_state));
> > +             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
> >                * in non-vrr mode, as only there vblank timestamping will give
> > @@ -522,8 +524,8 @@ 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,
> > -                             amdgpu_dm_vrr_active(acrtc_state));
> > +     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);
> >       drm_crtc_handle_vblank(&acrtc->base);
> >
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-03-12 14:28     ` Alex Deucher
  0 siblings, 0 replies; 9+ messages in thread
From: Alex Deucher @ 2020-03-12 14:28 UTC (permalink / raw)
  To: Harry Wentland
  Cc: Leo Li, David Francis, LKML, amd-gfx list, Christian König,
	David Airlie, Maling list - DRI developers, Alex Deucher,
	Bhawanpreet Lakha, Nicholas Kazlauskas

Applied.  thanks!

Alex

On Fri, Jan 24, 2020 at 9:48 AM Harry Wentland <hwentlan@amd.com> wrote:
>
> On 2020-01-23 8:07 p.m., Lyude Paul wrote:
> > 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.
> >
> > Signed-off-by: Lyude Paul <lyude@redhat.com>
>
> Thanks. Great change.
>
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>
> Harry
>
> > ---
> >  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
> >  1 file changed, 8 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > index 9402374d2466..3675e1c32707 100644
> > --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > @@ -407,8 +407,9 @@ 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,
> > -                              amdgpu_dm_vrr_active(acrtc_state));
> > +             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
> >                * vrr mode, as vblank timestamping will give valid results
> > @@ -458,8 +459,9 @@ 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,
> > -                              amdgpu_dm_vrr_active(acrtc_state));
> > +             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
> >                * in non-vrr mode, as only there vblank timestamping will give
> > @@ -522,8 +524,8 @@ 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,
> > -                             amdgpu_dm_vrr_active(acrtc_state));
> > +     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);
> >       drm_crtc_handle_vblank(&acrtc->base);
> >
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread
* Re: [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages
@ 2020-03-12 14:28     ` Alex Deucher
  0 siblings, 0 replies; 9+ messages in thread
From: Alex Deucher @ 2020-03-12 14:28 UTC (permalink / raw)
  To: Harry Wentland
  Cc: Leo Li, David Francis, LKML, amd-gfx list, Christian König,
	David Airlie, Maling list - DRI developers, Alex Deucher,
	Bhawanpreet Lakha, Nicholas Kazlauskas

Applied.  thanks!

Alex

On Fri, Jan 24, 2020 at 9:48 AM Harry Wentland <hwentlan@amd.com> wrote:
>
> On 2020-01-23 8:07 p.m., Lyude Paul wrote:
> > 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.
> >
> > Signed-off-by: Lyude Paul <lyude@redhat.com>
>
> Thanks. Great change.
>
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>
> Harry
>
> > ---
> >  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 ++++++++------
> >  1 file changed, 8 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > index 9402374d2466..3675e1c32707 100644
> > --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> > @@ -407,8 +407,9 @@ 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,
> > -                              amdgpu_dm_vrr_active(acrtc_state));
> > +             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
> >                * vrr mode, as vblank timestamping will give valid results
> > @@ -458,8 +459,9 @@ 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,
> > -                              amdgpu_dm_vrr_active(acrtc_state));
> > +             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
> >                * in non-vrr mode, as only there vblank timestamping will give
> > @@ -522,8 +524,8 @@ 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,
> > -                             amdgpu_dm_vrr_active(acrtc_state));
> > +     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);
> >       drm_crtc_handle_vblank(&acrtc->base);
> >
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

^ permalink raw reply	[flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-03-12 14:28 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-24  1:07 [PATCH] drm/amdgpu: Stop using the DRIVER debugging flag for vblank debugging messages Lyude Paul
2020-01-24  1:07 ` Lyude Paul
2020-01-24  1:07 ` Lyude Paul
2020-01-24 14:48 ` Harry Wentland
2020-01-24 14:48   ` Harry Wentland
2020-01-24 14:48   ` Harry Wentland
2020-03-12 14:28   ` Alex Deucher
2020-03-12 14:28     ` Alex Deucher
2020-03-12 14:28     ` Alex Deucher

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.