From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Rob Clark <robdclark@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: add plane support
Date: Fri, 22 Jul 2011 08:30:11 -0700 [thread overview]
Message-ID: <20110722083011.73a6fe68@jbarnes-desktop> (raw)
In-Reply-To: <CAF6AEGuv8pT590gM+8LP2Wk-aP6ckN=6VGyQ3kDiZe=uHMYJtg@mail.gmail.com>
On Fri, 22 Jul 2011 08:52:52 -0500
Rob Clark <robdclark@gmail.com> wrote:
> On Mon, Jun 20, 2011 at 3:11 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > /**
> > + * drm_plane_funcs - driver plane control functions
> > + * @update_plane: update the plane configuration
> > + */
> > +struct drm_plane_funcs {
> > + int (*update_plane)(struct drm_plane *plane,
> > + struct drm_crtc *crtc, struct drm_framebuffer *fb,
> > + int crtc_x, int crtc_y,
> > + unsigned int crtc_w, unsigned int crtc_h,
> > + uint32_t src_x, uint32_t src_y,
> > + uint32_t src_w, uint32_t src_h);
> > + void (*disable_plane)(struct drm_plane *plane);
> > +};
> > +
>
>
> would it freak anyone out too much to ask about multi-planar formats?
> Ie. say you have an overlay that could display I420 w/ separate Y, U,
> & V addresses or NV12 w/ separate Y and UV addresses. Some of the
> SoC's out there require that chroma and luma is in different memory
> banks. In omap4xxx case we don't have this requirement, but we do
> have different tiling for Y and UV (NV12).
>
> Not something that directly affects this patchset.. I'm thinking more
> along the lines of having a way to create a drm_framebuffer w/ more
> than one GEM buffer, one per color plane. The other option is to bury
> this all behind a single GEM buffer.. although that seems like it
> could get ugly/hacky.
>
> Am I opening a can of worms here? ;-)
Yes. :)
Given the format constraints for planar, multi-buffer configs, it might
be best to expose those as driver specific ioctls. It's a big ugly to
have a driver specific addfb (only because we don't have one currently)
but should be doable for funkier things like this.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-07-22 15:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 20:11 [RFC] Updated plane support v3 Jesse Barnes
2011-06-20 20:11 ` [PATCH 1/4] drm: add plane support Jesse Barnes
2011-07-21 10:30 ` Joonyoung Shim
2011-07-21 17:14 ` Jesse Barnes
2011-07-25 8:18 ` Joonyoung Shim
2011-07-25 14:57 ` Rob Clark
2011-07-26 4:21 ` Joonyoung Shim
2011-07-22 13:52 ` Rob Clark
2011-07-22 15:30 ` Jesse Barnes [this message]
2011-07-22 15:57 ` Rob Clark
2011-07-22 22:18 ` Alan Cox
2011-06-20 20:11 ` [PATCH 2/4] drm: add an fb creation ioctl that takes a pixel format Jesse Barnes
2011-06-20 20:11 ` [PATCH 3/4] drm/i915: rename existing overlay support to "legacy" Jesse Barnes
2011-06-20 20:11 ` [PATCH 4/4] drm/i915: add SNB video sprite support Jesse Barnes
2011-06-21 8:55 ` [RFC] Updated plane support v3 Marcus Lorentzon
2011-06-21 9:12 ` Daniel Vetter
2011-06-21 16:13 ` Jesse Barnes
2011-06-21 11:21 ` Rob Clark
2011-06-21 13:16 ` Rob Clark
2011-06-21 16:19 ` Jesse Barnes
2011-06-22 1:09 ` Rob Clark
2011-09-19 8:03 ` Joonyoung Shim
-- strict thread matches above, loose matches on Subject: below --
2011-06-07 20:07 [RFC] Updated DRM plane handling patches Jesse Barnes
2011-06-07 20:07 ` [PATCH 1/4] drm: add plane support Jesse Barnes
2011-06-07 21:01 ` Jesse Barnes
2011-06-08 9:41 ` Marcus Lorentzon
2011-06-08 18:54 ` Jesse Barnes
2011-06-09 9:16 ` Marcus Lorentzon
2011-06-07 21:05 ` 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=20110722083011.73a6fe68@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=robdclark@gmail.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;
as well as URLs for NNTP newsgroup(s).