From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pratyush Meduri <pratyush.meduri@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: remoteproc: qcom,pas-common: allow up to 3 iommus
Date: Mon, 20 Jul 2026 08:10:41 +0200 [thread overview]
Message-ID: <20260720-steadfast-swinging-shrimp-196ac6@quoll> (raw)
In-Reply-To: <20260717095825.3962666-2-pratyush.meduri@oss.qualcomm.com>
On Fri, Jul 17, 2026 at 03:28:23PM +0530, Pratyush Meduri wrote:
> The ADSP PAS on several Qualcomm SoCs (e.g. SA8775P/lemans, QCS8300,
> Monaco) needs more than a single SMMU stream ID for the audio ML
> (machine-learning) offload use case. In addition to the primary
> ADSP stream ID, the DSP/SPF issues DMA transactions through extra
> stream IDs that are not covered by the existing single-entry mapping.
>
> Relax the iommus constraint to allow between 1 and 3 entries so the
> additional ML offload stream IDs can be described, fixing dtb_check
> schema violations on device trees that add them.
What dtb_check violations? Do not reference non-existing warnings. If
this is real, then place the warning here - and be sure we can actually
reproduce it.
>
> Signed-off-by: Pratyush Meduri <pratyush.meduri@oss.qualcomm.com>
> ---
> .../devicetree/bindings/remoteproc/qcom,pas-common.yaml | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml
> index 11faf655f530..fb656bda8527 100644
> --- a/Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,pas-common.yaml
> @@ -33,7 +33,8 @@ properties:
> maxItems: 6
>
> iommus:
> - maxItems: 1
> + minItems: 1
> + maxItems: 3
So now all devices have three streams as well? Or only these three? You
said only newer, so why are you raising this also for sm8150?
Beside, you need to list the items.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-20 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 9:58 [PATCH v2 0/3] arm64: dts: qcom: enable audio ML offload Pratyush Meduri
2026-07-17 9:58 ` [PATCH v2 1/3] dt-bindings: remoteproc: qcom,pas-common: allow up to 3 iommus Pratyush Meduri
2026-07-20 6:10 ` Krzysztof Kozlowski [this message]
2026-07-17 9:58 ` [PATCH v2 2/3] arm64: dts: qcom: lemans: enable audio ML offload memory and SMMU mappings Pratyush Meduri
2026-07-17 10:11 ` sashiko-bot
2026-07-20 6:12 ` Krzysztof Kozlowski
2026-07-17 9:58 ` [PATCH v2 3/3] arm64: dts: qcom: monaco: " Pratyush Meduri
2026-07-17 10:13 ` sashiko-bot
2026-07-20 6:12 ` Krzysztof Kozlowski
2026-07-21 11:23 ` Pratyush Meduri
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=20260720-steadfast-swinging-shrimp-196ac6@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=pratyush.meduri@oss.qualcomm.com \
--cc=robh@kernel.org \
/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