From: Conor Dooley <conor@kernel.org>
To: Aliaksandr Smirnou <asmirnou@pinefeat.co.uk>
Cc: jacopo.mondi@ideasonboard.com, hverkuil@xs4all.nl,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: Pinefeat cef168 lens control board
Date: Tue, 7 Oct 2025 20:39:26 +0100 [thread overview]
Message-ID: <20251007-geologic-epidemic-2f667f232cf6@spud> (raw)
In-Reply-To: <20251005133228.62704-2-asmirnou@pinefeat.co.uk>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On Sun, Oct 05, 2025 at 02:32:27PM +0100, Aliaksandr Smirnou wrote:
> Add the Device Tree schema and examples for the Pinefeat cef168 lens
> control board. This board interfaces Canon EF & EF-S lenses with
> non-Canon camera bodies, enabling electronic control of focus and
> aperture via V4L2.
>
> Power supply is derived from fixed supplies via connector or GPIO
> header. Therefore, the driver does not manage any regulator, so
> representing any supply in the binding is redundant.
>
> Signed-off-by: Aliaksandr Smirnou <asmirnou@pinefeat.co.uk>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-07 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 13:32 [PATCH v5 0/2] Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-10-05 13:32 ` [PATCH v5 1/2] dt-bindings: Pinefeat cef168 lens control board Aliaksandr Smirnou
2025-10-07 19:39 ` Conor Dooley [this message]
2025-10-05 13:32 ` [PATCH v5 2/2] media: i2c: Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-10-05 14:32 ` Kieran Bingham
2025-10-05 18:00 ` Aliaksandr Smirnou
2025-10-05 19:58 ` Kieran Bingham
2025-10-06 20:46 ` 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=20251007-geologic-epidemic-2f667f232cf6@spud \
--to=conor@kernel.org \
--cc=asmirnou@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