From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Hongyang Zhao <hongyang.zhao@thundersoft.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Roger Shimizu <rosh@debian.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: qcs6490-rubikpi3: Add IMX219 camera overlays
Date: Tue, 18 Aug 2026 14:41:20 +0200 [thread overview]
Message-ID: <1ef41a49-dcf8-4252-acdd-f7f3c1210c55@oss.qualcomm.com> (raw)
In-Reply-To: <20260812-rubikpi-next-20260615-v3-2-06e21232d8e4@thundersoft.com>
On 8/12/26 4:22 AM, Hongyang Zhao wrote:
> RUBIK Pi 3 ships without camera sensors, and its two connectors support
> multiple modules. Keep module-specific nodes out of the base board DTS
> and add per-connector overlays for Raspberry Pi Camera Module V2 IMX219
> sensors.
>
> CAM1 uses CCI1 and CSIPHY1, while CAM2 uses CCI0 and CSIPHY4. Each
> overlay describes the 24 MHz sensor input clock and models the module
> power domain controlled through the connector PWR_EN signal. The
> baseboard supplies VCC3V3_OUTPUT separately and has no per-camera
> regulator.
>
> Describe each connector CAMERA_GPIO signal as a privacy indicator LED
> and associate it with the corresponding sensor. This lets the V4L2 core
> control the LED while the sensor is streaming.
>
> Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Signed-off-by: Hongyang Zhao <hongyang.zhao@thundersoft.com>
> ---
[...]
> + camera@10 {
> + compatible = "sony,imx219";
> + reg = <0x10>;
> +
> + clocks = <&cam1_imx219_clk>;
> +
> + VANA-supply = <&vreg_cam1_pwr>;
> + VDIG-supply = <&vreg_cam1_pwr>;
> + VDDL-supply = <&vreg_cam1_pwr>;
> +
> + leds = <&cam1_privacy_led>;
> + led-names = "privacy";
No reset GPIOs?
You should also have a reference to the mclk pin state to make sure
the correct pin function kicks in
Konrad
next prev parent reply other threads:[~2026-08-18 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 2:22 [PATCH v3 0/2] arm64: dts: qcom: qcs6490-rubikpi3: Add IMX219 camera overlays Hongyang Zhao
2026-08-12 2:22 ` [PATCH v3 1/2] arm64: dts: qcom: qcs6490-rubikpi3: Add 3.3 V output supply Hongyang Zhao
2026-08-18 12:39 ` Konrad Dybcio
2026-08-12 2:22 ` [PATCH v3 2/2] arm64: dts: qcom: qcs6490-rubikpi3: Add IMX219 camera overlays Hongyang Zhao
2026-08-18 12:41 ` Konrad Dybcio [this message]
2026-08-25 11:13 ` Hongyang Zhao
2026-08-26 10:25 ` Konrad Dybcio
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=1ef41a49-dcf8-4252-acdd-f7f3c1210c55@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongyang.zhao@thundersoft.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rosh@debian.org \
--cc=s.hauer@pengutronix.de \
/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