From: Damien Lespiau <damien.lespiau@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Erik Gilling <konkers@google.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Linaro-mm-sig] [RFC 0/4] Atomic Display Framework
Date: Thu, 29 Aug 2013 09:52:56 +0100 [thread overview]
Message-ID: <20130829085256.GA10489@strange.amr.corp.intel.com> (raw)
In-Reply-To: <20130829075851.GE11428@intel.com>
On Thu, Aug 29, 2013 at 10:58:51AM +0300, Ville Syrjälä wrote:
> After that we need to figure out how we can expose them to userspace w/o
> risking breaking stuff too much. Maybe a new ioctl to enumerate private
> planes only? And the maybe only accept direct use of private planes via
> the atomic API, not through the old setplane API. Or if people want to
> use setplane we could add a flag there indicating that the user is aware
> of private planes and wants to use them.
FWIW, in my yet to be published new stereo 3D series, I added a
DRM_SET_CAP ioctl for userspace to tell DRM to expose some stereo bits
in the mode structure.
Making it possible for the primary plane to be exposed as a drm_plane
could be the second user of this ioctl (well, assuming people are fine
with this new ioctl, a whole different story, but now that'd be 2 users
of it).
--
Damien
next prev parent reply other threads:[~2013-08-29 8:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 1:51 [RFC 0/4] Atomic Display Framework Greg Hackmann
2013-08-29 1:51 ` [RFC 1/4] video: Add generic display entity core Greg Hackmann
2013-08-29 1:51 ` [RFC 2/4] video: add atomic display framework Greg Hackmann
2013-08-29 1:51 ` [RFC 3/4] video: adf: add display core helper Greg Hackmann
2013-08-29 1:51 ` [RFC 4/4] video: adf: add memblock helper Greg Hackmann
2013-08-29 3:51 ` [RFC 0/4] Atomic Display Framework Rob Clark
2013-08-29 7:01 ` [Linaro-mm-sig] " Daniel Vetter
2013-08-29 7:58 ` Ville Syrjälä
2013-08-29 8:52 ` Damien Lespiau [this message]
2013-08-29 12:59 ` Rob Clark
2013-08-29 12:25 ` Rob Clark
2013-08-29 7:36 ` Ville Syrjälä
2013-08-29 12:54 ` Rob Clark
2013-08-29 23:34 ` Greg Hackmann
2013-08-30 14:00 ` Rob Clark
2013-08-30 14:11 ` Ville Syrjälä
2013-09-02 7:39 ` Daniel Vetter
2013-09-02 13:19 ` Rob Clark
2013-09-02 15:26 ` Alex Deucher
2013-08-29 23:26 ` Greg Hackmann
2013-08-30 13:55 ` Rob Clark
2013-08-30 14:01 ` Ville Syrjälä
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=20130829085256.GA10489@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=konkers@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox