From: Hsia-Jun Li <randy.li@synaptics.com>
To: dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, daniel@ffwll.ch, ezequiel@vanguardiasur.com.ar,
helen.koike@collabora.com, hverkuil-cisco@xs4all.nl,
jszhang@kernel.org, laurent.pinchart@ideasonboard.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mchehab@kernel.org,
mripard@kernel.org, nicolas@ndufresne.ca, ribalda@chromium.org,
sakari.ailus@linux.intel.com, sebastian.hesselbarth@gmail.com,
tfiga@chromium.org, tzimmermann@suse.de,
"Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
Subject: [PATCH v3 2/4] media: videodev2.h: add pixel format modifiers
Date: Tue, 1 Nov 2022 18:04:46 +0800 [thread overview]
Message-ID: <20221101100448.66712-3-randy.li@synaptics.com> (raw)
In-Reply-To: <20221101100448.66712-1-randy.li@synaptics.com>
From: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
Signed-off-by: Hsia-Jun(Randy) Li <randy.li@synaptics.com>
---
include/uapi/linux/videodev2.h | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
index 29da1f4b4578..d00b2e9c0c54 100644
--- a/include/uapi/linux/videodev2.h
+++ b/include/uapi/linux/videodev2.h
@@ -816,6 +816,26 @@ struct v4l2_pix_format {
#define V4L2_PIX_FMT_FLAG_PREMUL_ALPHA 0x00000001
#define V4L2_PIX_FMT_FLAG_SET_CSC 0x00000002
+/*
+ * F O R M A T M O D I F I E S
+ */
+/* Vendor Ids: */
+#define V4L2_PIX_FMT_RESERVED ((1ULL << 56) - 1)
+
+#define fourcc_mod_get_vendor(modifier) \
+ (((modifier) >> 56) & 0xff)
+
+#define fourcc_mod_is_vendor(modifier, vendor) \
+ (fourcc_mod_get_vendor(modifier) == V4L2_PIX_FMT_MOD_VENDOR_## vendor)
+
+#define fourcc_mod_code(vendor, val) \
+ ((((__u64)V4L2_PIX_FMT_MOD_VENDOR_## vendor) << 56) | ((val) & 0x00ffffffffffffffULL))
+
+/* Format Modifier tokens */
+#define V4L2_PIX_FMT_MOD_INVALID fourcc_mod_code(NONE, V4L2_PIX_FMT_RESERVED)
+#define V4L2_PIX_FMT_MOD_LINEAR fourcc_mod_code(NONE, 0)
+
+
/*
* F O R M A T E N U M E R A T I O N
*/
--
2.17.1
next prev parent reply other threads:[~2022-11-01 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 10:04 [PATCH v3 0/4] Add pixel formats used in Synatpics SoC Hsia-Jun Li
2022-11-01 10:04 ` [PATCH v3 1/4] drm/fourcc: Add Synaptics VideoSmart tiled modifiers Hsia-Jun Li
2022-11-01 10:04 ` Hsia-Jun Li [this message]
2022-11-01 17:10 ` [PATCH v3 2/4] media: videodev2.h: add pixel format modifiers kernel test robot
2022-11-01 19:01 ` kernel test robot
2022-11-02 1:25 ` kernel test robot
2022-11-01 10:04 ` [PATCH v3 3/4] media: videodev2.h: add Synaptics tiled modifiers Hsia-Jun Li
2022-11-01 10:04 ` [PATCH v3 4/4] media: docs: Add Synpatics tile modifiers Hsia-Jun 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=20221101100448.66712-3-randy.li@synaptics.com \
--to=randy.li@synaptics.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jszhang@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tfiga@chromium.org \
--cc=tzimmermann@suse.de \
/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