From: "Rob Herring (Arm)" <robh@kernel.org>
To: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
Cc: chris.lew@oss.qualcomm.com, dmaengine@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>,
linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Frank Li <Frank.Li@kernel.org>, Andy Gross <agross@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: dma: qcom,bam-dma: Add optional qcom,vmid property
Date: Wed, 22 Jul 2026 10:33:00 -0500 [thread overview]
Message-ID: <178473437962.973796.9171369311202714598.robh@kernel.org> (raw)
In-Reply-To: <20260714-qcom-bam-dma-vmid-ext-v1-1-cef87c57b7dc@oss.qualcomm.com>
On Tue, 14 Jul 2026 10:30:22 +0530, Vishnu Santhosh wrote:
> A SoC can have multiple BAM DMA instances. Some of these BAMs are
> powered by a remote processor that enforces XPU (eXternal Protection
> Unit) access control and reads the per-channel descriptor FIFOs as an
> AXI master under that remote processor's execution environment, so
> their FIFOs must be accessible to the remote processor's VMID; other
> BAM instances on the same SoC are not behind such a remote processor
> and must not have this property set.
>
> Add an optional qcom,vmid property listing the destination VMID(s)
> that the affected BAM instance's descriptor FIFOs must be accessible
> to. HLOS is always the source owner and must not be listed.
>
> Co-developed-by: Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
> Signed-off-by: Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
> Signed-off-by: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
> ---
> .../devicetree/bindings/dma/qcom,bam-dma.yaml | 26 ++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-07-22 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 5:00 [PATCH 0/2] dmaengine: qcom: bam_dma: SCM-assign descriptor FIFOs to a remote VMID Vishnu Santhosh
2026-07-14 5:00 ` [PATCH 1/2] dt-bindings: dma: qcom,bam-dma: Add optional qcom,vmid property Vishnu Santhosh
2026-07-22 15:33 ` Rob Herring (Arm) [this message]
2026-07-14 5:00 ` [PATCH 2/2] dmaengine: qcom: bam_dma: SCM-assign descriptor FIFOs to a remote VMID Vishnu Santhosh
2026-07-23 13:37 ` Konrad Dybcio
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=178473437962.973796.9171369311202714598.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=chris.lew@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=deepak.singh@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishnu.santhosh@oss.qualcomm.com \
--cc=vkoul@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®