From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH/RFC 03/09] iommu/ipmmu-vmsa: Introduce keepipmmu boot parameter
Date: Wed, 20 Feb 2019 23:56:17 +0900 [thread overview]
Message-ID: <155067457726.15971.1787990365004385103.sendpatchset@octo> (raw)
In-Reply-To: <155067454871.15971.12157033067057246708.sendpatchset@octo>
From: Magnus Damm <damm+renesas@opensource.se>
Introduce a keepipmmu boot paramenter to let the user override.
Not-Yet-Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
drivers/iommu/ipmmu-vmsa.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
--- 0004/drivers/iommu/ipmmu-vmsa.c
+++ work/drivers/iommu/ipmmu-vmsa.c 2019-02-20 23:17:54.038850305 +0900
@@ -759,6 +759,17 @@ static int ipmmu_init_platform_device(st
return 0;
}
+
+static int keep_ipmmu;
+
+static int __init keepipmmu_setup(char *__unused)
+{
+ keep_ipmmu = 1;
+ return 1;
+}
+
+__setup("keepipmmu", keepipmmu_setup);
+
static const struct soc_device_attribute soc_rcar_gen3[] = {
{ .soc_id = "r8a774a1", },
{ .soc_id = "r8a774c0", },
@@ -802,7 +813,8 @@ static bool ipmmu_slave_whitelist(struct
* then assume the IPMMU will not be needed for address expansion.
*/
if (memblock_end_of_DRAM() <= SZ_4G)
- return false;
+ if (!keep_ipmmu)
+ return false;
/* Check whether this slave device can work with the IPMMU */
for (i = 0; i < ARRAY_SIZE(rcar_gen3_slave_whitelist); i++) {
next prev parent reply other threads:[~2019-02-20 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 14:55 [PATCH/RFC 00/09] IPMMU address translation enablement prototype Magnus Damm
2019-02-20 14:55 ` [PATCH/RFC 01/09] iommu/ipmmu-vmsa: Disable IPMMU when address expansion is not needed Magnus Damm
2019-02-20 16:09 ` Geert Uytterhoeven
2019-03-19 13:45 ` Magnus Damm
2019-03-19 14:07 ` Geert Uytterhoeven
2019-02-20 14:56 ` [PATCH/RFC 02/09] iommu/ipmmu-vmsa: Display system memory informationn during boot Magnus Damm
2019-02-20 14:56 ` Magnus Damm [this message]
2019-02-20 19:54 ` [PATCH/RFC 03/09] iommu/ipmmu-vmsa: Introduce keepipmmu boot parameter Geert Uytterhoeven
2019-02-20 14:56 ` [PATCH/RFC 04/09] arm64: dts: renesas: ulcb: " Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 05/09] arm64: dts: renesas: salvator: " Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 06/09] arm64: dts: renesas: draak: " Magnus Damm
2019-02-20 14:56 ` [PATCH/RFC 07/09] arm64: dts: renesas: ebisu: " Magnus Damm
2019-02-20 14:57 ` [PATCH/RFC 08/09] arm64: dts: renesas: eagle: " Magnus Damm
2019-02-20 14:57 ` [PATCH/RFC 09/09] arm64: dts: renesas: cat874: " Magnus Damm
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=155067457726.15971.1787990365004385103.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=linux-renesas-soc@vger.kernel.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).