All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915: Use per-device debugs for bigjoiner stuff
Date: Fri, 21 Jan 2022 16:06:17 +0200	[thread overview]
Message-ID: <87sfth2nfq.fsf@intel.com> (raw)
In-Reply-To: <20220121130710.10382-3-ville.syrjala@linux.intel.com>

On Fri, 21 Jan 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Specify which device we're talking about when spewing
> bigjoiner debugs.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  drivers/gpu/drm/i915/display/intel_display.c | 21 +++++++++++---------
>  1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 36e547bd0cbe..9fb72c356208 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -7633,9 +7633,10 @@ static int intel_atomic_check_bigjoiner(struct intel_atomic_state *state,
>  
>  	slave_crtc = intel_dsc_get_bigjoiner_secondary(crtc);
>  	if (!slave_crtc) {
> -		DRM_DEBUG_KMS("[CRTC:%d:%s] Big joiner configuration requires "
> -			      "CRTC + 1 to be used, doesn't exist\n",
> -			      crtc->base.base.id, crtc->base.name);
> +		drm_dbg_kms(&i915->drm,
> +			    "[CRTC:%d:%s] Big joiner configuration requires "
> +			    "CRTC + 1 to be used, doesn't exist\n",
> +			    crtc->base.base.id, crtc->base.name);
>  		return -EINVAL;
>  	}
>  
> @@ -7649,16 +7650,18 @@ static int intel_atomic_check_bigjoiner(struct intel_atomic_state *state,
>  	if (slave_crtc_state->uapi.enable)
>  		goto claimed;
>  
> -	DRM_DEBUG_KMS("[CRTC:%d:%s] Used as slave for big joiner\n",
> -		      slave_crtc->base.base.id, slave_crtc->base.name);
> +	drm_dbg_kms(&i915->drm,
> +		    "[CRTC:%d:%s] Used as slave for big joiner\n",
> +		    slave_crtc->base.base.id, slave_crtc->base.name);
>  
>  	return copy_bigjoiner_crtc_state(slave_crtc_state, new_crtc_state);
>  
>  claimed:
> -	DRM_DEBUG_KMS("[CRTC:%d:%s] Slave is enabled as normal CRTC, but "
> -		      "[CRTC:%d:%s] claiming this CRTC for bigjoiner.\n",
> -		      slave_crtc->base.base.id, slave_crtc->base.name,
> -		      master_crtc->base.base.id, master_crtc->base.name);
> +	drm_dbg_kms(&i915->drm,
> +		    "[CRTC:%d:%s] Slave is enabled as normal CRTC, but "
> +		    "[CRTC:%d:%s] claiming this CRTC for bigjoiner.\n",
> +		    slave_crtc->base.base.id, slave_crtc->base.name,
> +		    master_crtc->base.base.id, master_crtc->base.name);
>  	return -EINVAL;
>  }

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-01-21 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 13:07 [Intel-gfx] [PATCH 1/3] drm/i915: Reject bigjoiner if the pipe doesn't support it Ville Syrjala
2022-01-21 13:07 ` [Intel-gfx] [PATCH 2/3] drm/i915: Simplify intel_dsc_source_support() Ville Syrjala
2022-01-21 14:05   ` Jani Nikula
2022-01-21 13:07 ` [Intel-gfx] [PATCH 3/3] drm/i915: Use per-device debugs for bigjoiner stuff Ville Syrjala
2022-01-21 14:06   ` Jani Nikula [this message]
2022-01-21 14:03 ` [Intel-gfx] [PATCH 1/3] drm/i915: Reject bigjoiner if the pipe doesn't support it Jani Nikula
2022-01-21 15:55   ` Ville Syrjälä
2022-01-21 16:33     ` Ville Syrjälä
2022-01-21 14:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] " Patchwork
2022-01-21 18:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfth2nfq.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.