From: sashiko-bot@kernel.org
To: "Daniel J Blueman" <daniel@quora.org>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: media: qcom,sm8550-iris: Allow IOVA reservation memory-region
Date: Mon, 01 Jun 2026 04:27:04 +0000 [thread overview]
Message-ID: <20260601042705.6B24C1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260601041336.9497-1-daniel@quora.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding schema fails to enforce the second `memory-region` item (IOVA reservation) for the `qcom,x1e80100-iris` compatible, which strictly requires it to prevent system reboots.
--
commit c0ad29924b6618f643fc065b86b7d5896e42b2ff
Author: Daniel J Blueman <daniel@quora.org>
dt-bindings: media: qcom,sm8550-iris: Allow IOVA reservation memory-region
In addition to the firmware-loaded codec carveout, some Iris platforms
need to declare an IOMMU IOVA reservation (a reserved-memory node with
iommu-addresses) to keep DMA away from IOVA ranges that earlier
firmware stages have already mapped through the SMMU.
> diff --git a/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml b/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
> index 9c4b760508b50..0d83bb86c6c3f 100644
> --- a/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
> +++ b/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
> @@ -80,7 +80,11 @@ properties:
> dma-coherent: true
>
> memory-region:
> - maxItems: 1
> + minItems: 1
> + maxItems: 2
> + items:
> + - description: Firmware-loaded codec carveout
> + - description: IOMMU IOVA reservation region
[Severity: Medium]
Should the schema also enforce minItems: 2 for the qcom,x1e80100-iris
compatible in an allOf conditional block?
The commit message for the subsequent patch ("arm64: dts: qcom: hamoa: Reserve
low IOVA range for Iris") explicitly states that on X1-family hamoa platforms
(which use the qcom,x1e80100-iris compatible), missing the IOVA reservation
causes unhandled SMMU page faults and spontaneous device reboots.
Without an allOf constraint enforcing the second memory region item for this
compatible, incomplete device trees missing the mandatory reservation will pass
schema validation but cause runtime failures.
>
> operating-points-v2: true
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260601041336.9497-1-daniel@quora.org?part=1
next prev parent reply other threads:[~2026-06-01 4:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 4:13 [PATCH 1/2] dt-bindings: media: qcom,sm8550-iris: Allow IOVA reservation memory-region Daniel J Blueman
2026-06-01 4:13 ` [PATCH 2/2] arm64: dts: qcom: hamoa: Reserve low IOVA range for Iris Daniel J Blueman
2026-06-02 10:26 ` Bryan O'Donoghue
2026-06-02 15:03 ` Val Packett
2026-06-02 15:33 ` Bryan O'Donoghue
2026-06-02 15:35 ` Daniel J Blueman
2026-06-04 6:38 ` Vikash Garodia
2026-06-08 3:48 ` Val Packett
2026-06-08 4:17 ` Xilin Wu
2026-06-08 13:36 ` Bryan O'Donoghue
2026-06-09 13:01 ` Bryan O'Donoghue
2026-07-10 10:51 ` Bryan O'Donoghue
2026-06-10 1:14 ` Daniel J Blueman
2026-06-01 4:27 ` sashiko-bot [this message]
2026-06-01 17:45 ` [PATCH 1/2] dt-bindings: media: qcom,sm8550-iris: Allow IOVA reservation memory-region Rob Herring (Arm)
2026-06-04 19:15 ` Frank Li
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=20260601042705.6B24C1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@quora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-media@vger.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