From: sashiko-bot@kernel.org
To: "Mukesh Ojha" <mukesh.ojha@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: qcom: Introduce Hawi SoC
Date: Tue, 22 Sep 2026 20:38:18 +0000 [thread overview]
Message-ID: <20260922203818.E7BE11F0089C@smtp.kernel.org> (raw)
In-Reply-To: <20260923-hawi-dt-post-v1-3-e41473b6298b@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] dt: pcie iommu-map property missing mask cell
--
commit b9bce85781ff89249270f3214ceed073984ef78e
Author: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
arm64: dts: qcom: Introduce Hawi SoC
This commit introduces the device tree definition for the Qualcomm Hawi SoC.
It adds a large number of nodes including CPUs, interrupts, timers, reserved
memory, interconnects, SMMU, PCIe, USB, thermal zones, and remoteprocs.
> diff --git a/arch/arm64/boot/dts/qcom/hawi.dtsi b/arch/arm64/boot/dts/qcom/hawi.dtsi
> new file mode 100644
> index 0000000000000..c7ae8133b9cdc
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/hawi.dtsi
[ ... ]
> @@ -2957,8 +2957,8 @@
>
> operating-points-v2 = <&pcie0_opp_table>;
>
> + iommu-map = <0 &apps_smmu 0x1000 0x1>,
> + <0x100 &apps_smmu 0x1001 0x1>;
[Severity: High]
Are we missing a mask cell for the SMMU specifier in this iommu-map property?
The apps_smmu node defines #iommu-cells = <2>, which means the iommu-map
array requires 5 cells per tuple (rid-base, phandle, iommu-base-high,
iommu-base-low, length). Providing only 4 cells per tuple can cause the
parser to misalign the tuples, treating the length as part of the iommu-base
mask and stealing the next tuple's rid-base for the length. This completely
breaks parsing of the IOMMU specifier and results in broken PCIe DMA
translation.
> +
> + interrupt-map = <0 0 0 1 &intc 0 0 GIC_ESPI 213 IRQ_TYPE_LEVEL_HIGH>,
[ ... ]
> @@ -3139,8 +3139,8 @@
>
> operating-points-v2 = <&pcie1_opp_table>;
>
> + iommu-map = <0 &apps_smmu 0x1080 0x1>,
> + <0x100 &apps_smmu 0x1081 0x1>;
[Severity: High]
Is this iommu-map array similarly missing a mask cell for the SMMU
specifier?
As with the pcie0 node above, providing 4 cells per tuple when 5 are
expected can cause parsing issues that break the IOMMU specifier.
> +
> + interrupt-map = <0 0 0 1 &intc 0 0 GIC_ESPI 106 IRQ_TYPE_LEVEL_HIGH>,
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923-hawi-dt-post-v1-0-e41473b6298b@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-09-22 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:18 [PATCH 0/4] arm64: dts: qcom: Introduce Qualcomm Hawi platform device tree Mukesh Ojha
2026-09-22 20:18 ` [PATCH 1/4] dt-bindings: arm: cpus: Add Oryon PartNum 3 CPU compatibles Mukesh Ojha
2026-09-22 20:18 ` [PATCH 2/4] arm64: dts: qcom: hawi: Add header file for IPCC physical client IDs Mukesh Ojha
2026-09-22 20:18 ` [PATCH 3/4] arm64: dts: qcom: Introduce Hawi SoC Mukesh Ojha
2026-09-22 20:38 ` sashiko-bot [this message]
2026-09-23 17:36 ` Mukesh Ojha
2026-09-23 10:41 ` Konrad Dybcio
2026-09-23 13:03 ` Mukesh Ojha
2026-09-22 20:18 ` [PATCH 4/4] arm64: dts: qcom: hawi: Add base MTP board Mukesh Ojha
2026-09-22 20:39 ` sashiko-bot
2026-09-23 13:04 ` Mukesh Ojha
2026-09-23 10:42 ` Konrad Dybcio
2026-09-23 12:59 ` Mukesh Ojha
2026-09-24 1:06 ` (subset) [PATCH 0/4] arm64: dts: qcom: Introduce Qualcomm Hawi platform device tree Bjorn Andersson
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=20260922203818.E7BE11F0089C@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--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 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.