Re: [PATCH v5 1/3] dt-bindings: remoteproc: Move iommus constraint to SoC-specific bindings
From: Komal Bajaj
Date: Wed Nov 18 2026 - 01:53:29 EST
On 11/17/2026 9:22 PM, Mukesh Ojha wrote:
On Mon, Nov 16, 2026 at 11:58:20AM +0100, Krzysztof Kozlowski wrote:
On Fri, Nov 13, 2026 at 08:02:20PM +0530, Komal Bajaj wrote:@Komal,
qcom,pas-common.yaml limits iommus to a single entry for every PASI do not understand this sentence. Compatible cannot declare iommus, but
remoteproc, which is too restrictive for SoCs whose firmware uses
multiple IOMMU streams.
Drop iommus from common binding and let each SoC-specific binding declare
it with its own limits. These bindings set unevaluatedProperties: false,
so a compatible that does not declare iommus rejects it. Declare it for
anyway the bindings do not reject it.
Yeah, this patch should prepare for the 2nd patch, so ideally this should
be a no functional change patch. Any constraints change should be a
separate change. So, ideally, this should be removing from the common PAS
and adding it to every SoC PAS YAML that inherits qcom,pas-common.yaml.
Ack, agree. I will update this accordingly and keep it as a no-functional-change.
Thanks
Komal
-Mukesh