From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Joonyoung Shim <dofmind@gmail.com>
Cc: inki.dae@samsung.com, intel-gfx@lists.freedesktop.org,
kyungmin.park@samsung.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: add plane support
Date: Thu, 21 Jul 2011 10:14:06 -0700 [thread overview]
Message-ID: <20110721101406.0d9dd4ee@jbarnes-desktop> (raw)
In-Reply-To: <CAPLVkLt5a5Te=ZkFgTBxP0Y6fVcQVi1igRE5jK3UnGMiAxmekQ@mail.gmail.com>
On Thu, 21 Jul 2011 19:30:00 +0900
Joonyoung Shim <dofmind@gmail.com> wrote:
> Hi,
>
> simple questions :)
>
> 2011/6/21 Jesse Barnes <jbarnes@virtuousgeek.org>:
> > Planes are a bit like half-CRTCs. They have a location and fb, but
> > don't drive outputs directly. Add support for handling them to the core
> > KMS code.
> >
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > ---
> > drivers/gpu/drm/drm_crtc.c | 235 +++++++++++++++++++++++++++++++++++++++++++-
> > drivers/gpu/drm/drm_drv.c | 3 +
> > include/drm/drm.h | 3 +
> > include/drm/drm_crtc.h | 73 ++++++++++++++-
> > include/drm/drm_mode.h | 35 +++++++
> > 5 files changed, 346 insertions(+), 3 deletions(-)
> >
>
> snip
>
> > diff --git a/include/drm/drm_mode.h b/include/drm/drm_mode.h
> > index c4961ea..fa6d348 100644
> > --- a/include/drm/drm_mode.h
> > +++ b/include/drm/drm_mode.h
> > @@ -120,6 +120,41 @@ struct drm_mode_crtc {
> > struct drm_mode_modeinfo mode;
> > };
> >
> > +/* Planes blend with or override other bits on the CRTC */
> > +struct drm_mode_set_plane {
> > + __u32 plane_id;
> > + __u32 crtc_id;
> > + __u32 fb_id; /* fb object contains surface format type */
> > +
> > + /* Signed dest location allows it to be partially off screen */
> > + __s32 crtc_x, crtc_y;
>
> Is this location offset from base(0, 0) of fb for plane, or from base
> of crtc(mode)?
This is the offset on the crtc specifically (which could be displaying
a nonzero offset of a given fb).
>
> > + __u32 crtc_w, crtc_h;
>
> What is it for? size of plane?
These are the size of the rect on the crtc. It's possible to have say
a small source fb that gets scaled to a different size on the crtc by
the plane blender or display hardware.
>
> > +
> > + /* Source values are 16.16 fixed point */
> > + __u32 src_x, src_y;
> > + __u32 src_h, src_w;
>
> What are these for?
These specify the offset and size of the rect used for the source
area. This allows the sprite hardware to send a subregion to the plane
blender for display on the crtc.
> > +
> > + __u32 zpos;
>
> Is this for order of plane(overlay)?
Yes.
Hope that helps; most of the above came out of earlier review comments
since some display hardware allows a lot of flexibility when displaying
overlay planes.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-07-21 17:14 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 [this message]
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
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=20110721101406.0d9dd4ee@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dofmind@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kyungmin.park@samsung.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).