Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Luca Coelho <luca@coelho.fi>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: remove noisy logs in intel_dp_dsc_get_output_bpp()
Date: Tue, 07 Jun 2022 11:05:22 +0300	[thread overview]
Message-ID: <871qw0rj99.fsf@intel.com> (raw)
In-Reply-To: <20220607074433.1202917-1-luca@coelho.fi>

On Tue, 07 Jun 2022, Luca Coelho <luca@coelho.fi> wrote:
> From: Luca Coelho <luciano.coelho@intel.com>
>
> The intel_dp_dsc_get_output_bpp() function outputs two lines of
> unconditional logs, which was okay when it was called only once.  But
> now, we also call this function from intel_dp_mode_valid(), which is
> in turn called for every mode we need to validate.  This causes a lot
> of useless noise.
>
> Remove the unconditional prints to avoid spamming the logs.  Also
> remove one more print that is not unconditional, but is related.
>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

Some of these might be useful on the compute config path, but meh.

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

> ---
>  drivers/gpu/drm/i915/display/intel_dp.c | 5 -----
>  1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index b8e2d3cd4d68..e198c6d7e3b5 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -658,7 +658,6 @@ static u16 intel_dp_dsc_get_output_bpp(struct drm_i915_private *i915,
>  	 */
>  	bits_per_pixel = (link_clock * lane_count * 8) /
>  			 intel_dp_mode_to_fec_clock(mode_clock);
> -	drm_dbg_kms(&i915->drm, "Max link bpp: %u\n", bits_per_pixel);
>  
>  	/* Small Joiner Check: output bpp <= joiner RAM (bits) / Horiz. width */
>  	max_bpp_small_joiner_ram = small_joiner_ram_size_bits(i915) /
> @@ -667,9 +666,6 @@ static u16 intel_dp_dsc_get_output_bpp(struct drm_i915_private *i915,
>  	if (bigjoiner)
>  		max_bpp_small_joiner_ram *= 2;
>  
> -	drm_dbg_kms(&i915->drm, "Max small joiner bpp: %u\n",
> -		    max_bpp_small_joiner_ram);
> -
>  	/*
>  	 * Greatest allowed DSC BPP = MIN (output BPP from available Link BW
>  	 * check, output bpp from small joiner RAM check)
> @@ -681,7 +677,6 @@ static u16 intel_dp_dsc_get_output_bpp(struct drm_i915_private *i915,
>  			i915->max_cdclk_freq * 48 /
>  			intel_dp_mode_to_fec_clock(mode_clock);
>  
> -		drm_dbg_kms(&i915->drm, "Max big joiner bpp: %u\n", max_bpp_bigjoiner);
>  		bits_per_pixel = min(bits_per_pixel, max_bpp_bigjoiner);
>  	}

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-06-07  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  7:44 [Intel-gfx] [PATCH] drm/i915: remove noisy logs in intel_dp_dsc_get_output_bpp() Luca Coelho
2022-06-07  8:05 ` Jani Nikula [this message]
2022-06-07  8:07   ` Luca Coelho
2022-06-07 11:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-07 14:22 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-06-07 19:10 ` [Intel-gfx] [PATCH] " Jani Nikula

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=871qw0rj99.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luca@coelho.fi \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox