From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH] drm/i915/skl: Bypass debug message if scalers are not requested
Date: Wed, 5 Aug 2015 15:14:30 +0100 [thread overview]
Message-ID: <1438784070-7430-1-git-send-email-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
The loop below does nothing if scaler_users has no bits set so
it is safe to bail out early in order to avoid dmesg spam, on
for example cursor updates.
v2: Commit message and rebase.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Chandra Konduru <chandra.konduru@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
---
drivers/gpu/drm/i915/intel_atomic.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_atomic.c b/drivers/gpu/drm/i915/intel_atomic.c
index e2531cf59266..523afd21cf87 100644
--- a/drivers/gpu/drm/i915/intel_atomic.c
+++ b/drivers/gpu/drm/i915/intel_atomic.c
@@ -148,6 +148,10 @@ int intel_atomic_setup_scalers(struct drm_device *dev,
int num_scalers_need;
int i, j;
+
+ if (scaler_state->scaler_users == 0)
+ return 0;
+
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,
--
2.4.6
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-08-05 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 14:14 Tvrtko Ursulin [this message]
2015-08-12 5:49 ` [PATCH] drm/i915/skl: Bypass debug message if scalers are not requested shuang.he
-- strict thread matches above, loose matches on Subject: below --
2015-04-24 16:08 Tvrtko Ursulin
2015-04-24 16:30 ` Konduru, Chandra
2015-04-24 16:33 ` Tvrtko Ursulin
2015-04-24 17:52 ` Konduru, Chandra
2015-04-24 18:07 ` Konduru, Chandra
2015-05-04 14:29 ` Daniel Vetter
2015-08-05 13:20 ` Tvrtko Ursulin
2015-08-05 13:58 ` Daniel Vetter
2015-08-05 14:12 ` Tvrtko Ursulin
2015-08-05 14:19 ` Tvrtko Ursulin
2015-08-05 15:02 ` Tvrtko Ursulin
2015-04-28 8:24 ` shuang.he
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=1438784070-7430-1-git-send-email-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
/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