From: "Michel Dänzer" <michel@daenzer.net>
To: christopher.halse.rogers@canonical.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm: Warn if vblank state has become inconsistent.
Date: Wed, 27 Apr 2011 10:38:14 +0200 [thread overview]
Message-ID: <1303893494.5633.129.camel@thor.local> (raw)
In-Reply-To: <1303884659-739-2-git-send-email-christopher.halse.rogers@canonical.com>
On Mit, 2011-04-27 at 16:10 +1000, christopher.halse.rogers@canonical.com wrote:
> From: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com>
>
> After emitting all the waiting vblank events no-one should hold
> a vblank reference. Emit a warning if this is not the case.
>
> Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com>
> ---
> drivers/gpu/drm/drm_irq.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
> index a1f12cb..72407fa 100644
> --- a/drivers/gpu/drm/drm_irq.c
> +++ b/drivers/gpu/drm/drm_irq.c
> @@ -960,6 +960,7 @@ void drm_vblank_off(struct drm_device *dev, int crtc)
> e->event.sequence);
> }
>
> + WARN_ON(atomic_read(&dev->vblank_refcount[crtc]) != 0);
> spin_unlock_irqrestore(&dev->vbl_lock, irqflags);
> }
> EXPORT_SYMBOL(drm_vblank_off);
Reviewed-by: Michel Dänzer <michel@daenzer.net>
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-04-27 8:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 6:10 [PATCH 1/3] drm: Send pending vblank events before disabling vblank christopher.halse.rogers
2011-04-27 6:10 ` [PATCH 2/3] drm: Warn if vblank state has become inconsistent christopher.halse.rogers
2011-04-27 8:38 ` Michel Dänzer [this message]
2011-04-27 6:10 ` [PATCH 3/3] drm: Factor-out drm_emit_vblank_event code christopher.halse.rogers
2011-04-27 8:36 ` Michel Dänzer
2011-04-27 8:48 ` Christopher James Halse Rogers
2011-04-27 9:06 ` Michel Dänzer
2011-04-28 20:36 ` Jesse Barnes
2011-04-29 3:57 ` [PATCH] drm: Factor-out drm_emit_vblank_event code. (v2) christopher.halse.rogers
2011-04-29 6:43 ` Michel Dänzer
2011-04-29 15:55 ` Marcin Slusarz
2011-05-01 23:55 ` Christopher James Halse Rogers
2011-05-02 0:09 ` [PATCH] drm: Factor-out drm_emit_vblank_event code. (v3) christopher.halse.rogers
2011-04-27 8:32 ` [PATCH 1/3] drm: Send pending vblank events before disabling vblank Michel Dänzer
2011-04-27 8:58 ` Christopher James Halse Rogers
2011-04-27 9:08 ` Michel Dänzer
2011-04-27 9:17 ` Christopher James Halse Rogers
2011-04-28 8:09 ` Christopher James Halse Rogers
2011-04-28 20:46 ` Jesse Barnes
2011-04-28 20:53 ` Jesse Barnes
2011-04-28 20:42 ` Jesse Barnes
2011-04-28 20:34 ` Jesse Barnes
[not found] <mailman.30.1303894729.31758.dri-devel@lists.freedesktop.org>
2011-04-27 15:50 ` [PATCH 2/3] drm: Warn if vblank state has become inconsistent Mario Kleiner
2011-04-28 7:47 ` Christopher James Halse Rogers
2011-04-28 16:40 ` Mario Kleiner
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=1303893494.5633.129.camel@thor.local \
--to=michel@daenzer.net \
--cc=christopher.halse.rogers@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
/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