From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aliaksandr Smirnou <support@pinefeat.co.uk>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: Pinefeat cef168 lens control board
Date: Sun, 17 Aug 2025 09:14:24 +0200 [thread overview]
Message-ID: <c1b848b9-b1da-4976-9838-d474394a0992@kernel.org> (raw)
In-Reply-To: <20250814201038.15054-1-support@pinefeat.co.uk>
On 14/08/2025 22:10, Aliaksandr Smirnou wrote:
> On Thu, 14 Aug 2025 11:04:10 +0200, Krzysztof Kozlowski wrote:
>> You describe here the entire board, not the MCU only or lens motor
>> only...
>
> Since you asked about 5 V, I was explaining that this power source is not
> relevant for the driver.
>
>> Can the board be used outside of above setup? I understand so far this
>> is only for Rpi where both above supplies - 3.3 V and 5 V - are coming
>> from the header pins, so supplies would be totally redundant.
>
> There are several variants of the board, differing only in physical size
> and type of CSI connector, targeting different cameras. The board should
> be compatible with any single-board computer that uses a similar CSI
> connector pinout and MIPI signal lane assignment. For example, the NVIDIA
> Jetson series replicates the Raspberry Pi camera and GPIO header pinout.
> So yes, the board can be used outside of a Raspberry Pi setup.
If they replicate also power coming from the header and CSI line, then
it's fine, but if the do not, then you would need a controllable
regulator supply.
>
> As noted above, these supplies are redundant and were not included in the
> driver description. Given that, is it acceptable to remove the vcc-supply
> property?
Yeah, for simplicity. Please mention this rationale in the commit msg -
power supply is derived from fixed supplies (connector/header on RPi),
so representing it is redundant.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-17 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 21:31 [PATCH v2 0/2] Pinefeat cef168 lens control board driver Alexander Smirnov
2025-08-11 21:31 ` [PATCH v2 1/2] dt-bindings: Pinefeat cef168 lens control board Alexander Smirnov
2025-08-12 7:13 ` Krzysztof Kozlowski
2025-08-12 19:37 ` Aliaksandr Smirnou
2025-08-14 9:04 ` Krzysztof Kozlowski
2025-08-14 20:10 ` Aliaksandr Smirnou
2025-08-17 7:14 ` Krzysztof Kozlowski [this message]
2025-08-14 9:00 ` Krzysztof Kozlowski
2025-08-11 21:31 ` [PATCH v2 2/2] media/i2c: Pinefeat cef168 lens control board driver Alexander Smirnov
2025-08-13 1:28 ` kernel test robot
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=c1b848b9-b1da-4976-9838-d474394a0992@kernel.org \
--to=krzk@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
all inboxes | Powered by JetHome®