From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, hdegoede@redhat.com
Subject: [PATCH 3/6] media: v4l: cci: Add macros to obtain register width
Date: Fri, 10 Nov 2023 11:47:02 +0200 [thread overview]
Message-ID: <20231110094705.1367083-4-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20231110094705.1367083-1-sakari.ailus@linux.intel.com>
Add CCI_REG_WIDTH() macro to obtain register width in bits and similarly,
CCI_REG_WIDTH_BYTES() to obtain it in bytes.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
include/media/v4l2-cci.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/media/v4l2-cci.h b/include/media/v4l2-cci.h
index b4ce0a46092c..80eaa7fdc606 100644
--- a/include/media/v4l2-cci.h
+++ b/include/media/v4l2-cci.h
@@ -40,6 +40,9 @@ struct cci_reg_sequence {
#define CCI_REG_FLAG_PRIVATE_END 31U
#define CCI_REG_PRIVATE_MASK GENMASK(CCI_REG_FLAG_PRIVATE_END, CCI_REG_FLAG_PRIVATE_START)
+#define CCI_REG_WIDTH_BYTES(x) (((x) & CCI_REG_WIDTH_MASK) >> CCI_REG_WIDTH_SHIFT)
+#define CCI_REG_WIDTH(x) (CCI_REG_WIDTH_BYTES(x) << 3)
+
#define CCI_REG8(x) ((1 << CCI_REG_WIDTH_SHIFT) | (x))
#define CCI_REG16(x) ((2 << CCI_REG_WIDTH_SHIFT) | (x))
#define CCI_REG24(x) ((3 << CCI_REG_WIDTH_SHIFT) | (x))
--
2.39.2
next prev parent reply other threads:[~2023-11-10 17:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:46 [PATCH 0/6] Use V4L2 CCI in CCS driver Sakari Ailus
2023-11-10 9:47 ` [PATCH 1/6] media: v4l: cci: Include linux/bits.h Sakari Ailus
2023-11-10 11:11 ` Hans de Goede
2023-11-10 14:44 ` Laurent Pinchart
2023-11-10 9:47 ` [PATCH 2/6] media: v4l: cci: Add driver-private bit definitions Sakari Ailus
2023-11-10 11:11 ` Hans de Goede
2023-11-10 14:44 ` Laurent Pinchart
2023-11-10 21:21 ` Sakari Ailus
2023-11-10 9:47 ` Sakari Ailus [this message]
2023-11-10 11:14 ` [PATCH 3/6] media: v4l: cci: Add macros to obtain register width Hans de Goede
2023-11-10 11:17 ` Sakari Ailus
2023-11-10 14:44 ` Laurent Pinchart
2023-11-10 14:49 ` Laurent Pinchart
2023-11-10 14:52 ` Hans de Goede
2023-11-10 21:21 ` Sakari Ailus
2023-11-10 9:47 ` [PATCH 4/6] media: ccs: Generate V4L2 CCI compliant register definitions Sakari Ailus
2023-11-10 9:47 ` [PATCH 5/6] media: ccs: Better separate CCS static data access Sakari Ailus
2023-11-10 14:46 ` Laurent Pinchart
2023-11-10 21:24 ` Sakari Ailus
2023-11-10 9:47 ` [PATCH 6/6] media: ccs: Use V4L2 CCI for accessing sensor registers Sakari Ailus
2023-11-10 15:21 ` Laurent Pinchart
2023-11-10 21:38 ` Sakari Ailus
2023-11-10 22:53 ` Laurent Pinchart
2023-11-10 23:03 ` 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=20231110094705.1367083-4-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--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