From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rob Clark <rob@ti.com>
Cc: daniel.vetter@ffwll.ch, Ben Widawsky <ben@bwidawsk.net>,
dri-devel@lists.freedesktop.org, patches@linaro.org
Subject: Re: [RFC 0/9] nuclear pageflip
Date: Wed, 12 Sep 2012 11:59:27 +0300 [thread overview]
Message-ID: <20120912085927.GA9227@intel.com> (raw)
In-Reply-To: <CAF6AEGvvK6JZNm1eKKtixva=d3wqaExkJtBW7SG_3rfvWk+qLQ@mail.gmail.com>
On Tue, Sep 11, 2012 at 05:07:49PM -0500, Rob Clark wrote:
> On Tue, Sep 11, 2012 at 4:15 PM, Ben Widawsky <ben@bwidawsk.net> wrote:
> > On Sun, 9 Sep 2012 22:19:59 -0500
> > Rob Clark <rob@ti.com> wrote:
> >
> >> On Sun, Sep 9, 2012 at 10:03 PM, Rob Clark <rob.clark@linaro.org> wrote:
> >> > From: Rob Clark <rob@ti.com>
> >> >
> >> > This is following a bit the approach that Ville is taking for atomic-
> >> > modeset, in that it is switching over to using properties for everything.
> >> > The advantage of this approach is that it makes it easier to add new
> >> > attributes to set as part of a page-flip (and even opens the option to
> >> > add new object types).
> >>
> >> oh, and for those wondering what the hell this is all about,
> >> nuclear-pageflip is a pageflip that atomically updates the CRTC layer
> >> and zero or more attached plane layers, optionally changing various
> >> properties such as z-order (or even blending modes, etc) atomically.
> >> It includes the option for a test step so userspace compositor can
> >> test a proposed configuration (if any properties not marked as
> >> 'dynamic' are updated). This intended to allow, for example, weston
> >> compositor to synchronize updates to plane (sprite) layers with CRTC
> >> layer.
> >>
> >
> > Can we please name this something different? I complained about this in
> > IRC, but I don't know if you hang around in #intel-gfx.
> >
> > Some suggestions:
> > multiplane pageflip
> > muliplane atomic pageflip
> > atomic multiplane pageflip
> > atomic multiflip
> > pageflip of atomic and multiplane nature
> >
> > Nuclear is not at all descriptive and requires as your response shows
> > :-)
> >
>
> fair enough.. I was originally calling it atomic-pageflip until
> someone (I don't remember who) started calling it nuclear-pageflip to
> differentiate from atomic-modeset. But IMO we could just call the two
> ioclts atomic-modeset and atomic-pageflip. (Or even modeset2 and
> pageflip2, but that seems much more boring)
My plan has been to use the same ioctl for both uses. They'll need
nearly identical handling anyway on the ioctl level. I have something
semi-working currently, but I need to clean it up a bit before I can
show it to anyone.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2012-09-12 8:59 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 3:03 [RFC 0/9] nuclear pageflip Rob Clark
2012-09-10 3:03 ` [RFC 1/9] drm: add atomic fxns Rob Clark
2012-09-12 16:57 ` Jesse Barnes
2012-09-12 17:35 ` Rob Clark
2012-09-12 18:03 ` Ville Syrjälä
2012-09-12 18:34 ` Rob Clark
2012-09-12 19:05 ` Jesse Barnes
2012-09-12 19:57 ` Rob Clark
2012-09-10 3:03 ` [RFC 2/9] drm: add object property type Rob Clark
2012-09-10 3:03 ` [RFC 3/9] drm: add DRM_MODE_PROP_DYNAMIC property flag Rob Clark
2012-09-10 3:03 ` [RFC 4/9] drm: convert plane to properties Rob Clark
2012-09-10 3:03 ` [RFC 5/9] drm: add drm_plane_state Rob Clark
2012-09-10 3:03 ` [RFC 6/9] drm: convert page_flip to properties Rob Clark
2012-09-10 3:03 ` [RFC 7/9] drm: add drm_crtc_state Rob Clark
2012-09-10 3:03 ` [RFC 8/9] drm: nuclear pageflip Rob Clark
2012-09-10 3:03 ` [RFC 9/9] drm/omap: update for atomic age Rob Clark
2012-09-10 3:19 ` [RFC 0/9] nuclear pageflip Rob Clark
2012-09-11 21:15 ` Ben Widawsky
2012-09-11 22:07 ` Rob Clark
2012-09-12 8:59 ` Ville Syrjälä [this message]
2012-09-12 12:30 ` Rob Clark
2012-09-12 14:23 ` Ville Syrjälä
2012-09-12 14:28 ` Rob Clark
2012-09-12 14:34 ` Ville Syrjälä
2012-09-12 14:42 ` Rob Clark
2012-09-12 15:12 ` Ville Syrjälä
2012-09-12 15:23 ` Rob Clark
2012-09-12 15:32 ` Ville Syrjälä
2012-09-12 15:48 ` Rob Clark
2012-09-12 17:27 ` Ville Syrjälä
2012-09-12 18:00 ` Clark, Rob
2012-09-12 18:58 ` Ville Syrjälä
2012-09-12 19:40 ` Rob Clark
2012-09-13 8:40 ` Ville Syrjälä
2012-09-13 13:39 ` Rob Clark
2012-09-13 14:29 ` Ville Syrjälä
2012-09-13 16:35 ` Rob Clark
2012-09-14 12:50 ` Ville Syrjälä
2012-09-14 13:25 ` Rob Clark
2012-09-14 13:58 ` Ville Syrjälä
2012-09-14 14:45 ` Rob Clark
2012-09-14 15:48 ` Ville Syrjälä
2012-09-14 16:29 ` Rob Clark
2012-09-14 17:02 ` Ville Syrjälä
2012-09-14 17:34 ` Rob Clark
2012-09-14 18:23 ` Ville Syrjälä
2012-09-14 21:51 ` Rob Clark
2012-09-15 2:12 ` Rob Clark
2012-09-15 14:56 ` Ville Syrjälä
2012-09-15 16:07 ` Rob Clark
2012-09-15 17:04 ` Ville Syrjälä
2012-09-15 17:15 ` Rob Clark
2012-09-15 19:08 ` Ville Syrjälä
2012-09-15 20:16 ` Rob Clark
2012-09-14 21:14 ` Jesse Barnes
2012-09-14 21:42 ` Rob Clark
2012-09-14 21:46 ` Kristian Høgsberg
2012-09-15 14:53 ` Ville Syrjälä
2012-09-15 16:05 ` Rob Clark
2012-09-15 18:00 ` Ville Syrjälä
2012-09-15 20:10 ` 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=20120912085927.GA9227@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=patches@linaro.org \
--cc=rob@ti.com \
/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.