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: Fix FVP video RAM size
Date: Tue, 21 Apr 2020 16:14:03 -0700 [thread overview]
Message-ID: <20200421231403.199217-1-pcc@google.com> (raw)
According to the Fast Models Reference Manual, FVP has 32MB of video
RAM starting at physical address 0x18000000, but the DTS only declares
8MB. Fix that.
Signed-off-by: Peter Collingbourne <pcc@google.com>
---
arch/arm64/boot/dts/arm/fvp-base-revc.dts | 4 ++--
1 file changed, 2 insertions(+), 2 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..72c018188c40 100644
--- a/arch/arm64/boot/dts/arm/fvp-base-revc.dts
+++ b/arch/arm64/boot/dts/arm/fvp-base-revc.dts
@@ -105,9 +105,9 @@ reserved-memory {
/* Chipselect 2,00000000 is physically at 0x18000000 */
vram: vram@18000000 {
- /* 8 MB of designated video RAM */
+ /* 32 MB of designated video RAM */
compatible = "shared-dma-pool";
- reg = <0x00000000 0x18000000 0 0x00800000>;
+ reg = <0x00000000 0x18000000 0 0x02000000>;
no-map;
};
};
--
2.26.1.301.g55bc3eb7cb9-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-04-21 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 23:14 Peter Collingbourne [this message]
2020-04-23 23:30 ` [PATCH] arm64: dts: fast models: Fix FVP video RAM size Peter Collingbourne
2020-04-23 23:49 ` [PATCH] arm64: dts: fast models: Switch to dynamically allocated VRAM Peter Collingbourne
2020-04-24 13:20 ` 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=20200421231403.199217-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).