From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/4] IOMMU group cleanup
Date: Fri, 21 Jul 2017 13:12:34 +0100 [thread overview]
Message-ID: <cover.1500637633.git.robin.murphy@arm.com> (raw)
Hi all,
Prompted by some discussion around the questionable usefulness of
iommu_present() for SoC topologies, I took a look at what was left to
finish off the intention of making groups mandatory. Turns out it
wasn't much, so here it is. As well as the general rationalisation
aspect, between this and the probe-deferral changes in 4.12, we should
now be able to rely on the presence of a group unambiguously indicating
whether a given device is associated with an IOMMU or not.
Robin.
Robin Murphy (4):
iommu/msm: Add iommu_group support
iommu/tegra-smmu: Add iommu_group support
iommu/tegra-gart: Add iommu_group support
iommu: Finish making iommu_group support mandatory
drivers/iommu/iommu.c | 19 ++++---------------
drivers/iommu/msm_iommu.c | 15 ++++++++++++++-
drivers/iommu/tegra-gart.c | 19 +++++++++++++++++++
drivers/iommu/tegra-smmu.c | 9 +++++++++
4 files changed, 46 insertions(+), 16 deletions(-)
--
2.12.2.dirty
next reply other threads:[~2017-07-21 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 12:12 Robin Murphy [this message]
[not found] ` <cover.1500637633.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-07-21 12:12 ` [PATCH 1/4] iommu/msm: Add iommu_group support Robin Murphy
[not found] ` <b87d44e09fa18efbb9daf6258c1f8ecbedaac23c.1500637633.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-07-24 7:34 ` Sricharan R
[not found] ` <f5071164-c965-b6bf-c330-90ff6ea0c956-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-07-24 9:55 ` Robin Murphy
[not found] ` <e148ac58-2fda-454f-c8b1-e01dd1c1347c-5wv7dgnIgG8@public.gmane.org>
2017-07-26 15:29 ` Sricharan R
2017-07-21 12:12 ` [PATCH 2/4] iommu/tegra-smmu: " Robin Murphy
2017-08-02 8:12 ` Mikko Perttunen
2017-07-21 12:12 ` [PATCH 3/4] iommu/tegra-gart: " Robin Murphy
[not found] ` <9c3fa9661e8177f0ccea960dd584a05fc19f92c8.1500637633.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-07-26 20:56 ` Dmitry Osipenko
2017-07-21 12:12 ` [PATCH 4/4] iommu: Finish making iommu_group support mandatory Robin Murphy
2017-07-26 11:12 ` [PATCH 0/4] IOMMU group cleanup Joerg Roedel
2017-08-11 15:21 ` Joerg Roedel
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=cover.1500637633.git.robin.murphy@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).