From: sashiko-bot@kernel.org
To: "Antony Kurniawan Soemardi via B4 Relay"
<devnull+linux.smankusors.com@kernel.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v2 08/10] ARM: dts: qcom: msm8960: add SMSM & SPS
Date: Thu, 14 May 2026 21:41:38 +0000 [thread overview]
Message-ID: <20260514214139.041E6C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260514-msm8960-wifi-v2-8-7cbae45dab5e@smankusors.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The `sps_sic_non_secure` node is named `interrupt-controller@12100000` but lacks the required `interrupt-controller` property.
- [Low] The newly added `smsm` node uses deprecated `qcom,ipc-X` properties.
--
commit 8d6a970313bb462414684a54e064e3c213cf7869
Author: Antony Kurniawan Soemardi <linux@smankusors.com>
ARM: dts: qcom: msm8960: add SMSM & SPS
This commit adds the Shared Memory State Machine node to coordinate state
transitions between the Applications processor and the Riva subsystem. It also
adds the SPS SIC non-secure node.
> diff --git a/arch/arm/boot/dts/qcom/qcom-msm8960.dtsi b/arch/arm/boot/dts/qcom/qcom-msm8960.dtsi
> index e215d8809f288..fdc060df45449 100644
> --- a/arch/arm/boot/dts/qcom/qcom-msm8960.dtsi
> +++ b/arch/arm/boot/dts/qcom/qcom-msm8960.dtsi
> @@ -109,6 +109,31 @@ smem {
> hwlocks = <&sfpb_mutex 3>;
> };
>
> + smsm {
> + compatible = "qcom,smsm";
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + qcom,ipc-1 = <&l2cc 8 4>;
> + qcom,ipc-2 = <&l2cc 8 14>;
> + qcom,ipc-3 = <&l2cc 8 23>;
> + qcom,ipc-4 = <&sps_sic_non_secure 0x4094 0>;
This isn't a bug, but the device tree binding schema for qcom,smsm marks
qcom,ipc-1 through qcom,ipc-4 as deprecated.
Is it possible to use the modern mboxes property here instead to model
the cross-processor hardware signaling?
[ ... ]
> @@ -459,6 +484,11 @@ clock-controller@4000000 {
> "hdmipll";
> };
>
> + sps_sic_non_secure: interrupt-controller@12100000 {
Since this node lacks the interrupt-controller property and acts as a syscon,
naming it interrupt-controller@12100000 will trigger dtbs_check warnings.
Should this be renamed to a generic name like syscon@12100000?
> + compatible = "qcom,msm8960-sps-sic", "syscon";
> + reg = <0x12100000 0x10000>;
> + };
> +
> sdcc3: mmc@12180000 {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260514-msm8960-wifi-v2-0-7cbae45dab5e@smankusors.com?part=8
next prev parent reply other threads:[~2026-05-14 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:08 [PATCH v2 00/10] ARM: qcom: msm8960: enable WCNSS (Bluetooth & Wi-Fi) Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 01/10] dt-bindings: clock: qcom,rpmcc: add msm8960 compatible Antony Kurniawan Soemardi via B4 Relay
2026-05-15 6:56 ` Krzysztof Kozlowski
2026-05-14 14:08 ` [PATCH v2 02/10] dt-bindings: mfd: syscon: add qcom,msm8960-sps-sic Antony Kurniawan Soemardi via B4 Relay
2026-05-14 19:40 ` sashiko-bot
2026-05-15 6:57 ` Krzysztof Kozlowski
2026-05-14 14:08 ` [PATCH v2 03/10] mfd: qcom_rpm: add msm8960 QDSS clock resource Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 04/10] clk: qcom: clk-rpm: add msm8960 compatible Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 05/10] ARM: dts: qcom: msm8960: add RPM clock controller and fix USB clocks Antony Kurniawan Soemardi via B4 Relay
2026-05-14 21:01 ` sashiko-bot
2026-05-14 14:08 ` [PATCH v2 06/10] ARM: dts: qcom: msm8960: add SCM Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 07/10] ARM: dts: qcom: msm8960: add SMEM & hwlock Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 08/10] ARM: dts: qcom: msm8960: add SMSM & SPS Antony Kurniawan Soemardi via B4 Relay
2026-05-14 21:41 ` sashiko-bot [this message]
2026-05-14 14:08 ` [PATCH v2 09/10] ARM: dts: qcom: msm8960: add Riva Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 10/10] ARM: dts: qcom: msm8960: huashan: enable Wi-Fi and Bluetooth Antony Kurniawan Soemardi via B4 Relay
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=20260514214139.041E6C2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+linux.smankusors.com@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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