From: Conor Dooley <conor@kernel.org>
To: Aliaksandr Smirnou <support@pinefeat.co.uk>
Cc: 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 v3 1/2] dt-bindings: Pinefeat cef168 lens control board
Date: Mon, 18 Aug 2025 18:36:50 +0100 [thread overview]
Message-ID: <20250818-stark-unsocial-96d32a311cab@spud> (raw)
In-Reply-To: <20250817130549.7766-2-support@pinefeat.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2511 bytes --]
On Sun, Aug 17, 2025 at 02:05:48PM +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.
Wut? This doesn't make sense, you have supplies so they should be
documented. The fact that they're shared with a bunch of other things on
the SBC you're aiming the product at doesn't matter. What if someone
doesn't use this sensor with an RPi and there is a dedicated regulator?
> Signed-off-by: Aliaksandr Smirnou <support@pinefeat.co.uk>
Is that actually your email address?
> ---
> .../bindings/media/i2c/pinefeat,cef168.yaml | 48 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> MAINTAINERS | 6 +++
> 3 files changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/pinefeat,cef168.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/pinefeat,cef168.yaml b/Documentation/devicetree/bindings/media/i2c/pinefeat,cef168.yaml
> new file mode 100644
> index 000000000000..80cdff40d175
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/pinefeat,cef168.yaml
> @@ -0,0 +1,48 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (c) 2025 Pinefeat LLP
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/pinefeat,cef168.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Pinefeat cef168 lens driver
> +
> +maintainers:
> + - Aliaksandr Smirnou <support@pinefeat.co.uk>
> +
> +description: |
> + Pinefeat produces an adapter designed to interface between
> + Canon EF & EF-S lenses and non-Canon camera bodies, incorporating
> + features for electronic focus and aperture adjustment. The cef168
> + circuit board, included with the adapter, provides a software
> + programming interface that allows control of lens focus and
> + aperture positions.
> This driver enables controlling the lens
> + focus and aperture via the V4L2 (Video4Linux2) API.
Don't mention drivers in bindings, how linux handles things is not
relevant to a hardware description.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-18 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 13:05 [PATCH v3 0/2] Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-08-17 13:05 ` [PATCH v3 1/2] dt-bindings: Pinefeat cef168 lens control board Aliaksandr Smirnou
2025-08-18 17:36 ` Conor Dooley [this message]
2025-08-18 19:29 ` Aliaksandr Smirnou
2025-08-19 8:21 ` Krzysztof Kozlowski
2025-08-17 13:05 ` [PATCH v3 2/2] media: i2c: Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-08-19 13:47 ` Jacopo Mondi
2025-08-19 21:32 ` Aliaksandr Smirnou
2025-08-20 12:56 ` Jacopo Mondi
2025-08-22 17:04 ` 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=20250818-stark-unsocial-96d32a311cab@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=support@pinefeat.co.uk \
/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