From: Marcus Lorentzon <marcus.xm.lorentzon@stericsson.com>
To: Luc Verhaegen <libv@skynet.be>
Cc: "hoegsberg@gmail.com" <hoegsberg@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [RFC PATCH] drm: Add plane event
Date: Wed, 18 Apr 2012 18:00:38 +0200 [thread overview]
Message-ID: <4F8EE526.3020700@stericsson.com> (raw)
In-Reply-To: <20120418154325.GE15308@skynet.be>
On 04/18/2012 05:43 PM, Luc Verhaegen wrote:
> This means that there should be (at least) three separate actions:
> * page flipping: buffers -> planes at next vblank, for a list of
> buffer(s) and plane tuples.
> * setplanes: colour format, position, scaling, ordering, rotation, color
> key, crtc adherance,_plus_ the above.
> * actual modeset, which handles the CRTC and out to the monitor and
> whatnot, which should also include the above.
The setplanes is exactly the piece I'm missing today ... and it should
be async as flip.
/Marcus
next prev parent reply other threads:[~2012-04-18 16:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 4:31 [RFC PATCH] drm: Add plane event Joonyoung Shim
2012-04-18 8:46 ` Daniel Vetter
2012-04-18 10:11 ` Joonyoung Shim
2012-04-18 12:25 ` Rob Clark
2012-04-18 14:04 ` Marcus Lorentzon
2012-04-18 14:26 ` Ville Syrjälä
2012-04-18 14:36 ` Daniel Vetter
2012-04-18 15:10 ` Marcus Lorentzon
2012-04-18 15:27 ` Daniel Vetter
2012-04-18 15:55 ` Marcus Lorentzon
2012-04-18 16:04 ` Jesse Barnes
2012-04-18 19:08 ` Daniel Vetter
2012-04-18 16:06 ` Ville Syrjälä
2012-04-18 16:26 ` Marcus Lorentzon
2012-04-18 18:19 ` Ville Syrjälä
2012-04-19 8:10 ` Daniel Vetter
2012-04-18 15:43 ` Luc Verhaegen
2012-04-18 16:00 ` Marcus Lorentzon [this message]
2012-04-19 1:24 ` Kristian Høgsberg
2012-04-19 8:05 ` Daniel Vetter
2012-04-18 14:58 ` Marcus Lorentzon
2012-04-18 15:57 ` Jesse Barnes
2012-04-18 16:47 ` Luc Verhaegen
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=4F8EE526.3020700@stericsson.com \
--to=marcus.xm.lorentzon@stericsson.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@gmail.com \
--cc=libv@skynet.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.