From: Sameer Pujar <spujar@nvidia.com>
To: <vkoul@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <dmaengine@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ldewangan@nvidia.com>, <mkumard@nvidia.com>, <spujar@nvidia.com>
Subject: [RESEND PATCH 0/2] Virtualization support for Tegra ADMA
Date: Tue, 21 May 2024 11:07:59 +0000 [thread overview]
Message-ID: <20240521110801.1692582-1-spujar@nvidia.com> (raw)
From: Mohan Kumar <mkumard@nvidia.com>
Tegra ADMA HW supports multiple PAGES for virtualization, to
support virtualization
- reg-names property has been added to DT binding for the hypervisor mode.
- In hypervisor mode the ADMA global registers are not accessed by guest.
Mohan Kumar (2):
dt-bindings: dma: Add reg-names to nvidia,tegra210-adma
dmaengine: tegra210-adma: Add support for ADMA virtualization
.../bindings/dma/nvidia,tegra210-adma.yaml | 10 +++++
drivers/dma/tegra210-adma.c | 44 +++++++++++++++----
2 files changed, 46 insertions(+), 8 deletions(-)
--
2.45.1
next reply other threads:[~2024-05-21 11:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 11:07 Sameer Pujar [this message]
2024-05-21 11:08 ` [RESEND PATCH 1/2] dt-bindings: dma: Add reg-names to nvidia,tegra210-adma Sameer Pujar
2024-05-21 11:53 ` Krzysztof Kozlowski
2024-05-22 5:35 ` Sameer Pujar
2024-05-22 6:47 ` Krzysztof Kozlowski
2024-05-22 7:43 ` Sameer Pujar
2024-05-22 11:29 ` Krzysztof Kozlowski
2024-05-24 7:36 ` Thierry Reding
2024-05-28 6:48 ` Krzysztof Kozlowski
2024-05-30 12:48 ` Thierry Reding
2024-05-31 7:43 ` Krzysztof Kozlowski
2024-05-31 9:06 ` Thierry Reding
2024-05-28 15:35 ` Rob Herring
2024-05-30 12:29 ` Thierry Reding
2024-05-21 11:08 ` [RESEND PATCH 2/2] dmaengine: tegra210-adma: Add support for ADMA virtualization Sameer Pujar
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=20240521110801.1692582-1-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).