From: <john.wei@mediatek.com>
To: <john.wei@mediatek.com>, <louis.kuo@mediak.com>,
<mchehab@kernel.org>, <matthias.bgg@gmail.com>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>
Subject: [RFC PATCH V0 1/2] media: v4l2: Add fields to frame descriptors
Date: Fri, 7 May 2021 10:53:36 +0800 [thread overview]
Message-ID: <1620356017-26486-2-git-send-email-john.wei@mediatek.com> (raw)
In-Reply-To: <1620356017-26486-1-git-send-email-john.wei@mediatek.com>
From: John Wei <john.wei@mediatek.com>
Add enable, hsize, vsize, user_data_desc to frame descriptors
This patch is derived from following patches
https://patchwork.kernel.org/patch/10875875/
https://patchwork.kernel.org/patch/10875869/
Signed-off-by: John Wei <john.wei@mediatek.com>
---
include/media/v4l2-subdev.h | 25 ++++++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
index 30ec011..f603831 100644
--- a/include/media/v4l2-subdev.h
+++ b/include/media/v4l2-subdev.h
@@ -308,15 +308,38 @@ struct v4l2_subdev_audio_ops {
int (*s_stream)(struct v4l2_subdev *sd, int enable);
};
+enum v4l2_mbus_csi2_user_defined_data_desc {
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_NONE,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_Y_HIST,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_AE_HIST,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_FLICKER,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_GYRO,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_PDAF_PIXEL,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_PDAF_DIFF,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_HDR_LE,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_HDR_ME,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_HDR_SE,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_HDR_SSE,
+ V4L2_MBUS_CSI2_USER_DEFINED_DATA_DESC_HDR_SSSE,
+};
+
/**
* struct v4l2_mbus_frame_desc_entry_csi2
*
* @channel: CSI-2 virtual channel
* @data_type: CSI-2 data type ID
+ * @enable: enable this data identifier
+ * @hsize: horizontal size
+ * @vsize: vertical size
+ * @user_data_desc: the description of user defined data
*/
struct v4l2_mbus_frame_desc_entry_csi2 {
u8 channel;
u8 data_type;
+ u8 enable;
+ u16 hsize;
+ u16 vsize;
+ enum v4l2_mbus_csi2_user_defined_data_desc user_data_desc;
};
/**
@@ -354,7 +377,7 @@ struct v4l2_mbus_frame_desc_entry {
} bus;
};
-#define V4L2_FRAME_DESC_ENTRY_MAX 4
+#define V4L2_FRAME_DESC_ENTRY_MAX 8
enum v4l2_mbus_frame_desc_type {
V4L2_MBUS_FRAME_DESC_TYPE_PLATFORM,
--
1.7.9.5
next prev parent reply other threads:[~2021-05-07 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 2:53 [RFC PATCH V0 0/2] media: v4l2: extend framework to support advanced feature of Mediatek Camsys driver john.wei
2021-05-07 2:53 ` john.wei [this message]
2021-05-07 2:53 ` [RFC PATCH V0 2/2] media: v4l2-ctrl: Add user defined base for ISP user control john.wei
2021-05-07 9:38 ` [RFC PATCH V0 0/2] media: v4l2: extend framework to support advanced feature of Mediatek Camsys driver Sakari Ailus
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=1620356017-26486-2-git-send-email-john.wei@mediatek.com \
--to=john.wei@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediak.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=wsd_upstream@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 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).