summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorPaul Rolland <rol@as2917.net>2009-08-09 12:24:01 +1000
committerDave Airlie <airlied@redhat.com>2009-08-09 12:24:01 +1000
commit8d3457ec3198a569dd14dc9e3ae8b6163bcaa0b5 (patch)
treeb05b1c0fe5392a2c70274b3ab279bf9d8c87a09f /drivers
parent38d5487db7f289be1d56ac7df704ee49ed3213b9 (diff)
downloadop-kernel-dev-8d3457ec3198a569dd14dc9e3ae8b6163bcaa0b5.zip
op-kernel-dev-8d3457ec3198a569dd14dc9e3ae8b6163bcaa0b5.tar.gz
drm: silence pointless vblank warning.
Some applications/hardware combinations are triggering the message "failed to acquire vblank counter" to be issued up to 20 times a second, which makes it both useless and dangerous, as this may hide other important messages. This changes makes it only appear when people are debugging. Signed-off-by: Paul Rolland <rol@as2917.net> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org> Lost-twice-by: Dave Airlie <airlied@redhat.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/gpu/drm/drm_irq.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index b4a3dbc..f85aaf2 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -566,7 +566,7 @@ int drm_wait_vblank(struct drm_device *dev, void *data,
ret = drm_vblank_get(dev, crtc);
if (ret) {
- DRM_ERROR("failed to acquire vblank counter, %d\n", ret);
+ DRM_DEBUG("failed to acquire vblank counter, %d\n", ret);
return ret;
}
seq = drm_vblank_count(dev, crtc);
OpenPOWER on IntegriCloud