From: sashiko-bot@kernel.org
To: "Vladimir Zapolskiy" <vz@kernel.org>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org, media-ci@linuxtv.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH 2/7] arm64: dts: qcom: sm8450: Add CSI2 PHY device tree nodes
Date: Fri, 23 Oct 2026 16:57:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-182975@kernel.org> (raw)
In-Reply-To: <20261023163057.775917-3-vz@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: qcom: sm8450: codename compatible used for csiphy nodes
--
commit 0c7c977d6500322c8d06815e06e46862092f3fc5
Author: Vladimir Zapolskiy <vz@kernel.org>
arm64: dts: qcom: sm8450: Add CSI2 PHY device tree nodes
This commit adds six CAMSS CSIPHY device tree nodes and a shared CSIPHY OPP
table for the Qualcomm SM8450 (Waipio) SoC.
> diff --git a/arch/arm64/boot/dts/qcom/sm8450.dtsi b/arch/arm64/boot/dts/qcom/sm8450.dtsi
> index b8793482b1815..b70a8635c6be8 100644
> --- a/arch/arm64/boot/dts/qcom/sm8450.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8450.dtsi
[ ... ]
> @@ -3298,6 +3314,270 @@ cci1_i2c1: i2c-bus@1 {
> };
> };
>
> + csiphy0: phy@ace4000 {
> + compatible = "qcom,waipio-csi2-phy", "qcom,x1e80100-csi2-phy";
[Severity: Low]
Should csiphy0 through csiphy5 in arch/arm64/boot/dts/qcom/sm8450.dtsi (and
the corresponding binding in
Documentation/devicetree/bindings/phy/qcom,x1e80100-csi2-phy.yaml) use the
SoC model-number compatible "qcom,sm8450-csi2-phy" instead of the internal
codename "qcom,waipio-csi2-phy"?
In Documentation/devicetree/bindings/arm/qcom.yaml, the canonical SoC
compatible for Waipio is "qcom,sm8450", and
Documentation/devicetree/bindings/arm/qcom-soc.yaml specifies that SoCs
numbered with sm[0-9]+ use "qcom,sm<number>-*" for component compatibles,
while codename-based compatibles are reserved for the newer codename-only
SoCs:
# Preferred naming style for compatibles of SoC components:
- pattern: "^qcom,(apq|ipq|mdm|msm|qcm|qcs|q[dr]u|sa|sc|sd[amx]|sm|x1[ep])[0-9]+(pro)?-.*$"
- pattern: "^qcom,sar[0-9]+[a-z]?-.*$"
- pattern: "^qcom,(sa|sc)8[0-9]+[a-z][a-z]?-.*$"
- pattern: "^qcom,(eliza|kaanapali|glymur|hawi|mahua|maili|milos|nord|shikra)-.+$"
All other SoC-specific blocks in arch/arm64/boot/dts/qcom/sm8450.dtsi,
including the camera subsystem nodes camcc ("qcom,sm8450-camcc") and
cci0/cci1 ("qcom,sm8450-cci") as well as all other PHY nodes, follow the
"qcom,sm8450-*" naming convention.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023163057.775917-1-vz@kernel.org?part=2
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Vladimir Zapolskiy" <vz@kernel.org>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org, media-ci@linuxtv.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH 2/7] arm64: dts: qcom: sm8450: Add CSI2 PHY device tree nodes
Date: Fri, 23 Oct 2026 16:57:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-182975@kernel.org> (raw)
In-Reply-To: <20261023163057.775917-3-vz@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: qcom: sm8450: codename compatible used for csiphy nodes
--
commit 0c7c977d6500322c8d06815e06e46862092f3fc5
Author: Vladimir Zapolskiy <vz@kernel.org>
arm64: dts: qcom: sm8450: Add CSI2 PHY device tree nodes
This commit adds six CAMSS CSIPHY device tree nodes and a shared CSIPHY OPP
table for the Qualcomm SM8450 (Waipio) SoC.
> diff --git a/arch/arm64/boot/dts/qcom/sm8450.dtsi b/arch/arm64/boot/dts/qcom/sm8450.dtsi
> index b8793482b1815..b70a8635c6be8 100644
> --- a/arch/arm64/boot/dts/qcom/sm8450.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8450.dtsi
[ ... ]
> @@ -3298,6 +3314,270 @@ cci1_i2c1: i2c-bus@1 {
> };
> };
>
> + csiphy0: phy@ace4000 {
> + compatible = "qcom,waipio-csi2-phy", "qcom,x1e80100-csi2-phy";
[Severity: Low]
Should csiphy0 through csiphy5 in arch/arm64/boot/dts/qcom/sm8450.dtsi (and
the corresponding binding in
Documentation/devicetree/bindings/phy/qcom,x1e80100-csi2-phy.yaml) use the
SoC model-number compatible "qcom,sm8450-csi2-phy" instead of the internal
codename "qcom,waipio-csi2-phy"?
In Documentation/devicetree/bindings/arm/qcom.yaml, the canonical SoC
compatible for Waipio is "qcom,sm8450", and
Documentation/devicetree/bindings/arm/qcom-soc.yaml specifies that SoCs
numbered with sm[0-9]+ use "qcom,sm<number>-*" for component compatibles,
while codename-based compatibles are reserved for the newer codename-only
SoCs:
# Preferred naming style for compatibles of SoC components:
- pattern: "^qcom,(apq|ipq|mdm|msm|qcm|qcs|q[dr]u|sa|sc|sd[amx]|sm|x1[ep])[0-9]+(pro)?-.*$"
- pattern: "^qcom,sar[0-9]+[a-z]?-.*$"
- pattern: "^qcom,(sa|sc)8[0-9]+[a-z][a-z]?-.*$"
- pattern: "^qcom,(eliza|kaanapali|glymur|hawi|mahua|maili|milos|nord|shikra)-.+$"
All other SoC-specific blocks in arch/arm64/boot/dts/qcom/sm8450.dtsi,
including the camera subsystem nodes camcc ("qcom,sm8450-camcc") and
cci0/cci1 ("qcom,sm8450-cci") as well as all other PHY nodes, follow the
"qcom,sm8450-*" naming convention.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023163057.775917-1-vz@kernel.org?part=2
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-23 16:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 16:30 [PATCH 0/7] media: qcom: camss: Add Waipio CAMSS support Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-23 16:30 ` [PATCH 1/7] dt-bindings: phy: qcom,x1e80100-csi2-phy: Add Waipio compatible Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-23 16:44 ` sashiko-bot
2026-10-23 16:44 ` sashiko-bot
2026-10-23 22:43 ` Bryan O'Donoghue
2026-10-23 22:43 ` Bryan O'Donoghue
2026-10-26 10:04 ` Krzysztof Kozlowski
2026-10-26 10:04 ` Krzysztof Kozlowski
2026-10-23 16:30 ` [PATCH 2/7] arm64: dts: qcom: sm8450: Add CSI2 PHY device tree nodes Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-23 16:57 ` sashiko-bot [this message]
2026-10-23 16:57 ` sashiko-bot
2026-10-23 22:44 ` Bryan O'Donoghue
2026-10-23 22:44 ` Bryan O'Donoghue
2026-10-26 10:05 ` Krzysztof Kozlowski
2026-10-26 10:05 ` Krzysztof Kozlowski
2026-10-23 16:30 ` [PATCH 3/7] dt-bindings: media: Add description of Qualcomm Waipio CAMSS IP Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-23 16:58 ` sashiko-bot
2026-10-23 16:58 ` sashiko-bot
2026-10-26 10:03 ` Krzysztof Kozlowski
2026-10-26 10:03 ` Krzysztof Kozlowski
2026-10-23 16:30 ` [PATCH 4/7] arm64: dts: qcom: sm8450: Add CAMSS device tree node Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-26 10:04 ` Krzysztof Kozlowski
2026-10-26 10:04 ` Krzysztof Kozlowski
2026-10-26 16:32 ` Loic Poulain
2026-10-26 16:32 ` Loic Poulain
2026-10-26 22:38 ` Vladimir Zapolskiy
2026-10-26 22:38 ` Vladimir Zapolskiy
2026-10-27 9:07 ` Loic Poulain
2026-10-27 9:07 ` Loic Poulain
2026-10-27 9:54 ` Vladimir Zapolskiy
2026-10-27 9:54 ` Vladimir Zapolskiy
2026-10-27 10:31 ` Loic Poulain
2026-10-27 10:31 ` Loic Poulain
2026-10-27 12:57 ` Vladimir Zapolskiy
2026-10-27 12:57 ` Vladimir Zapolskiy
2026-10-27 11:14 ` Konrad Dybcio
2026-10-27 11:14 ` Konrad Dybcio
2026-10-23 16:30 ` [PATCH 5/7] arm64: dts: qcom: sm8450: Add description of pins with MCLK function Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-26 14:09 ` Konrad Dybcio
2026-10-26 14:09 ` Konrad Dybcio
2026-10-23 16:30 ` [PATCH 6/7] media: qcom: camss: Allow CSI2 PHY devices without CSIPHY resources Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
2026-10-23 16:30 ` [PATCH 7/7] media: qcom: camss: Add Waipio CAMSS support Vladimir Zapolskiy
2026-10-23 16:30 ` Vladimir Zapolskiy
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=sashiko-outbox-182975@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=media-ci@linuxtv.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
--cc=vz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.