Linux IOMMU Development
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [PATCH v2 0/3] Add support for ARM SMMU architectures 1 and 2
Date: Mon, 24 Jun 2013 18:31:23 +0100	[thread overview]
Message-ID: <1372095086-15681-1-git-send-email-will.deacon@arm.com> (raw)

Hello again,

This is version 2 of the patches I originally posted here:

  http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/175128.html

Changes since v1 include:
  - Dropped the first six preparatory patches, since they've been picked
    up by their respective trees.
  - Fixed arm_smmu_devices list locking and removed unnecessary use of
    _safe list iterators
  - Added calculation of compound output mask to domain initialisation,
    rather than iterate up the SMMU chain during the ->map fast path
  - Added timeout to TLB invalidation loop
  - Expanded comment about non-coherent table walking
  - Renamed arm_smmu_create_mapping to arm_smmu_handle_mapping

Thanks to everybody who was reviewed the patches so far!

All comments welcome,

Will

Will Deacon (3):
  documentation: iommu: add description of ARM System MMU binding
  iommu: add support for ARM Ltd. System MMU architecture
  MAINTAINERS: add entry for ARM system MMU driver

 .../devicetree/bindings/iommu/arm,smmu.txt         |   70 +
 MAINTAINERS                                        |    6 +
 drivers/iommu/Kconfig                              |   13 +
 drivers/iommu/Makefile                             |    1 +
 drivers/iommu/arm-smmu.c                           | 1969 ++++++++++++++++++++
 5 files changed, 2059 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/iommu/arm,smmu.txt
 create mode 100644 drivers/iommu/arm-smmu.c

-- 
1.8.2.2

             reply	other threads:[~2013-06-24 17:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 17:31 Will Deacon [this message]
     [not found] ` <1372095086-15681-1-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-06-24 17:31   ` [PATCH v2 1/3] documentation: iommu: add description of ARM System MMU binding Will Deacon
     [not found]     ` <1372095086-15681-2-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-06-25 21:24       ` Andreas Herrmann
2013-06-24 17:31   ` [PATCH v2 2/3] iommu: add support for ARM Ltd. System MMU architecture Will Deacon
     [not found]     ` <1372095086-15681-3-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-06-25 21:25       ` Andreas Herrmann
2013-06-26  9:00         ` Will Deacon
2013-07-08 16:34       ` Olav Haugan
     [not found]         ` <51DAEA0F.2030808-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-07-09  7:48           ` Will Deacon
2013-06-24 17:31   ` [PATCH v2 3/3] MAINTAINERS: add entry for ARM system MMU driver Will Deacon
2013-06-26  9:48   ` [PATCH v2 0/3] Add support for ARM SMMU architectures 1 and 2 Joerg Roedel
     [not found]     ` <20130626094805.GS11309-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-06-26 11:32       ` Will Deacon

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=1372095086-15681-1-git-send-email-will.deacon@arm.com \
    --to=will.deacon-5wv7dgnigg8@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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