From: Archit Taneja <archit@ti.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Synchronization between a crtc mode_set and page_flip?
Date: Wed, 2 Apr 2014 15:22:47 +0530 [thread overview]
Message-ID: <533BDDEF.1050900@ti.com> (raw)
Hi,
I was trying to figure out how we are supposed to manage synchronization
between a mode_set and a page_flip called on a crtc.
Say, if a mode_set is immediately followed by a page_flip. The driver
can't process the page_flip straight away since the hardware is still
completing the mode_set.
What is the driver supposed to do? Should it return -EBUSY? Or should it
somehow queue the page_flip task internally?
A lot of libdrm applications seem to call mode_set, and call a page_flip
soon after it. They tend to bail out if page_flip returns an error, they
don't try to do another page_flip if it fails the first time. Is this
okay behaviour?
Thanks,
Archit
next reply other threads:[~2014-04-02 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 9:52 Archit Taneja [this message]
2014-04-02 13:11 ` Synchronization between a crtc mode_set and page_flip? Rob Clark
2014-04-03 8:58 ` Archit Taneja
2014-04-03 21:24 ` Daniel Vetter
2014-04-04 7:21 ` Archit Taneja
2014-04-04 11:54 ` Rob Clark
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=533BDDEF.1050900@ti.com \
--to=archit@ti.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