From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm: Send pending vblank events before disabling vblank.
Date: Thu, 28 Apr 2011 13:42:26 -0700 [thread overview]
Message-ID: <20110428134226.21fe7627@jbarnes-desktop> (raw)
In-Reply-To: <1303893156.5633.126.camel@thor.local>
On Wed, 27 Apr 2011 10:32:36 +0200
Michel Dänzer <michel@daenzer.net> wrote:
> 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>
> >
> > This is the least-bad behaviour. It means that we signal the
> > vblank event before it actually happens, but since we're disabling
> > vblanks there's no guarantee that it will *ever* happen otherwise.
>
> This may indeed be the best we can do for events that are pending when
> the CRTC is disabled[0], but I can't see anything that would prevent new
> events from getting scheduled (or synchronous vblank waits from timing
> out) while the CRTC is disabled?
>
> [0] Though it might unnecessarily send events prematurely when the CRTC
> is just disabled temporarily, e.g. as part of a modeset.
We should return -EINVAL in that case from drm_wait_vblank due to
drm_vblank_get failing (i.e. the driver enable_vblank hook should fail
if the corresponding crtc is off). At least that's how it's supposed
to work.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-04-28 20:42 UTC|newest]
Thread overview: 22+ 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
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 [this message]
2011-04-28 20:34 ` Jesse Barnes
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=20110428134226.21fe7627@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.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