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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, rosh@debian.org
Subject: Re: [PATCH] arm64: dts: qcom: qcs6490-rubikpi3: Enable cameras
Date: Thu, 25 Jun 2026 11:30:48 +0200 [thread overview]
Message-ID: <a4073f5a-1965-4a6c-ba39-c236429e2db7@oss.qualcomm.com> (raw)
In-Reply-To: <20260616-rubikpi-next-20260615-v1-1-3d96b89397ff@thundersoft.com>
On 6/16/26 9:29 AM, Hongyang Zhao wrote:
> Enable the two Raspberry Pi camera connectors on RubikPi 3 with
> IMX219 sensors. CAM1 is connected to CCI1 and CSIPHY1, while CAM2
> is connected to CCI0 and CSIPHY4.
>
> Add the shared 24 MHz camera oscillator, camera power enable
> regulators, CAMSS endpoints, CCI sensor nodes and privacy LED GPIOs.
>
> Signed-off-by: Hongyang Zhao <hongyang.zhao@thundersoft.com>
> ---
[...]
> + vreg_cam1_pwr: regulator-camera1-pwr {
> + compatible = "regulator-fixed";
> +
> + regulator-name = "vreg_camera1_pwr";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +
> + gpio = <&tlmm 57 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> +
> + pinctrl-0 = <&cam1_pwr_en>;
> + pinctrl-names = "default";
> +
> + vin-supply = <&vreg_vcc3v3_output>;
> + };
> +
> + vreg_cam2_pwr: regulator-camera2-pwr {
> + compatible = "regulator-fixed";
> +
> + regulator-name = "vreg_camera2_pwr";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +
> + gpio = <&tlmm 58 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> +
> + pinctrl-0 = <&cam2_pwr_en>;
> + pinctrl-names = "default";
> +
> + vin-supply = <&vreg_vcc3v3_output>;
> + };
Are these supplies part of the baseboard?
[...]
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + /* CAM1 is routed to CSI1 / CSIPHY1. */
I believe these comments are self-explanatory given the names of the labels
[...]
> + cam1_privacy_led_state: cam1-privacy-led-state {
> + pins = "gpio18";
> + function = "gpio";
> + drive-strength = <8>;
> + output-low;
Please drop the output-foo properties from TLMM pins, the GPIO
state will be controlled by the driver
Konrad
next prev parent reply other threads:[~2026-06-25 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 7:29 Hongyang Zhao
2026-06-25 9:30 ` Konrad Dybcio [this message]
2026-06-25 15:08 ` Hongyang Zhao
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=a4073f5a-1965-4a6c-ba39-c236429e2db7@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hongyang.zhao@thundersoft.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rosh@debian.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®