From: Vivek Kasireddy <vivek.kasireddy@intel.com>
To: <linux-media@vger.kernel.org>
Cc: Vivek Kasireddy <vivek.kasireddy@intel.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: [PATCH 3/4] media: vivid: Add definitions for the 32-bit packed YUV formats
Date: Thu, 7 Feb 2019 19:18:45 -0800 [thread overview]
Message-ID: <20190208031846.14453-4-vivek.kasireddy@intel.com> (raw)
In-Reply-To: <20190208031846.14453-1-vivek.kasireddy@intel.com>
Enable vivid to make use of the following formats:
V4L2_PIX_FMT_AYUV32
V4L2_PIX_FMT_XYUV32
V4L2_PIX_FMT_VUYA32
V4L2_PIX_FMT_VUYX32
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
---
drivers/media/platform/vivid/vivid-vid-common.c | 30 +++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/drivers/media/platform/vivid/vivid-vid-common.c b/drivers/media/platform/vivid/vivid-vid-common.c
index 661f4015fba1..74b83bcc6119 100644
--- a/drivers/media/platform/vivid/vivid-vid-common.c
+++ b/drivers/media/platform/vivid/vivid-vid-common.c
@@ -168,6 +168,36 @@ struct vivid_fmt vivid_formats[] = {
.buffers = 1,
.alpha_mask = 0x000000ff,
},
+ {
+ .fourcc = V4L2_PIX_FMT_AYUV32,
+ .vdownsampling = { 1 },
+ .bit_depth = { 32 },
+ .planes = 1,
+ .buffers = 1,
+ .alpha_mask = 0x000000ff,
+ },
+ {
+ .fourcc = V4L2_PIX_FMT_XYUV32,
+ .vdownsampling = { 1 },
+ .bit_depth = { 32 },
+ .planes = 1,
+ .buffers = 1,
+ },
+ {
+ .fourcc = V4L2_PIX_FMT_VUYA32,
+ .vdownsampling = { 1 },
+ .bit_depth = { 32 },
+ .planes = 1,
+ .buffers = 1,
+ .alpha_mask = 0xff000000,
+ },
+ {
+ .fourcc = V4L2_PIX_FMT_VUYX32,
+ .vdownsampling = { 1 },
+ .bit_depth = { 32 },
+ .planes = 1,
+ .buffers = 1,
+ },
{
.fourcc = V4L2_PIX_FMT_GREY,
.vdownsampling = { 1 },
--
2.14.5
next prev parent reply other threads:[~2019-02-08 3:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 3:18 [PATCH 0/4] Add support for 32-bit packed YUV formats Vivek Kasireddy
2019-02-08 3:18 ` [PATCH 1/4] media: v4l: Add " Vivek Kasireddy
2019-02-08 3:18 ` [PATCH 2/4] media: v4l2-tpg-core: Add support for " Vivek Kasireddy
2019-02-08 10:21 ` kbuild test robot
2019-02-08 10:49 ` kbuild test robot
2019-02-09 1:29 ` [PATCH v2 2/4] media: v4l2-tpg-core: Add support for 32-bit packed YUV formats (v2) Vivek Kasireddy
2019-02-08 3:18 ` Vivek Kasireddy [this message]
2019-02-08 3:18 ` [PATCH 4/4] media: imx-pxp: Start using the format VUYA32 instead of YUV32 Vivek Kasireddy
2019-02-08 9:14 ` Philipp Zabel
2019-02-08 9:15 ` Hans Verkuil
2019-02-08 9:47 ` Philipp Zabel
2019-02-08 10:31 ` Philipp Zabel
2019-02-09 1:38 ` [PATCH v2 4/4] media: imx-pxp: Start using the format VUYA32 instead of YUV32 (v2) Vivek Kasireddy
2019-02-11 10:29 ` Philipp Zabel
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=20190208031846.14453-4-vivek.kasireddy@intel.com \
--to=vivek.kasireddy@intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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).