From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: remove excessive scaler debugging messages
Date: Mon, 7 Sep 2015 11:17:01 +0100 [thread overview]
Message-ID: <55ED641D.3020905@linux.intel.com> (raw)
In-Reply-To: <1439557193-27461-1-git-send-email-jani.nikula@intel.com>
On 08/14/2015 01:59 PM, Jani Nikula wrote:
> There's so much scaler debugging messages that it makes other debugging
> hard. Remove them.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/intel_atomic.c | 3 ---
> drivers/gpu/drm/i915/intel_display.c | 2 --
> 2 files changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_atomic.c b/drivers/gpu/drm/i915/intel_atomic.c
> index e2531cf59266..9336e8030980 100644
> --- a/drivers/gpu/drm/i915/intel_atomic.c
> +++ b/drivers/gpu/drm/i915/intel_atomic.c
> @@ -149,9 +149,6 @@ int intel_atomic_setup_scalers(struct drm_device *dev,
> int i, j;
>
> num_scalers_need = hweight32(scaler_state->scaler_users);
> - DRM_DEBUG_KMS("crtc_state = %p need = %d avail = %d scaler_users = 0x%x\n",
> - crtc_state, num_scalers_need, intel_crtc->num_scalers,
> - scaler_state->scaler_users);
>
> /*
> * High level flow:
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 21aa745caed1..52720ff9f769 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2935,8 +2935,6 @@ static void skl_detach_scaler(struct intel_crtc *intel_crtc, int id)
> I915_WRITE(SKL_PS_CTRL(intel_crtc->pipe, id), 0);
> I915_WRITE(SKL_PS_WIN_POS(intel_crtc->pipe, id), 0);
> I915_WRITE(SKL_PS_WIN_SZ(intel_crtc->pipe, id), 0);
> - DRM_DEBUG_KMS("CRTC:%d Disabled scaler id %u.%u\n",
> - intel_crtc->base.base.id, intel_crtc->pipe, id);
> }
I had some patches for this, especially "[PATCH] drm/i915/skl: Only
disable scalers once" which I couldn't test properly due lack of
hardware. And "[PATCH] drm/i915/skl: Bypass debug message if scalers are
not requested", which only silences the case when scalers are not in
use, so yours may even be better.
But for the former, I think someone who knows this code should look at
my patch. To me it looks warranted to skip disabling scalers if they are
already disabled, rather than just kill the debug message.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-09-07 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 12:59 [PATCH] drm/i915: remove excessive scaler debugging messages Jani Nikula
2015-08-14 13:16 ` Daniel Vetter
2015-08-16 16:14 ` shuang.he
2015-09-07 10:17 ` Tvrtko Ursulin [this message]
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=55ED641D.3020905@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox