From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH/RFC 00/09] IPMMU address translation enablement prototype
Date: Wed, 20 Feb 2019 23:55:48 +0900 [thread overview]
Message-ID: <155067454871.15971.12157033067057246708.sendpatchset@octo> (raw)
IPMMU address translation enablement prototype
[PATCH/RFC 01/09] iommu/ipmmu-vmsa: Disable IPMMU when address expansion is not needed
[PATCH/RFC 02/09] iommu/ipmmu-vmsa: Display system memory informationn during boot
[PATCH/RFC 03/09] iommu/ipmmu-vmsa: Introduce keepipmmu boot parameter
[PATCH/RFC 04/09] arm64: dts: renesas: ulcb: Introduce keepipmmu boot parameter
[PATCH/RFC 05/09] arm64: dts: renesas: salvator: Introduce keepipmmu boot parameter
[PATCH/RFC 06/09] arm64: dts: renesas: draak: Introduce keepipmmu boot parameter
[PATCH/RFC 07/09] arm64: dts: renesas: ebisu: Introduce keepipmmu boot parameter
[PATCH/RFC 08/09] arm64: dts: renesas: eagle: Introduce keepipmmu boot parameter
[PATCH/RFC 09/09] arm64: dts: renesas: cat874: Introduce keepipmmu boot parameter
These patches experiment with runtime detection of system memory amount
and location to check if all memory exists within 32 bits physical address
space or not. In case all memory exists within 32 bits then we can assume
address expansion via IPMMU will not be required so the white list code
will simply ignore enablement of IPMMU devices on systems with smaller
amounts of system memory.
Not intended for upstream merge however patch 1/9 might be not so far off.
Not-Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Developed on top of next-20190215
arch/arm64/boot/dts/renesas/r8a774c0-cat874.dts | 2 -
arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 2 -
arch/arm64/boot/dts/renesas/r8a77990-ebisu.dts | 2 -
arch/arm64/boot/dts/renesas/r8a77995-draak.dts | 2 -
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 2 -
arch/arm64/boot/dts/renesas/ulcb.dtsi | 2 -
drivers/iommu/ipmmu-vmsa.c | 29 +++++++++++++++++++++-
7 files changed, 34 insertions(+), 7 deletions(-)
next 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 Magnus Damm [this message]
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 ` [PATCH/RFC 03/09] iommu/ipmmu-vmsa: Introduce keepipmmu boot parameter Magnus Damm
2019-02-20 19:54 ` 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=155067454871.15971.12157033067057246708.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).