From: Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org,
geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org,
Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org
Subject: [PATCH v5 07/07] iommu/ipmmu-vmsa: Drop LPAE Kconfig dependency
Date: Tue, 20 Sep 2016 22:45:06 +0900 [thread overview]
Message-ID: <20160920134506.25470.77154.sendpatchset@little-apple> (raw)
In-Reply-To: <20160920134355.25470.93701.sendpatchset@little-apple>
From: Magnus Damm <damm+renesas-yzvPICuk2ACczHhG9Qg4qA@public.gmane.org>
Neither the ARM page table code enabled by IOMMU_IO_PGTABLE_LPAE
nor the IPMMU_VMSA driver actually depends on ARM_LPAE, so get
rid of the dependency.
Tested with ipmmu-vmsa on r8a7794 ALT and a kernel config using:
# CONFIG_ARM_LPAE is not set
Signed-off-by: Magnus Damm <damm+renesas-yzvPICuk2ACczHhG9Qg4qA@public.gmane.org>
Acked-by: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
---
Changes since V4:
- Rebased patch to fit on top of earlier Kconfig changes in series
Changes since V3:
- None
Changes since V2:
- None
Changes since V1:
- Rebased on top of ARCH_RENESAS change
- Added Acked-by from Laurent
drivers/iommu/Kconfig | 1 -
1 file changed, 1 deletion(-)
--- 0008/drivers/iommu/Kconfig
+++ work/drivers/iommu/Kconfig 2016-09-20 22:13:03.500607110 +0900
@@ -275,7 +275,6 @@ config EXYNOS_IOMMU_DEBUG
config IPMMU_VMSA
bool "Renesas VMSA-compatible IPMMU"
depends on ARM || IOMMU_DMA
- depends on ARM_LPAE
depends on ARCH_RENESAS || COMPILE_TEST
select IOMMU_API
select IOMMU_IO_PGTABLE_LPAE
next prev parent reply other threads:[~2016-09-20 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 13:43 [PATCH v5 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V5 Magnus Damm
2016-09-20 13:44 ` [PATCH v5 01/07] iommu/ipmmu-vmsa: Remove platform data handling Magnus Damm
2016-09-20 13:44 ` [PATCH v5 02/07] iommu/ipmmu-vmsa: Rework interrupt code and use bitmap for context Magnus Damm
2016-09-20 13:44 ` [PATCH v5 03/07] iommu/ipmmu-vmsa: Break out utlb parsing code Magnus Damm
2016-09-20 13:44 ` [PATCH v5 04/07] iommu/ipmmu-vmsa: Break out domain allocation code Magnus Damm
2016-09-20 13:44 ` [PATCH v5 05/07] iommu/ipmmu-vmsa: Add new IOMMU_DOMAIN_DMA ops Magnus Damm
2016-09-22 14:45 ` Joerg Roedel
2016-10-19 23:45 ` Magnus Damm
2016-09-20 13:44 ` [PATCH v5 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access Magnus Damm
2016-09-20 13:45 ` Magnus Damm [this message]
2016-09-22 14:47 ` [PATCH v5 00/07] iommu/ipmmu-vmsa: IPMMU multi-arch update V5 Joerg Roedel
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=20160920134506.25470.77154.sendpatchset@little-apple \
--to=magnus.damm-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org \
--cc=horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@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).