From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Make scaler updates less chatty
Date: Thu, 17 Nov 2016 11:06:23 -0200 [thread overview]
Message-ID: <1479387983.2382.14.camel@intel.com> (raw)
In-Reply-To: <1479376805-5087-1-git-send-email-tvrtko.ursulin@linux.intel.com>
Em Qui, 2016-11-17 às 10:00 +0000, Tvrtko Ursulin escreveu:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> It looks to me skl_update_scaler will already log interesting
> debug messages when the state transitions or there is an error.
>
> In this case it feels we can remove the two unconditional
> debug messages which happen immediately before calling
> skl_update_scaler. This way we get rid of the sole debug
> message when switching virtual terminals for example.
I also got annoyed by this at some point.
Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 2ebb8b833395..cd5256c0b2d6 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -4727,13 +4727,8 @@ skl_update_scaler(struct intel_crtc_state
> *crtc_state, bool force_detach,
> */
> int skl_update_scaler_crtc(struct intel_crtc_state *state)
> {
> - struct intel_crtc *intel_crtc = to_intel_crtc(state-
> >base.crtc);
> const struct drm_display_mode *adjusted_mode = &state-
> >base.adjusted_mode;
>
> - DRM_DEBUG_KMS("Updating scaler for [CRTC:%d:%s] scaler_user
> index %u.%u\n",
> - intel_crtc->base.base.id, intel_crtc-
> >base.name,
> - intel_crtc->pipe, SKL_CRTC_INDEX);
> -
> return skl_update_scaler(state, !state->base.active,
> SKL_CRTC_INDEX,
> &state->scaler_state.scaler_id, DRM_ROTATE_0,
> state->pipe_src_w, state->pipe_src_h,
> @@ -4754,7 +4749,6 @@ static int skl_update_scaler_plane(struct
> intel_crtc_state *crtc_state,
> struct intel_plane_state
> *plane_state)
> {
>
> - struct intel_crtc *intel_crtc = to_intel_crtc(crtc_state-
> >base.crtc);
> struct intel_plane *intel_plane =
> to_intel_plane(plane_state->base.plane);
> struct drm_framebuffer *fb = plane_state->base.fb;
> @@ -4762,10 +4756,6 @@ static int skl_update_scaler_plane(struct
> intel_crtc_state *crtc_state,
>
> bool force_detach = !fb || !plane_state->base.visible;
>
> - DRM_DEBUG_KMS("Updating scaler for [PLANE:%d:%s] scaler_user
> index %u.%u\n",
> - intel_plane->base.base.id, intel_plane-
> >base.name,
> - intel_crtc->pipe,
> drm_plane_index(&intel_plane->base));
> -
> ret = skl_update_scaler(crtc_state, force_detach,
> drm_plane_index(&intel_plane->base),
> &plane_state->scaler_id,
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-17 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 10:00 [PATCH] drm/i915: Make scaler updates less chatty Tvrtko Ursulin
2016-11-17 11:45 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-11-17 14:04 ` Tvrtko Ursulin
2016-11-17 13:06 ` Paulo Zanoni [this message]
2016-11-17 14:01 ` [PATCH] " Maarten Lankhorst
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=1479387983.2382.14.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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;
as well as URLs for NNTP newsgroup(s).