From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Hangxiang Ma <hangxiang.ma@oss.qualcomm.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
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: kaanapali-mtp: Add s5kjn5 image sensor on CSIPHY2
Date: Fri, 24 Jul 2026 13:50:23 +0200 [thread overview]
Message-ID: <e3de235c-e962-4882-b4ed-8001142c838d@oss.qualcomm.com> (raw)
In-Reply-To: <20260720-knp-camera-v2-4-a21c3f0ecd55@oss.qualcomm.com>
On 7/21/26 6:57 AM, Hangxiang Ma wrote:
> Enable the S5KJN5 image sensor which connected to cci0_i2c1 on Kaanapali
> MTP. The sensor appears on CCI pins connected to the CSIPHY2 interface
> in four lane mode.
>
> Signed-off-by: Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>
> ---
[...]
> +&camss {
> + status = "okay";
> +
> + ports {
> + /*
> + * port0 => csiphy0
> + * port1 => csiphy1
> + * port2 => csiphy2
> + * port3 => csiphy3
> + * port4 => csiphy4
> + * port5 => csiphy5
> + */
This comment is SoC-specific and is really not very useful, especially
since it's an identity mapping
Konrad
next prev parent reply other threads:[~2026-07-24 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 4:57 [PATCH v2 0/4] Add CCI and CAMSS support for Kaanapali Hangxiang Ma
2026-07-21 4:57 ` [PATCH v2 1/4] arm64: dts: qcom: kaanapali: Add CAMSS block definitions Hangxiang Ma
2026-07-21 4:57 ` [PATCH v2 2/4] arm64: dts: qcom: kaanapali: Add CCI definitions Hangxiang Ma
2026-07-21 4:57 ` [PATCH v2 3/4] arm64: dts: qcom: kaanapali: Add camera MCLK pinctrl Hangxiang Ma
2026-07-21 4:57 ` [PATCH v2 4/4] arm64: dts: qcom: kaanapali-mtp: Add s5kjn5 image sensor on CSIPHY2 Hangxiang Ma
2026-07-24 11:50 ` Konrad Dybcio [this message]
2026-07-31 2:15 ` Hangxiang Ma
2026-07-27 14:04 ` Abel Vesa
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=e3de235c-e962-4882-b4ed-8001142c838d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hangxiang.ma@oss.qualcomm.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 \
/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®