From: Aliaksandr Smirnou <support@pinefeat.co.uk>
To: jacopo.mondi@ideasonboard.com, hverkuil@xs4all.nl,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aliaksandr Smirnou <support@pinefeat.co.uk>
Subject: [PATCH v4 0/2] Pinefeat cef168 lens control board driver
Date: Fri, 22 Aug 2025 18:10:39 +0100 [thread overview]
Message-ID: <20250822171041.7340-1-support@pinefeat.co.uk> (raw)
This patch series adds support for the Pinefeat adapter, which interfaces
Canon EF and EF-S lenses to non-Canon camera bodies. The cef168 circuit
control board provides an I2C interface for electronic focus and aperture
control. The driver integrates with the V4L2 sub-device API.
For more information about the product, see:
https://github.com/pinefeat/cef168
Changes in v4:
- removed driver mention from the hardware documentation;
- added named email in commit signed-off-by;
- added select CRC8 in Kconfig;
- removed header file;
- moved variable declaration at the beginning of the function;
- removed kerneldoc from structures;
- removed control id check as the core handles this for us;
- removed Power Management Runtime (pm_runtime_*) calls as redundant;
- reserved v4l2 controls in linux header file;
Link to v3: https://lore.kernel.org/all/20250817130549.7766-1-support@pinefeat.co.uk/
Patches:
dt-bindings: Pinefeat cef168 lens control board
media: i2c: Pinefeat cef168 lens control board driver
.../bindings/media/i2c/pinefeat,cef168.yaml | 47 +++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
MAINTAINERS | 7 +
drivers/media/i2c/Kconfig | 9 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/cef168.c | 331 ++++++++++++++++++
include/uapi/linux/v4l2-controls.h | 6 +
7 files changed, 403 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/pinefeat,cef168.yaml
create mode 100644 drivers/media/i2c/cef168.c
base-commit: 2b38afce25c4e1b8f943ff4f0a2b51d6c40f2ed2
--
2.34.1
next reply other threads:[~2025-08-22 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 17:10 Aliaksandr Smirnou [this message]
2025-08-22 17:10 ` [PATCH v4 1/2] dt-bindings: Pinefeat cef168 lens control board Aliaksandr Smirnou
2025-08-24 9:22 ` Krzysztof Kozlowski
2025-08-22 17:10 ` [PATCH v4 2/2] media: i2c: Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-08-30 11:14 [PATCH v4 0/2] " Aliaksandr Smirnou
2025-08-30 13:20 ` Krzysztof Kozlowski
2025-09-21 18:52 ` Aliaksandr Smirnou
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=20250822171041.7340-1-support@pinefeat.co.uk \
--to=support@pinefeat.co.uk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®