From: Peter Collingbourne <pcc@google.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Will Deacon <will@kernel.org>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Peter Collingbourne <pcc@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH] arm64: dts: fast models: Switch to dynamically allocated VRAM
Date: Thu, 23 Apr 2020 16:49:03 -0700 [thread overview]
Message-ID: <20200423234903.226369-1-pcc@google.com> (raw)
In-Reply-To: <CAMn1gO6Ki=3Znco6xr9h3MhxfTGCH-PYk3V+KxKi_tpNYDzVuA@mail.gmail.com>
According to the Fast Models Reference Manual, FVP has 32MB of video
RAM, However, even 32MB is not sufficient for some applications,
such as Android, which requires around 100-200MB when textures are
allocated in VRAM via DRM.
FVP supports DMA between DRAM and the graphics device. Therefore,
use a dynamically allocated region of reserved memory to provide
a sufficient amount of video RAM. The allocation is of size 256MB,
which ought to be enough for anyone.
Although this means that the designated VRAM ends up being left unused,
FVP allows the size of DRAM to be configurable, so this should not
be a problem in practice.
Signed-off-by: Peter Collingbourne <pcc@google.com>
---
arch/arm64/boot/dts/arm/fvp-base-revc.dts | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/arm/fvp-base-revc.dts b/arch/arm64/boot/dts/arm/fvp-base-revc.dts
index 66381d89c1ce..57641f16f22e 100644
--- a/arch/arm64/boot/dts/arm/fvp-base-revc.dts
+++ b/arch/arm64/boot/dts/arm/fvp-base-revc.dts
@@ -103,11 +103,9 @@ reserved-memory {
#size-cells = <2>;
ranges;
- /* Chipselect 2,00000000 is physically at 0x18000000 */
- vram: vram@18000000 {
- /* 8 MB of designated video RAM */
+ vram: vram {
compatible = "shared-dma-pool";
- reg = <0x00000000 0x18000000 0 0x00800000>;
+ size = <0 0x10000000>;
no-map;
};
};
--
2.26.2.303.gf8c07b1a785-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-23 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 23:14 [PATCH] arm64: dts: fast models: Fix FVP video RAM size Peter Collingbourne
2020-04-23 23:30 ` Peter Collingbourne
2020-04-23 23:49 ` Peter Collingbourne [this message]
2020-04-24 13:20 ` [PATCH] arm64: dts: fast models: Switch to dynamically allocated VRAM Sudeep Holla
2020-04-28 13:06 ` [PATCH] arm64: dts: fast models: Fix FVP video RAM size Linus Walleij
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=20200423234903.226369-1-pcc@google.com \
--to=pcc@google.com \
--cc=kevin.brodsky@arm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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).