From: Magnus Damm <magnus.damm@gmail.com>
To: iommu@lists.linux-foundation.org
Cc: laurent.pinchart+renesas@ideasonboard.com,
geert+renesas@glider.be, joro@8bytes.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
horms+renesas@verge.net.au, Magnus Damm <magnus.damm@gmail.com>,
robin.murphy@arm.com, m.szyprowski@samsung.com
Subject: [PATCH v4 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V4
Date: Wed, 08 Jun 2016 16:17:37 +0900 [thread overview]
Message-ID: <20160608071737.7560.32571.sendpatchset@little-apple> (raw)
iommu/ipmmu-vmsa: IPMMU multi-arch update V4
[PATCH v4 01/07] iommu/ipmmu-vmsa: Remove platform data handling
[PATCH v4 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context
[PATCH v4 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code
[PATCH v4 04/07] iommu/ipmmu-vmsa: Break out domain allocation code
[PATCH v4 05/07] iommu/ipmmu-vmsa: Add new IOMMU_DOMAIN_DMA ops
[PATCH v4 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access
[PATCH v4 07/07] iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency
These patches update the IPMMU driver with a couple of changes
to support build on multiple architectures. In the process of
doing so the interrupt code gets reworked and the foundation
for supporting multiple contexts are added.
Changes since V3:
- Updated patch 3/7 to fix hang-on-boot issue on 32-bit ARM - thanks Geert!
- Reworked group parameter handling in patch 3/7 and 5/7.
- Added patch 6/7 to fix build of the driver on s390/tile/um architectures
Changes since V2:
- Got rid of patch 3 from the V2 however patch 1, 2 and 4 are kept.
- V3 patch 3, 4 and 5 come from
[PATCH 00/04] iommu/ipmmu-vmsa: IPMMU CONFIG_IOMMU_DMA update
- Patch 5 has been reworked to include patch 3 of the V1 of this series
Changes since V1:
- Got rid of patch 2 and 3 from initial series
- Updated bitmap code locking and also used lighter bitop functions
- Updated the Kconfig bits to apply on top of ARCH_RENESAS
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
drivers/iommu/Kconfig | 1
drivers/iommu/ipmmu-vmsa.c | 302 +++++++++++++++++++++++++++++++++++---------
2 files changed, 243 insertions(+), 60 deletions(-)
next reply other threads:[~2016-06-08 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 7:17 Magnus Damm [this message]
2016-06-08 7:17 ` [PATCH v4 01/07] iommu/ipmmu-vmsa: Remove platform data handling Magnus Damm
2016-06-08 7:17 ` [PATCH v4 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context Magnus Damm
2016-06-08 7:18 ` [PATCH v4 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code Magnus Damm
2016-06-08 7:18 ` [PATCH v4 04/07] iommu/ipmmu-vmsa: Break out domain allocation code Magnus Damm
2016-06-08 7:18 ` [PATCH v4 05/07] iommu/ipmmu-vmsa: Add new IOMMU_DOMAIN_DMA ops Magnus Damm
2016-06-08 7:18 ` [PATCH v4 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access Magnus Damm
2016-06-08 7:18 ` [PATCH v4 07/07] iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency Magnus Damm
2016-06-10 6:55 ` [PATCH v4 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V4 Geert Uytterhoeven
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=20160608071737.7560.32571.sendpatchset@little-apple \
--to=magnus.damm@gmail.com \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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).