From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Seung-Woo Kim <sw0312.kim@samsung.com>,
dri-devel@lists.freedesktop.org, Inki Dae <inki.dae@samsung.com>,
kyungmin.park@samsung.com, airlied@redhat.com
Subject: Re: [PATCH libdrm] libdrm: update drm/drm_fourcc.h from kernel to add multi plane formats
Date: Fri, 06 Apr 2012 13:22:06 +0200 [thread overview]
Message-ID: <4F7ED1DE.7040608@samsung.com> (raw)
In-Reply-To: <CAH9JG2XArT-kTOAefdn=jTvUD7-hb-UaBkN2TF5tsjG=EA1XtA@mail.gmail.com>
Hello,
On 04/06/2012 11:22 AM, Kyungmin Park wrote:
> + V4L2 develper
> Sylwester, please give your opinions? How to handle it at v4l2 side.
>
> Thank you,
> Kyungmin Park
>
> On Apr 6, 2012 12:44 AM, "Ville Syrjälä" <syrjala@sci.fi
> <mailto:syrjala@sci.fi>> wrote:
>
> On Fri, Apr 06, 2012 at 03:05:36PM +0900, Inki Dae wrote:
> > Hi Ville,
> >
> > > -----Original Message-----
> > > From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com
> <mailto:ville.syrjala@linux.intel.com>]
> > > Sent: Friday, April 06, 2012 3:14 AM
> > > To: airlied@redhat.com <mailto:airlied@redhat.com>
> > > Cc: inki.dae@samsung.com <mailto:inki.dae@samsung.com>;
> kyungmin.park@samsung.com <mailto:kyungmin.park@samsung.com>; dri-
> > > devel@lists.freedesktop.org <mailto:devel@lists.freedesktop.org>;
> Seung-Woo Kim
> > > Subject: Re: [PATCH libdrm] libdrm: update drm/drm_fourcc.h from kernel to
> > > add multi plane formats
> > >
> > > On Fri, Mar 30, 2012 at 01:12:58PM +0300, Ville Syrjälä wrote:
> > > > On Fri, Mar 30, 2012 at 11:54:50AM +0900, Seung-Woo Kim wrote:
> > > > > Multi buffer plane pixel formats are added as like kernel header.
> > > > >
> > > > > Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com
> <mailto:sw0312.kim@samsung.com>>
> > > > > ---
> > > > > include/drm/drm_fourcc.h | 7 +++++++
> > > > > 1 files changed, 7 insertions(+), 0 deletions(-)
> > > > >
> > > > > diff --git a/include/drm/drm_fourcc.h b/include/drm/drm_fourcc.h
> > > > > index 85facb0..7cfd95a 100644
> > > > > --- a/include/drm/drm_fourcc.h
> > > > > +++ b/include/drm/drm_fourcc.h
> > > > > @@ -107,6 +107,10 @@
> > > > > #define DRM_FORMAT_NV16 fourcc_code('N', 'V', '1',
> '6') /*
> > > 2x1 subsampled Cr:Cb plane */
> > > > > #define DRM_FORMAT_NV61 fourcc_code('N', 'V', '6',
> '1') /*
> > > 2x1 subsampled Cb:Cr plane */
> > > > >
> > > > > +/* 2 non contiguous plane YCbCr */
> > > > > +#define DRM_FORMAT_NV12M fourcc_code('N', 'M', '1', '2') /* 2x2
> > > subsampled Cr:Cb plane */
> > > >
> > > > NAK. DRM_FORMAT_NV12 handles this just fine.
> > >
> > > And I just realized that I was already too late with my NAK since this a
> > > libdrm patch. Apparently the kernel drm_fourcc.h changes were snuck in
> > > via some backdoor without review. Sigh.
> > >
> >
> > We had already requested review for it. for this you can refer to link
> > below:
> >
> > http://lists.freedesktop.org/archives/dri-devel/2011-December/017654.html
>
> I see. I couldn't find it in my work mailbox for some reason, and I
> don't remember having seen the patch before. I suppose I just missed it
> due to Christmas vacations, and was too blind to see it in my mailbox.
> Also google decicded to filter my search results too much, so I didn't
> spot it via the web archives either. I'm sorry for the false accusation.
>
> > > So they're now in Linus's tree. But looks like format_check() was never
> > > updated to accept them, so there's no way anyone could actually be using
> > > them. So Dave, can we still remove them from the kernel header?
> > >
> >
> > Yes, right. these formats aren't used for any SoCs except Exynos series yet
> > but just we are first. I think they should be added because anyone may use
> > them someday at least possible.
>
> Since DRM_FORMAT_NV12M is _identical_ to DRM_FORMAT_NV12, I see no point
> in adding it (similarly for YUV420M vs. YUV420).
In V4L2 the fourcc also determines the number of memory planes in the frame
buffer. The multi-planar API has been added to support devices with odd
alignment requirements (image components, like Y/CbCr in separate physical
memory buffers) for which it was difficult to map whole frame into contiguous
user memory region.
Here is some excample:
http://linuxtv.org/downloads/v4l-dvb-apis/V4L2-PIX-FMT-NV12M.html
I'm not terribly familiar with the buffer structure in DRM, maybe there are
better ways to handle something like this in DRI.
> --
> Ville Syrjälä
> syrjala@sci.fi <mailto:syrjala@sci.fi>
> http://www.sci.fi/~syrjala/
Regards,
--
Sylwester Nawrocki
Samsung Poland R&D Center
next prev parent reply other threads:[~2012-04-06 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 2:54 [PATCH libdrm] libdrm: update drm/drm_fourcc.h from kernel to add multi plane formats Seung-Woo Kim
2012-03-30 10:12 ` Ville Syrjälä
2012-03-30 11:07 ` 김승우
2012-03-30 12:13 ` Ville Syrjälä
2012-03-30 11:09 ` Marcus Lorentzon
2012-04-06 20:04 ` Sylwester Nawrocki
2012-04-05 18:13 ` Ville Syrjälä
2012-04-06 0:13 ` Rob Clark
2012-04-06 6:05 ` Inki Dae
2012-04-06 7:43 ` Ville Syrjälä
2012-04-06 9:22 ` Kyungmin Park
2012-04-06 11:22 ` Sylwester Nawrocki [this message]
2012-04-07 6:01 ` daeinki
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=4F7ED1DE.7040608@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=kmpark@infradead.org \
--cc=kyungmin.park@samsung.com \
--cc=sw0312.kim@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 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.