From: Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Subject: [RESEND PATCH 0/4] iommu: add qcom_iommu for early "B" family devices
Date: Wed, 9 Aug 2017 10:43:01 -0400 [thread overview]
Message-ID: <20170809144310.22855-1-robdclark@gmail.com> (raw)
An iommu driver for Qualcomm "B" family devices which do implement the
ARM SMMU spec, but not in a way that arm-smmu can support.
(I initially added support to arm-smmu, but it was decided that approach
was too intrusive and it would be cleaner to have a separate driver.)
I should note that all the dependencies for this driver have been merged
since 4.12, and it is the last thing needed for having another fully-
enabled (gpu/display/video codec/etc) ARM device that is fully upstream.
These patches can also be found at:
git://people.freedesktop.org/~robclark/linux qcom_iommu-next
https://cgit.freedesktop.org/~robclark/linux/log/?h=qcom_iommu-next
No change since last time.
Rob Clark (3):
Docs: dt: document qcom iommu bindings
iommu: arm-smmu: split out register defines
iommu: add qcom_iommu
Stanimir Varbanov (1):
iommu: qcom: initialize secure page table
.../devicetree/bindings/iommu/qcom,iommu.txt | 121 +++
drivers/iommu/Kconfig | 10 +
drivers/iommu/Makefile | 1 +
drivers/iommu/arm-smmu-regs.h | 220 +++++
drivers/iommu/arm-smmu.c | 211 +----
drivers/iommu/qcom_iommu.c | 932 +++++++++++++++++++++
6 files changed, 1293 insertions(+), 202 deletions(-)
create mode 100644 Documentation/devicetree/bindings/iommu/qcom,iommu.txt
create mode 100644 drivers/iommu/arm-smmu-regs.h
create mode 100644 drivers/iommu/qcom_iommu.c
--
2.13.0
next reply other threads:[~2017-08-09 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 14:43 Rob Clark [this message]
2017-08-09 14:43 ` [RESEND PATCH 2/4] iommu: arm-smmu: split out register defines Rob Clark
2017-08-10 17:28 ` Will Deacon
2017-08-09 14:43 ` [RESEND PATCH 3/4] iommu: add qcom_iommu Rob Clark
[not found] ` <20170809144310.22855-1-robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-09 14:43 ` [RESEND PATCH 1/4] Docs: dt: document qcom iommu bindings Rob Clark
2017-08-09 14:43 ` [RESEND PATCH 4/4] iommu: qcom: initialize secure page table Rob Clark
-- strict thread matches above, loose matches on Subject: below --
2017-08-09 14:41 [RESEND PATCH 0/4] iommu: add qcom_iommu for early "B" family devices Rob Clark
2017-07-13 12:07 Rob Clark
[not found] ` <20170713120747.20490-1-robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-07-14 8:38 ` Archit Taneja
2017-06-21 12:04 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=20170809144310.22855-1-robdclark@gmail.com \
--to=robdclark-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@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;
as well as URLs for NNTP newsgroup(s).