From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kernel@collabora.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] docs: uapi: media: Move NV12_10BE_8L128 to NV15 section
Date: Mon, 7 Aug 2023 13:28:05 +0200 [thread overview]
Message-ID: <fa3fd17d-570b-fd5f-1c35-3e4004333383@collabora.com> (raw)
In-Reply-To: <20230804192737.19016-3-nicolas.dufresne@collabora.com>
W dniu 4.08.2023 o 21:27, Nicolas Dufresne pisze:
> This is a 15 bits per pixel (or packed 10 bit format), so move it
> into the relevant section.
>
> Signed-off-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Reviewed-by: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
> ---
> .../media/v4l/pixfmt-yuv-planar.rst | 36 ++++++++++---------
> 1 file changed, 19 insertions(+), 17 deletions(-)
>
> diff --git a/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst b/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst
> index fb826923ff1d..1d43532095c0 100644
> --- a/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst
> +++ b/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst
> @@ -295,8 +295,6 @@ of the luma plane.
> .. _V4L2-PIX-FMT-NV12-32L32:
> .. _V4L2-PIX-FMT-NV12M-8L128:
> .. _V4L2-PIX-FMT-NV12-8L128:
> -.. _V4L2-PIX-FMT-NV12M-10BE-8L128:
> -.. _V4L2-PIX-FMT-NV12-10BE-8L128:
> .. _V4L2-PIX-FMT-MM21:
>
> Tiled NV12
> @@ -361,6 +359,25 @@ The layouts of the luma and chroma planes are identical.
> ``V4L2_PIX_FMT_NV12_8L128`` is similar to ``V4L2_PIX_FMT_NV12M_8L128`` but stores
> two planes in one memory.
>
> +``V4L2_PIX_FMT_MM21`` store luma pixel in 16x32 tiles, and chroma pixels
> +in 16x16 tiles. The line stride must be aligned to a multiple of 16 and the
> +image height must be aligned to a multiple of 32. The number of luma and chroma
> +tiles are identical, even though the tile size differ. The image is formed of
> +two non-contiguous planes.
> +
> +
> +.. _V4L2-PIX-FMT-NV15-4L4:
> +.. _V4L2-PIX-FMT-NV12M-10BE-8L128:
> +.. _V4L2-PIX-FMT-NV12-10BE-8L128:
> +
> +Tiled NV15
> +----------
> +
> +``V4L2_PIX_FMT_NV15_4L4`` Semi-planar 10-bit YUV 4:2:0 formats, using 4x4 tiling.
> +All components are packed without any padding between each other.
> +As a side-effect, each group of 4 components are stored over 5 bytes
> +(YYYY or UVUV = 4 * 10 bits = 40 bits = 5 bytes).
> +
> ``V4L2_PIX_FMT_NV12M_10BE_8L128`` is similar to ``V4L2_PIX_FMT_NV12M`` but stores
> 10 bits pixels in 2D 8x128 tiles, and stores tiles linearly in memory.
> the data is arranged in big endian order.
> @@ -379,21 +396,6 @@ byte 4: Y3(bits 7-0)
> ``V4L2_PIX_FMT_NV12_10BE_8L128`` is similar to ``V4L2_PIX_FMT_NV12M_10BE_8L128`` but stores
> two planes in one memory.
>
> -``V4L2_PIX_FMT_MM21`` store luma pixel in 16x32 tiles, and chroma pixels
> -in 16x16 tiles. The line stride must be aligned to a multiple of 16 and the
> -image height must be aligned to a multiple of 32. The number of luma and chroma
> -tiles are identical, even though the tile size differ. The image is formed of
> -two non-contiguous planes.
> -
> -.. _V4L2-PIX-FMT-NV15-4L4:
> -
> -Tiled NV15
> -----------
> -
> -Semi-planar 10-bit YUV 4:2:0 formats, using 4x4 tiling.
> -All components are packed without any padding between each other.
> -As a side-effect, each group of 4 components are stored over 5 bytes
> -(YYYY or UVUV = 4 * 10 bits = 40 bits = 5 bytes).
>
> .. _V4L2-PIX-FMT-NV16:
> .. _V4L2-PIX-FMT-NV61:
next prev parent reply other threads:[~2023-08-07 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230804192737.19016-1-nicolas.dufresne@collabora.com>
2023-08-04 19:27 ` [PATCH 1/5] docs: uapi: media: Properly locate NV12MT diagram Nicolas Dufresne
2023-08-07 11:22 ` Andrzej Pietrasiewicz
2023-08-04 19:27 ` [PATCH 2/5] docs: uapi: media: Move NV12_10BE_8L128 to NV15 section Nicolas Dufresne
2023-08-07 11:28 ` Andrzej Pietrasiewicz [this message]
2023-08-04 19:27 ` [PATCH 3/5] docs: uapi: media: Add common documentation of tiled NV15 Nicolas Dufresne
2023-08-07 11:37 ` Andrzej Pietrasiewicz
2023-09-13 18:11 ` Nicolas Dufresne
2023-08-04 19:27 ` [PATCH 4/5] docs: uapi: media: Add a layout diagram for MT2110T Nicolas Dufresne
2023-08-07 18:40 ` Andrzej Pietrasiewicz
2023-08-07 19:29 ` Nicolas Dufresne
2023-08-07 21:24 ` Nicolas Dufresne
2023-08-08 11:46 ` Andrzej Pietrasiewicz
2023-08-04 19:27 ` [PATCH 5/5] docs: uapi: media: Document Mediatek 10bit tiled formats Nicolas Dufresne
2023-08-07 18:35 ` Andrzej Pietrasiewicz
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=fa3fd17d-570b-fd5f-1c35-3e4004333383@collabora.com \
--to=andrzej.p@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.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®