From: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
To: linux-remoteproc@vger.kernel.org
Cc: mathieu.poirier@linaro.org, andersson@kernel.org,
linux-kernel@vger.kernel.org
Subject: Query: DMA device assigned to remoteproc usage by Linux
Date: Mon, 23 Dec 2024 23:27:50 +0530 [thread overview]
Message-ID: <CAN3W6UVqqY1P+0ZV3nwY-vmT3fArGhoF959H_15K3iz1z7shSw@mail.gmail.com> (raw)
Hi All,
Wanted to check if we have encountered remoteproc use case where a device
with dma is assigned to a remoteproc with its own streamid and iommu
translation context. This DMA device can have a selective DMA range
within the remoteproc carveout memory that needs to be iommu mapped
before the remoteproc is up.
Do we have any example in remoteproc that handles such scenario where
device dma (assigned to remoteproc) has its iommu setup by Linux (since
the iommu is under its control) ?
I was exploring some of the remoteproc drivers but did not find anything
close to DMA use case and from where remoteproc should get this ddr range ?
device tree ? or rsc table ? if rsc table then which among the below ?
enum fw_resource_type {
RSC_CARVEOUT = 0,
RSC_DEVMEM = 1,
RSC_TRACE = 2,
RSC_VDEV = 3,
RSC_LAST = 4,
RSC_VENDOR_START = 128,
RSC_VENDOR_END = 512,
-Mukesh
next reply other threads:[~2024-12-23 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 17:57 Mukesh Ojha [this message]
2025-01-20 6:39 ` Query: DMA device assigned to remoteproc usage by Linux Mukesh Ojha
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=CAN3W6UVqqY1P+0ZV3nwY-vmT3fArGhoF959H_15K3iz1z7shSw@mail.gmail.com \
--to=mukesh.ojha@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).