From: Joerg Roedel <joro@8bytes.org>
To: Suman Anna <s-anna@ti.com>, iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>
Subject: [PATCH 0/5] iommu/omap: Add support for iommu-groups and 'struct iommu_device'
Date: Fri, 31 Mar 2017 14:10:43 +0200 [thread overview]
Message-ID: <1490962248-12602-1-git-send-email-joro@8bytes.org> (raw)
Hi,
here is a small patch-set for the omap-iommu driver to make
it use new features of the iommu-core. Please review.
Thanks,
Joerg
Joerg Roedel (5):
iommu/omap: Move data structures to omap-iommu.h
iommu/omap: Permanently keep iommu_dev pointer in arch_data
iommu/omap: Set dev->archdata.iommu = NULL in omap_iommu_remove_device
iommu/omap: Make use of 'struct iommu_device'
iommu/omap: Add iommu-group support
drivers/iommu/omap-iommu.c | 137 ++++++++++++++++++++-----------
drivers/iommu/omap-iommu.h | 35 ++++++++
include/linux/platform_data/iommu-omap.h | 15 ----
3 files changed, 124 insertions(+), 63 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-31 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 12:10 Joerg Roedel [this message]
2017-03-31 12:10 ` [PATCH 1/5] iommu/omap: Move data structures to omap-iommu.h Joerg Roedel
2017-04-03 17:22 ` Suman Anna
2017-03-31 12:10 ` [PATCH 2/5] iommu/omap: Permanently keep iommu_dev pointer in arch_data Joerg Roedel
2017-04-03 20:35 ` Suman Anna
2017-04-07 14:35 ` Joerg Roedel
2017-03-31 12:10 ` [PATCH 3/5] iommu/omap: Set dev->archdata.iommu = NULL in omap_iommu_remove_device Joerg Roedel
2017-04-03 18:25 ` Suman Anna
2017-03-31 12:10 ` [PATCH 4/5] iommu/omap: Make use of 'struct iommu_device' Joerg Roedel
2017-03-31 12:10 ` [PATCH 5/5] iommu/omap: Add iommu-group support Joerg Roedel
2017-04-03 17:09 ` [PATCH 0/5] iommu/omap: Add support for iommu-groups and 'struct iommu_device' Suman Anna
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=1490962248-12602-1-git-send-email-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s-anna@ti.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