From: Krishna Reddy <vdumpa@nvidia.com>
To: will.deacon@arm.com, robin.murphy@arm.com, joro@8bytes.org
Cc: linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, treding@nvidia.com, yhsu@nvidia.com,
snikam@nvidia.com, praithatha@nvidia.com, talho@nvidia.com,
avanbrunt@nvidia.com, nicolinc@nvidia.com,
Krishna Reddy <vdumpa@nvidia.com>
Subject: [PATCH v2 0/5] Add Tegra194 Dual ARM SMMU driver
Date: Wed, 31 Oct 2018 16:43:45 -0700 [thread overview]
Message-ID: <1541029430-14150-1-git-send-email-vdumpa@nvidia.com> (raw)
NVIDIA's Xavier (Tegra194) SOC has three ARM SMMU(MMU-500) instances.
Two of the SMMU instances are used to interleave IOVA accesses across them.
The IOVA accesses from HW devices are interleaved across these two SMMU instances
and they need to be programmed identical.
The existing ARM SMMU driver can't be used in its current form for programming the
two SMMU instances identically. But, most of the code can be shared between ARM SMMU
driver and Tegra194 SMMU driver.
Page fault handling and TLB sync operations need to know about specific instance
of SMMU for correct fault handling and optimal TLB sync wait. Rest of the code doesn't
need to know about number of SMMU instances. Based on this fact, The patch series here
rearranges the arm-smmu.c code to allow sharing most of the ARM SMMU programming/iommu_ops
code between ARM SMMU driver and Tegra194 SMMU driver and transparently
handles programming of two SMMU instances.
The third SMMU instance would use the existing ARM SMMU driver.
Changes in v2:
* Added CONFIG_ARM_SMMU_TEGRA to protect Tegra194 SMMU driver compilation
* Enabled CONFIG_ARM_SMMU_TEGRA in defconfig
* Added SMMU nodes in Tegra194 device tree
Krishna Reddy (5):
iommu/arm-smmu: rearrange arm-smmu.c code
iommu/arm-smmu: Prepare fault, probe, sync functions for sharing code
iommu/tegra194_smmu: Add Tegra194 SMMU driver
arm64: defconfig: Enable ARM_SMMU_TEGRA
arm64: tegra: Add SMMU nodes to Tegra194 device tree
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 148 ++
arch/arm64/configs/defconfig | 1 +
drivers/iommu/Kconfig | 10 +
drivers/iommu/Makefile | 1 +
drivers/iommu/arm-smmu-common.c | 1971 +++++++++++++++++++++++++++
drivers/iommu/arm-smmu-common.h | 256 ++++
drivers/iommu/arm-smmu.c | 2167 +-----------------------------
drivers/iommu/tegra194-smmu.c | 201 +++
8 files changed, 2595 insertions(+), 2160 deletions(-)
create mode 100644 drivers/iommu/arm-smmu-common.c
create mode 100644 drivers/iommu/arm-smmu-common.h
create mode 100644 drivers/iommu/tegra194-smmu.c
--
2.1.4
next reply other threads:[~2018-10-31 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 23:43 Krishna Reddy [this message]
2018-11-26 23:58 ` [PATCH v2 0/5] Add Tegra194 Dual ARM SMMU driver Olof Johansson
2018-11-27 2:30 ` Krishna Reddy
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=1541029430-14150-1-git-send-email-vdumpa@nvidia.com \
--to=vdumpa@nvidia.com \
--cc=avanbrunt@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=praithatha@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=snikam@nvidia.com \
--cc=talho@nvidia.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
--cc=yhsu@nvidia.com \
/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