From: Olav Haugan <ohaugan@codeaurora.org>
To: joro@8bytes.org
Cc: robdclark@gmail.com, will.deacon@arm.com,
thierry.reding@gmail.com, iommu@lists.linux-foundation.org,
linux-arm-msm@vger.kernel.org, mitchelh@codeaurora.org,
Olav Haugan <ohaugan@codeaurora.org>
Subject: [PATCH v2 0/1] Add iommu map_range/unmap_range calls
Date: Wed, 16 Jul 2014 18:01:56 -0700 [thread overview]
Message-ID: <1405558917-7597-1-git-send-email-ohaugan@codeaurora.org> (raw)
Patch for adding map_range/unmap range to the generic IOMMU API.
v1 -> v2:
* Added support for "option" argument to unmap call. This can be used by
IOMMU driver implentations to allow clients to signal to the driver not
to do TLB invalidate for example.
* Added fallback in case iommu_{map,unmap}_range is called for an IOMMU driver
that does not have these implemented.
* Rebased on top of Joerg's tree.
* Split out patch from the rest of the patches.
Olav Haugan (1):
iommu-api: Add map_range/unmap_range functions
drivers/iommu/iommu.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
include/linux/iommu.h | 25 +++++++++++++++++++++++++
2 files changed, 73 insertions(+)
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-07-17 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 1:01 Olav Haugan [this message]
2014-07-17 1:01 ` [PATCH v2 1/1] iommu-api: Add map_range/unmap_range functions Olav Haugan
[not found] ` <1405558917-7597-2-git-send-email-ohaugan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-17 8:21 ` Thierry Reding
2014-07-22 0:59 ` Olav Haugan
[not found] ` <53CDB76A.5090602-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-22 7:45 ` Thierry Reding
2014-07-23 17:49 ` Olav Haugan
[not found] ` <53CFF5C3.5060600-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-24 9:34 ` Joerg Roedel
[not found] ` <20140724093427.GH14017-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-07-24 10:07 ` Thierry Reding
2014-07-24 10:14 ` Thierry Reding
2014-07-22 15:07 ` Rob Clark
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=1405558917-7597-1-git-send-email-ohaugan@codeaurora.org \
--to=ohaugan@codeaurora.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mitchelh@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.