From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jeffrey Mouroux <jeff.mouroux@xilinx.com>
Cc: mchehab@kernel.org, hansverk@cisco.com,
laurent.pinchart+renesas@ideasonboard.com,
sakari.ailus@linux.intel.com, tiffany.lin@mediatek.com,
ricardo.ribalda@gmail.com, evgeni.raikhel@intel.com,
nick@shmanahar.org, linux-media@vger.kernel.org,
Jeffrey Mouroux <jmouroux@xilinx.com>
Subject: Re: [PATCH v1 1/2] uapi: media: New fourcc codes needed by Xilinx Video IP
Date: Wed, 09 Aug 2017 10:53:37 +0300 [thread overview]
Message-ID: <5292400.sDssS5K49F@avalon> (raw)
In-Reply-To: <1502242278-14686-2-git-send-email-jmouroux@xilinx.com>
Hi Jeffrey,
Thank you for the patch.
On Tuesday 08 Aug 2017 18:31:17 Jeffrey Mouroux wrote:
> The Xilinx Video Mixer andn Xilinx Video Framebuffer DMA IP
> support video memory formats that are not represented in the
> current V4L2 fourcc library. This patch adds those missing
> fourcc codes.
Could you please also document the new formats in
Documentation/media/uapi/v4l/ ? You can have a look at pixfmt-*.rst for
examples. Please make sure that the documentation compiles without any error
("make htmldocs") before submitting the patch.
> Signed-off-by: Jeffrey Mouroux <jmouroux@xilinx.com>
> ---
> include/uapi/linux/videodev2.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> index 45cf735..a059439 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
> @@ -509,6 +509,7 @@ struct v4l2_pix_format {
> #define V4L2_PIX_FMT_RGB32 v4l2_fourcc('R', 'G', 'B', '4') /* 32
> RGB-8-8-8-8 */ #define V4L2_PIX_FMT_ARGB32 v4l2_fourcc('B', 'A', '2',
> '4') /* 32 ARGB-8-8-8-8 */ #define V4L2_PIX_FMT_XRGB32 v4l2_fourcc('B',
> 'X', '2', '4') /* 32 XRGB-8-8-8-8 */ +#define V4L2_PIX_FMT_XBGR30
> v4l2_fourcc('R', 'X', '3', '0') /* 32 XBGR-2-10-10-10 */
>
> /* Grey formats */
> #define V4L2_PIX_FMT_GREY v4l2_fourcc('G', 'R', 'E', 'Y') /* 8
> Greyscale */ @@ -536,12 +537,16 @@ struct v4l2_pix_format {
> #define V4L2_PIX_FMT_VYUY v4l2_fourcc('V', 'Y', 'U', 'Y') /* 16 YUV
> 4:2:2 */ #define V4L2_PIX_FMT_Y41P v4l2_fourcc('Y', '4', '1', 'P')
> /* 12 YUV 4:1:1 */ #define V4L2_PIX_FMT_YUV444 v4l2_fourcc('Y', '4',
> '4', '4') /* 16 xxxxyyyy uuuuvvvv */ +#define V4L2_PIX_FMT_XVUY32
> v4l2_fourcc('X', 'V', '3', '2') /* 32 XVUY 8:8:8:8 */ +#define
> V4L2_PIX_FMT_AVUY32 v4l2_fourcc('A', 'V', '3', '2') /* 32 AVUY 8:8:8:8 */
> +#define V4L2_PIX_FMT_VUY24 v4l2_fourcc('V', 'U', '2', '4') /* 24 VUY
> 8:8:8 */ #define V4L2_PIX_FMT_YUV555 v4l2_fourcc('Y', 'U', 'V', 'O') /* 16
> YUV-5-5-5 */ #define V4L2_PIX_FMT_YUV565 v4l2_fourcc('Y', 'U', 'V',
> 'P') /* 16 YUV-5-6-5 */ #define V4L2_PIX_FMT_YUV32 v4l2_fourcc('Y',
> 'U', 'V', '4') /* 32 YUV-8-8-8-8 */ #define V4L2_PIX_FMT_HI240
> v4l2_fourcc('H', 'I', '2', '4') /* 8 8-bit color */ #define
> V4L2_PIX_FMT_HM12 v4l2_fourcc('H', 'M', '1', '2') /* 8 YUV 4:2:0 16x16
> macroblocks */ #define V4L2_PIX_FMT_M420 v4l2_fourcc('M', '4', '2', '0')
> /* 12 YUV 4:2:0 2 lines y, 1 line uv interleaved */ +#define
> V4L2_PIX_FMT_XVUY10 v4l2_fourcc('X', 'Y', '1', '0') /* 32 XVUY 2-10-10-10
> */
>
> /* two planes -- one Y, one Cr + Cb interleaved */
> #define V4L2_PIX_FMT_NV12 v4l2_fourcc('N', 'V', '1', '2') /* 12 Y/CbCr
> 4:2:0 */ @@ -550,6 +555,8 @@ struct v4l2_pix_format {
> #define V4L2_PIX_FMT_NV61 v4l2_fourcc('N', 'V', '6', '1') /* 16 Y/CrCb
> 4:2:2 */ #define V4L2_PIX_FMT_NV24 v4l2_fourcc('N', 'V', '2', '4') /*
> 24 Y/CbCr 4:4:4 */ #define V4L2_PIX_FMT_NV42 v4l2_fourcc('N', 'V',
> '4', '2') /* 24 Y/CrCb 4:4:4 */ +#define V4L2_PIX_FMT_XV20
> v4l2_fourcc('X', 'V', '2', '0') /* 32 XY/UV 4:2:2 10-bit */ +#define
> V4L2_PIX_FMT_XV15 v4l2_fourcc('X', 'V', '1', '5') /* 32 XY/UV 4:2:0
> 10-bit */
>
> /* two non contiguous planes - one Y, one Cr + Cb interleaved */
> #define V4L2_PIX_FMT_NV12M v4l2_fourcc('N', 'M', '1', '2') /* 12 Y/CbCr
> 4:2:0 */ @@ -557,6 +564,8 @@ struct v4l2_pix_format {
> #define V4L2_PIX_FMT_NV16M v4l2_fourcc('N', 'M', '1', '6') /* 16 Y/CbCr
> 4:2:2 */ #define V4L2_PIX_FMT_NV61M v4l2_fourcc('N', 'M', '6', '1') /*
> 16 Y/CrCb 4:2:2 */ #define V4L2_PIX_FMT_NV12MT v4l2_fourcc('T', 'M',
> '1', '2') /* 12 Y/CbCr 4:2:0 64x32 macroblocks */ +#define
> V4L2_PIX_FMT_XV20M v4l2_fourcc('X', 'M', '2', '0') /* 32 XY/UV 4:2:2
> 10-bit */ +#define V4L2_PIX_FMT_XV15M v4l2_fourcc('X', 'M', '1', '5') /*
> 32 XY/UV 4:2:0 10-bit */ #define V4L2_PIX_FMT_NV12MT_16X16 v4l2_fourcc('V',
> 'M', '1', '2') /* 12 Y/CbCr 4:2:0 16x16 macroblocks */
>
> /* three planes - Y Cb, Cr */
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-08-09 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 1:31 [PATCH v1 0/2] New fourcc codes needed by Video DMA Driver Jeffrey Mouroux
2017-08-09 1:31 ` [PATCH v1 1/2] uapi: media: New fourcc codes needed by Xilinx Video IP Jeffrey Mouroux
2017-08-09 7:53 ` Laurent Pinchart [this message]
2017-08-09 1:31 ` [PATCH v1 2/2] media: v4l2-core: Update V4L2 framework with new fourcc codes Jeffrey Mouroux
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=5292400.sDssS5K49F@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=evgeni.raikhel@intel.com \
--cc=hansverk@cisco.com \
--cc=jeff.mouroux@xilinx.com \
--cc=jmouroux@xilinx.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nick@shmanahar.org \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tiffany.lin@mediatek.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.