Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Hongyang Zhao <hongyang.zhao@thundersoft.com>
Cc: Frank.Li@nxp.com, andersson@kernel.org,
	bryan.odonoghue@linaro.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, festevam@gmail.com,
	imx@lists.linux.dev, kernel@pengutronix.de,
	konradybcio@kernel.org, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh@kernel.org, rosh@debian.org, s.hauer@pengutronix.de
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: qcs6490-rubikpi3: Add IMX219 camera overlays
Date: Wed, 26 Aug 2026 12:25:12 +0200	[thread overview]
Message-ID: <c61f297e-3a42-4b23-b341-0f8d97d4b78f@oss.qualcomm.com> (raw)
In-Reply-To: <20260825111300.578054-1-hongyang.zhao@thundersoft.com>

On 8/25/26 1:13 PM, Hongyang Zhao wrote:
> Hi Konrad,
> 
> Thanks for the review.

[...]

>> No reset GPIOs?
> 
> Yes. The RubikPi camera connector does not route a dedicated sensor reset
> signal. It exposes PWR_EN and CAMERA_GPIO, but neither is connected
> directly to the IMX219 reset input when using the official Raspberry Pi
> Camera Module 2.
> 
> PWR_EN is connected to the module's ENABLE signal and controls the
> module-local power supplies. CAMERA_GPIO corresponds to a pin that is
> not connected on Camera Module 2. The IMX219 /PWDN signal remains local
> to the camera module and is tied to its 1.8 V rail.
> 
> Therefore, there is no board-controllable reset GPIO to describe for
> this camera configuration.
> 
>>
>> You should also have a reference to the mclk pin state to make sure
>> the correct pin function kicks in
> 
> The Camera Module 2 provides its own 24 MHz oscillator, which is
> connected to the IMX219 MCLK input on the module. RubikPi does not route
> a SoC CAM_MCLK signal to this connector. The fixed-clock node represents
> that module-local oscillator, so there is no corresponding TLMM MCLK
> pin state.
> 
> The Camera Module 2 schematic shows both connections:
> https://datasheets.raspberrypi.com/camera/camera-module-2-schematics.pdf
> 
> RUBIK Pi 3 schematic (CSI connector, page 13):
> https://thundercomm.s3-accelerate.amazonaws.com/uploads/web/rubik-pi-3/RUBIKPI3-IOB-V02-RELEASE.pdf

Got it, thanks for the explanation

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

      reply	other threads:[~2026-08-26 10:25 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
2026-08-25 11:13     ` Hongyang Zhao
2026-08-26 10:25       ` Konrad Dybcio [this message]

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=c61f297e-3a42-4b23-b341-0f8d97d4b78f@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