From: Anup Patel <anup.patel@broadcom.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will.deacon@arm.com>,
Robin Murphy <Robin.Murphy@arm.com>,
Sricharan R <sricharan@codeaurora.org>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Device Tree <devicetree@vger.kernel.org>,
Scott Branden <sbranden@broadcom.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Ray Jui <rjui@broadcom.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Vikram Prakash <vikramp@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Kumar Gala <galak@codeaurora.org>,
Anup Patel <anup.patel@broadcom.com>
Subject: [PATCH v2 0/4] iommu/arm-smmu: misc fixes for SMMUv1/SMMUv2
Date: Mon, 8 Feb 2016 10:47:28 +0530 [thread overview]
Message-ID: <1454908652-15317-1-git-send-email-anup.patel@broadcom.com> (raw)
The intention behind this patchset is to allow usage of IOMMU based
DMA mappings for 32bit devices. It is based on '4.5-rc3' tag of linux
mainline tree and Robin's SMMU patchset "[PATCH 0/4] Miscellaneous
ARM SMMU patches".
This patchset and its dependent patches are available in smmu_v2
branch of https://github.com/Broadcom/arm64-linux.git
All patches have been tested on Broadcom SoCs having SMMU-500.
Anup Patel (3):
iommu/arm-smmu: Invoke DT probe from arm_smmu_of_setup()
of: iommu: Increment DT node refcount in of_iommu_set_ops()
iommu/arm-smmu: Add stub of_xlate() operation in SMMUv1/SMMUv2 driver
Sricharan R (1):
iommu/arm-smmu: Init driver using IOMMU_OF_DECLARE
drivers/iommu/arm-smmu.c | 52 ++++++++++++++++++++++++++++++++++++------------
drivers/iommu/of_iommu.c | 1 +
2 files changed, 40 insertions(+), 13 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-08 5:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 5:17 Anup Patel [this message]
2016-02-08 5:17 ` [PATCH v2 1/4] iommu/arm-smmu: Init driver using IOMMU_OF_DECLARE Anup Patel
2016-02-08 5:17 ` [PATCH v2 2/4] iommu/arm-smmu: Invoke DT probe from arm_smmu_of_setup() Anup Patel
2016-02-18 12:00 ` Sricharan
2016-02-19 3:14 ` Anup Patel
2016-02-08 5:17 ` [PATCH v2 3/4] of: iommu: Increment DT node refcount in of_iommu_set_ops() Anup Patel
2016-02-08 5:17 ` [PATCH v2 4/4] iommu/arm-smmu: Add stub of_xlate() operation in SMMUv1/SMMUv2 driver Anup Patel
[not found] ` <1454908652-15317-5-git-send-email-anup.patel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-02-08 11:18 ` Mark Rutland
2016-02-08 12:41 ` Anup Patel
2016-02-08 12:43 ` Anup Patel
[not found] ` <CAALAos94ZHTKF5Gvjt7b56Yq+ZhhSSCN3xLdOWEpRvsrFohW6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-08 13:42 ` Mark Rutland
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=1454908652-15317-1-git-send-email-anup.patel@broadcom.com \
--to=anup.patel@broadcom.com \
--cc=Robin.Murphy@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=sricharan@codeaurora.org \
--cc=vikramp@broadcom.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 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).