From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Randy Li" <ayaka@soulik.info>
Cc: dri-devel@lists.freedesktop.org, airlied@linux.ie,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] drm/fourcc: add a 10bits fully packed variant of NV12
Date: Mon, 21 May 2018 12:28:47 -0400 [thread overview]
Message-ID: <6ace60b7da86e14b089bf2f5e8162288e1223ea5.camel@collabora.com> (raw)
In-Reply-To: <20180521144948.GF23723@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3347 bytes --]
Le lundi 21 mai 2018 à 17:49 +0300, Ville Syrjälä a écrit :
> On Mon, May 21, 2018 at 01:17:04AM +0800, Randy Li wrote:
> > This pixel format is a fully packed and 10bits variant of NV12.
> > A luma pixel would take 10bits in memory, without any
> > filled bits between pixels in a stride. The color gamut
> > follows the BT.2020 standard.
> >
> > Signed-off-by: Randy Li <ayaka@soulik.info>
> > ---
> > drivers/gpu/drm/drm_fourcc.c | 1 +
> > include/uapi/drm/drm_fourcc.h | 3 +++
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/drm_fourcc.c
> > b/drivers/gpu/drm/drm_fourcc.c
> > index 5ca6395cd4d3..1f43967c4013 100644
> > --- a/drivers/gpu/drm/drm_fourcc.c
> > +++ b/drivers/gpu/drm/drm_fourcc.c
> > @@ -173,6 +173,7 @@ const struct drm_format_info
> > *__drm_format_info(u32 format)
> > { .format = DRM_FORMAT_UYVY, .depth
> > = 0, .num_planes = 1, .cpp = { 2, 0, 0 }, .hsub = 2, .vsub = 1 },
> > { .format = DRM_FORMAT_VYUY, .depth
> > = 0, .num_planes = 1, .cpp = { 2, 0, 0 }, .hsub = 2, .vsub = 1 },
> > { .format = DRM_FORMAT_AYUV, .depth
> > = 0, .num_planes = 1, .cpp = { 4, 0, 0 }, .hsub = 1, .vsub = 1,
> > .has_alpha = true },
> > + { .format = DRM_FORMAT_NV12_10LE40, .depth
> > = 0, .num_planes = 2, .cpp = { 1, 2, 0 }, .hsub = 2, .vsub = 2 },
> > };
> >
> > unsigned int i;
> > diff --git a/include/uapi/drm/drm_fourcc.h
> > b/include/uapi/drm/drm_fourcc.h
> > index e04613d30a13..8eabf01e966f 100644
> > --- a/include/uapi/drm/drm_fourcc.h
> > +++ b/include/uapi/drm/drm_fourcc.h
> > @@ -140,6 +140,9 @@ extern "C" {
> > #define DRM_FORMAT_NV61 fourcc_code('N', 'V', '6',
> > '1') /* 2x1 subsampled Cb:Cr plane */
> > #define DRM_FORMAT_NV24 fourcc_code('N', 'V', '2',
> > '4') /* non-subsampled Cr:Cb plane */
> > #define DRM_FORMAT_NV42 fourcc_code('N', 'V', '4',
> > '2') /* non-subsampled Cb:Cr plane */
> > +/* A fully packed variant of NV12_10LE32 */
>
> What does "fully packed" mean? NV12_10LE32 doesn't even exist so
> referring to it makes no sense.
Fully packed means no padding bits at all, that's quite descriptive.
There is generally only one way to achieve this for a given layout and
format. Referring to NV12_10LE32 GStreamer format isn't very useful,
that I agree. I think Xilinx is submitting it as XV10.
In GStreamer, all the 10bit format naming started to be a mess, so I
encoded something, it's probably not great, but does the job. So when
we say NV12, it mean the YUV 4:2:0 with two planes, 10, means 10bit per
component, LE, for littlen endian, and 40 for 40bit packing length. If
you pack 10bit data over 40bit, you have basically 4 component per 5
bytes.
Unlike XV10 (aka NV12_10LE32), where you have 3 component per 4 bytes,
each 32bit have 3 components, and 2bit are ignored (padding).
>
> Please try to provide an unambiguous description of new formats like
> we
> have for everything else.
>
> > +#define DRM_FORMAT_NV12_10LE40 fourcc_code('R', 'K', '2',
> > '0') /* 2x2 subsampled Cr:Cb plane */
> > +
> >
> > /*
> > * 3 plane YCbCr
> > --
> > 2.14.3
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-05-21 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 17:17 [PATCH 0/2] Add support for a YUV 10bits pixel format Randy Li
2018-05-20 17:17 ` [PATCH 1/2] drm/fourcc: add a 10bits fully packed variant of NV12 Randy Li
2018-05-21 14:49 ` Ville Syrjälä
2018-05-21 16:28 ` Nicolas Dufresne [this message]
2018-05-22 9:12 ` Maarten Lankhorst
2018-05-22 9:26 ` Maarten Lankhorst
2018-05-22 9:49 ` Randy Li
2018-05-20 17:17 ` [PATCH 2/2] drm/rockchip: Support 10 bits yuv format in vop Randy Li
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=6ace60b7da86e14b089bf2f5e8162288e1223ea5.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=airlied@linux.ie \
--cc=ayaka@soulik.info \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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
all inboxes | Powered by JetHome®