From: Joerg Roedel <joro@8bytes.org>
To: Hiroshi Doyu <hdoyu@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>
Subject: [PATCH 0/2] iommu/tegra*: Add support for struct iommu_device
Date: Thu, 10 Aug 2017 00:29:10 +0200 [thread overview]
Message-ID: <1502317752-8792-1-git-send-email-joro@8bytes.org> (raw)
Hi,
here are two patches to add support for 'struct iommu_device'
to the tegra iommu-drivers. This will make the iommu-core
code aware of the hardware iommus that a driver manages.
It will also add the iommus to sysfs and link them to the
devices managed by them.
The patches apply on-top of Robin's iommu-group patches.
Please review.
Regards,
Joerg
Joerg Roedel (2):
iommu/tegra: Add support for struct iommu_device
iommu/tegra-gart: Add support for struct iommu_device
drivers/iommu/tegra-gart.c | 26 ++++++++++++++++++++++++++
drivers/iommu/tegra-smmu.c | 25 +++++++++++++++++++++++++
2 files changed, 51 insertions(+)
--
2.7.4
next reply other threads:[~2017-08-09 22:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 22:29 Joerg Roedel [this message]
2017-08-09 22:29 ` [PATCH 1/2] iommu/tegra: Add support for struct iommu_device Joerg Roedel
2017-08-18 12:47 ` Thierry Reding
2017-08-30 11:04 ` Jon Hunter
2017-08-30 12:09 ` Joerg Roedel
2017-08-30 14:22 ` Jon Hunter
2017-08-30 15:30 ` Joerg Roedel
2017-08-30 16:53 ` Jon Hunter
2017-08-31 10:23 ` Jon Hunter
2017-08-09 22:29 ` [PATCH 2/2] iommu/tegra-gart: " Joerg Roedel
2017-08-16 22:21 ` Dmitry Osipenko
2017-08-17 13:52 ` Thierry Reding
2017-08-17 17:17 ` Dmitry Osipenko
2017-08-18 12:47 ` Thierry Reding
2017-08-17 13:58 ` [PATCH 0/2] iommu/tegra*: " Thierry Reding
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=1502317752-8792-1-git-send-email-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=hdoyu@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).