From: Aliaksandr Smirnou <support@pinefeat.co.uk>
To: krzk@kernel.org
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,
support@pinefeat.co.uk
Subject: [PATCH v2 1/2] dt-bindings: Pinefeat cef168 lens control board
Date: Tue, 12 Aug 2025 20:37:22 +0100 [thread overview]
Message-ID: <20250812193722.10193-1-support@pinefeat.co.uk> (raw)
In-Reply-To: <84262447-0877-4c52-8c80-65f1288e5944@kernel.org>
On Tue, 12 Aug 2025 09:13:22 +0200, Krzysztof Kozlowski wrote:
> Property says VCC, description says VDD, datasheet says 5V (not 3.3V).
>
> I guess this should be for the 5V case, no?
Thank you following up.
The 5V line is used exclusively to power the lens motor (through the
power switch). This 5V supply can come from the Raspberry Pi GPIO
header, a battery, or other sources. Importantly, this power source
is independent of the board’s MCU and its kernel driver.
Additionally, the board does not include any voltage regulators.
The MCU operates at 3.3V, which is supplied either via the CSI connector
or the serial connector directly from the Raspberry Pi GPIO 3.3V rail.
Therefore, the driver does not manage any regulator, which is why the
“vcc-supply” property was absent in the binding.
Would you like me to remove the “vcc-supply” property as it was
originally?
next prev parent reply other threads:[~2025-08-12 19:37 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 [this message]
2025-08-14 9:04 ` Krzysztof Kozlowski
2025-08-14 20:10 ` Aliaksandr Smirnou
2025-08-17 7:14 ` Krzysztof Kozlowski
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=20250812193722.10193-1-support@pinefeat.co.uk \
--to=support@pinefeat.co.uk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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®