From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Relax PAS iommus item limit
Date: Mon, 5 Oct 2026 15:20:24 +0530 [thread overview]
Message-ID: <9f049a54-96cc-485d-85c1-58ee3c1cbd2a@oss.qualcomm.com> (raw)
In-Reply-To: <20261001-ordinary-cheerful-velociraptor-80c793@quoll>
On 10/1/2026 2:03 PM, Krzysztof Kozlowski wrote:
> On Wed, Sep 30, 2026 at 05:19:03PM +0530, Komal Bajaj wrote:
>> Some PAS users require more than one IOMMU mapping. Update
>> qcom,pas-common.yaml to allow up to three iommus entries so
>> PAS bindings can represent multi-stream mappings used by
>> platform device trees and avoid dt-schema array length failures.
> This is incomplete. You just added two more iommus to all devices. You
> need constraints and proper user of this.
I see your point. This change relaxes constraint for all targets, which
is broader than intended.
I will rework this and add required Shikra specific constraints in next
revision.
Thanks
Komal
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-10-05 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:49 [PATCH v2 0/2] arm64: dts: qcom: shikra: Add EL2 overlay for EVK variants Komal Bajaj
2026-09-30 11:49 ` [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Relax PAS iommus item limit Komal Bajaj
2026-10-01 8:33 ` Krzysztof Kozlowski
2026-10-05 9:50 ` Komal Bajaj [this message]
2026-09-30 11:49 ` [PATCH v2 2/2] arm64: dts: qcom: shikra: Add EL2 overlay for remoteproc SMMU mappings Komal Bajaj
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=9f049a54-96cc-485d-85c1-58ee3c1cbd2a@oss.qualcomm.com \
--to=komal.bajaj@oss.qualcomm.com \
--cc=abelvesa@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=krzk@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=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
all inboxes | Powered by JetHome®