From: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/7] iommu/omap: Add support for iommu-groups and 'struct iommu_device'
Date: Wed, 12 Apr 2017 00:21:25 -0500 [thread overview]
Message-ID: <20170412052132.14406-1-s-anna@ti.com> (raw)
Hi Joerg,
I have taken the liberty of refreshing the series you have posted
based on my testing and review comments. My unit tests are passing
now with the series. I have summarized the changes below and also
outlined the changes in each patch.
Laurent,
I cannot test the OMAP3 ISP, so request you to verify that the
OMAP3ISP driver functionality is maintained. I have created the
last patch separately for now since it's a separate subsystem,
but ideally I think it should go with the patch that adds the
iommu-group support. I am not sure how we want to merge this
patch.
Changes in v3:
* Added 3 new patches
- The first patch now results in the OMAP IOMMU devices being
probed before the callbacks kick in. This allowed me to go
back and use the patches from v1 where the IOMMU groups are
added in probe.
- The second patch drops the non-DT IOMMU device support so
that the name can be dropped from the platform data as well.
- Patch 7 fixes the OMAP3ISP driver after the addition of the
IOMMU group support.
* Squashed the "iommu/omap: Set dev->archdata.iommu = NULL in
omap_iommu_remove_device" patch into Patch 4
* Failure path cleanups in patches 4, 5 and 6
Changes in v2:
* Dropped patch 2 and moved device-link and
group-handling to attach/detach_dev call-backs for
now.
Joerg Roedel (4):
iommu/omap: Move data structures to omap-iommu.h
iommu/omap: Store iommu_dev pointer in arch_data
iommu/omap: Make use of 'struct iommu_device'
iommu/omap: Add iommu-group support
Suman Anna (3):
iommu/omap: Register driver before setting IOMMU ops
iommu/omap: Drop legacy-style device support
[media] omap3isp: Remove iommu_group related code
drivers/iommu/omap-iommu.c | 190 ++++++++++++++++++++-----------
drivers/iommu/omap-iommu.h | 34 ++++++
drivers/media/platform/omap3isp/isp.c | 17 ---
drivers/media/platform/omap3isp/isp.h | 1 -
include/linux/platform_data/iommu-omap.h | 20 ----
5 files changed, 156 insertions(+), 106 deletions(-)
--
2.12.0
next reply other threads:[~2017-04-12 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 5:21 Suman Anna [this message]
[not found] ` <20170412052132.14406-1-s-anna-l0cyMroinI0@public.gmane.org>
2017-04-12 5:21 ` [PATCH v3 1/7] iommu/omap: Register driver before setting IOMMU ops Suman Anna
2017-04-12 5:21 ` [PATCH v3 2/7] iommu/omap: Drop legacy-style device support Suman Anna
2017-04-12 5:21 ` [PATCH v3 3/7] iommu/omap: Move data structures to omap-iommu.h Suman Anna
2017-04-12 5:21 ` [PATCH v3 4/7] iommu/omap: Store iommu_dev pointer in arch_data Suman Anna
2017-04-12 5:21 ` [PATCH v3 5/7] iommu/omap: Make use of 'struct iommu_device' Suman Anna
2017-04-12 5:21 ` [PATCH v3 6/7] iommu/omap: Add iommu-group support Suman Anna
2017-04-12 5:21 ` [PATCH v3 7/7] [media] omap3isp: Remove iommu_group related code Suman Anna
2017-04-20 14:35 ` [PATCH v3 0/7] iommu/omap: Add support for iommu-groups and 'struct iommu_device' 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=20170412052132.14406-1-s-anna@ti.com \
--to=s-anna-l0cymroini0@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@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