Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Manivannan Sadhasivam" <manivannan.sadhasivam@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 15/22] arm64: dts: qcom: monaco: Fix the PCIe iommu-map entries
Date: Thu, 30 Jul 2026 12:25:16 +0000	[thread overview]
Message-ID: <20260730122516.BB6641F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260730-iommu-map-fix-v1-15-83405d37ba41@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [Medium] Incomplete fix for malformed `iommu-map` entries. The patch series fixes base DTSI files (e.g., `monaco.dtsi`, `lemans.dtsi`) to provide 5-cell `iommu-map` entries when targeting an IOMMU with `#iommu-cells = <2>`. However, it misses board and overlay files that explicitly override `iommu-map` with the old broken 4-cell format. Because these overrides shadow the base DT configuration, compiling these specific boards will still result in the exact same `of: Respect #{iommu,msi}-cells in maps` warning the series intends to resolve.
--

--- Patch [15]: [PATCH 15/22] arm64: dts: qcom: monaco: Fix the PCIe iommu-map entries ---
commit fe3050666c02dc7e846b1c3b4ae001c0063dea37
Author: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>

arm64: dts: qcom: monaco: Fix the PCIe iommu-map entries

This patch updates the PCIe iommu-map entries in monaco.dtsi to use 5 cells,
adding the missing SID mask. This matches the IOMMU provider's
#iommu-cells = <2> property and prevents a warning from the OF core.

> diff --git a/arch/arm64/boot/dts/qcom/monaco.dtsi b/arch/arm64/boot/dts/qcom/monaco.dtsi
> index e4c8466f941bd..799d13d7558f3 100644
> --- a/arch/arm64/boot/dts/qcom/monaco.dtsi
> +++ b/arch/arm64/boot/dts/qcom/monaco.dtsi
> @@ -2349,8 +2349,8 @@ &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
>  			interconnect-names = "pcie-mem",
>  					     "cpu-pcie";
>  
> -			iommu-map = <0x0 &pcie_smmu 0x0000 0x1>,
> -				    <0x100 &pcie_smmu 0x0001 0x1>;
> +			iommu-map = <0x0 &pcie_smmu 0x0000 0x0 0x1>,
> +				    <0x100 &pcie_smmu 0x0001 0x0 0x1>;

[Severity: Medium]
This isn't a bug introduced by this patch, but this fix appears to be
incomplete. Board and overlay files explicitly override iommu-map using the
old 4-cell format, which will shadow this base DT fix and still trigger the
OF core warning.

For example, in arch/arm64/boot/dts/qcom/monaco-monza-som.dtsi:&pcie0:
    iommu-map = <0x0 &pcie_smmu 0x0000 0x1>,

In arch/arm64/boot/dts/qcom/monaco-evk-ifp-mezzanine.dtso:&pcie0:
    iommu-map = <0x0   &pcie_smmu 0x0 0x1>,

And in arch/arm64/boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso:&pcie0:
    iommu-map = <0x0 &pcie_smmu 0x0 0x1>,

Should these files also be updated to use the 5-cell format?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260730-iommu-map-fix-v1-0-83405d37ba41@oss.qualcomm.com?part=15

  reply	other threads:[~2026-07-30 12:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 11:55 [PATCH 00/22] arm64: dts: qcom: Fix the PCIe iommu-map entries Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 01/22] arm64: dts: qcom: kaanapali: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 02/22] arm64: dts: qcom: kodiak: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:08   ` sashiko-bot
2026-07-30 11:55 ` [PATCH 03/22] arm64: dts: qcom: sar2130p: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 04/22] arm64: dts: qcom: sc8180x: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:11   ` sashiko-bot
2026-07-30 11:55 ` [PATCH 05/22] arm64: dts: qcom: sdm845: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 06/22] arm64: dts: qcom: sm8150: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 07/22] arm64: dts: qcom: sm8250: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:06   ` sashiko-bot
2026-07-30 11:55 ` [PATCH 08/22] arm64: dts: qcom: sm8350: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 09/22] arm64: dts: qcom: sm8450: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:04   ` sashiko-bot
2026-07-30 11:55 ` [PATCH 10/22] arm64: dts: qcom: sm8550: " Manivannan Sadhasivam via B4 Relay
2026-07-30 13:39   ` Neil Armstrong
2026-07-30 11:55 ` [PATCH 11/22] arm64: dts: qcom: sm8650: " Manivannan Sadhasivam via B4 Relay
2026-07-30 13:39   ` Neil Armstrong
2026-07-30 11:55 ` [PATCH 12/22] arm64: dts: qcom: sm8750: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 13/22] arm64: dts: qcom: talos: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:07   ` sashiko-bot
2026-07-30 11:55 ` [PATCH 14/22] arm64: dts: qcom: lemans: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 15/22] arm64: dts: qcom: monaco: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:25   ` sashiko-bot [this message]
2026-07-30 11:55 ` [PATCH 16/22] arm64: dts: qcom: monaco-monza-som: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:55 ` [PATCH 17/22] arm64: dts: qcom: monaco-evk-ifp-mezzanine: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:09   ` sashiko-bot
2026-07-30 11:55 ` [PATCH 18/22] arm64: dts: qcom: lemans-evk-ifp-mezzanine: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:56 ` [PATCH 19/22] arm64: dts: qcom: qcs6490-radxa-dragon-q6a: " Manivannan Sadhasivam via B4 Relay
2026-07-30 11:56 ` [PATCH 20/22] arm64: dts: qcom: qcs6490-thundercomm-minipc-g1iot: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:29   ` sashiko-bot
2026-07-30 11:56 ` [PATCH 21/22] arm64: dts: qcom: qcs6490-rb3gen2: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:12   ` sashiko-bot
2026-07-30 11:56 ` [PATCH 22/22] arm64: dts: qcom: qcs6490-rb3gen2-industrial-mezzanine: " Manivannan Sadhasivam via B4 Relay
2026-07-30 12:23 ` [PATCH 00/22] arm64: dts: qcom: " Dmitry Baryshkov
2026-07-30 16:14   ` Manivannan Sadhasivam
2026-07-30 16:25     ` Dmitry Baryshkov
2026-07-30 12:46 ` Konrad Dybcio

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=20260730122516.BB6641F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=manivannan.sadhasivam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox