From: sashiko-bot@kernel.org
To: "Loic Poulain" <loic.poulain@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
media-ci@linuxtv.org
Subject: Re: [PATCH v9 7/9] arm64: dts: qcom: agatti: Add OPE node
Date: Wed, 23 Sep 2026 16:15:51 +0000 [thread overview]
Message-ID: <20260923161551.986A21F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260923-camss-isp-ope-v9-7-86a75dc18b83@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: overlapping iommu stream IDs artificially merge IOMMU groups
--
commit f837397d169ca6bd9f29b986ea39a8a6e4ab9b26
Author: Loic Poulain <loic.poulain@oss.qualcomm.com>
arm64: dts: qcom: agatti: Add OPE node
Add the Offline Processing Engine (OPE) device tree node for the
Agatti platform (QCM2290).
> diff --git a/arch/arm64/boot/dts/qcom/agatti.dtsi b/arch/arm64/boot/dts/qcom/agatti.dtsi
> index 590bd2432d85b..69237959adc15 100644
> --- a/arch/arm64/boot/dts/qcom/agatti.dtsi
> +++ b/arch/arm64/boot/dts/qcom/agatti.dtsi
> @@ -1984,6 +1984,83 @@ port@1 {
> };
> };
>
> + isp_ope: isp@5c42000 {
> + compatible = "qcom,qcm2290-camss-ope";
[ ... ]
> + interconnect-names = "config",
> + "data";
> +
> + iommus = <&apps_smmu 0x800 0x0>,
> + <&apps_smmu 0x820 0x0>,
> + <&apps_smmu 0x840 0x0>;
[Severity: Medium]
Does this create a resource conflict with the existing camss node?
The newly added isp_ope node claims stream IDs 0x800, 0x820, and 0x840,
but these IDs are already claimed by the sibling camss node:
camss {
...
iommus = <&apps_smmu 0x400 0x0>,
<&apps_smmu 0x800 0x0>,
<&apps_smmu 0x820 0x0>,
<&apps_smmu 0x840 0x0>;
...
}
Because these overlapping stream IDs are unconditionally parsed during boot,
arm_smmu_master_alloc_smes detects the exact SMR overlap and forcefully
places both distinct platform devices into the exact same IOMMU group.
Will this artificially intertwine their DMA domains, break device isolation,
and cause both drivers to map IOVAs into a shared context?
Should the OPE stream IDs be removed from the camss node since OPE is now
split into its own distinct platform device?
> +
> + operating-points-v2 = <&ope_opp_table>;
> + power-domains = <&gcc GCC_CAMSS_TOP_GDSC>,
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923-camss-isp-ope-v9-0-86a75dc18b83@oss.qualcomm.com?part=7
next prev parent reply other threads:[~2026-09-23 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 16:00 [PATCH v9 0/9] media: qcom: camss: CAMSS Offline Processing Engine support Loic Poulain
2026-09-23 16:00 ` [PATCH v9 1/9] media: qcom: camss: Add V4L2 meta format for CAMSS ISP parameters Loic Poulain
2026-09-23 16:00 ` [PATCH v9 2/9] dt-bindings: media: qcom: Add CAMSS Offline Processing Engine (OPE) Loic Poulain
2026-09-23 16:00 ` [PATCH v9 3/9] dt-bindings: media: qcom,qcm2290-camss-ope: Document shikra compatible Loic Poulain
2026-09-23 16:00 ` [PATCH v9 4/9] media: uapi: Add CAMSS ISP configuration definition Loic Poulain
2026-09-23 16:00 ` [PATCH v9 5/9] media: Documentation: uapi: Add qcom-camss ISP params documentation Loic Poulain
2026-09-23 16:00 ` [PATCH v9 6/9] media: qcom: camss: Add CAMSS Offline Processing Engine driver Loic Poulain
2026-09-23 16:26 ` sashiko-bot
2026-09-23 16:00 ` [PATCH v9 7/9] arm64: dts: qcom: agatti: Add OPE node Loic Poulain
2026-09-23 16:15 ` sashiko-bot [this message]
2026-09-23 16:00 ` [PATCH v9 8/9] arm64: dts: qcom: shikra: " Loic Poulain
2026-09-23 16:00 ` [PATCH v9 9/9] arm64: defconfig: Enable Qualcomm CAMSS OPE driver Loic Poulain
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=20260923161551.986A21F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=media-ci@linuxtv.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 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.