arch/arm64: add FRAMEBUFFER region macros to memlayout

BRANCH=none
BUG=chrome-os-partner:51537
TEST=build pass

Change-Id: Id3dd3a553370eada1e79708dc71afc2d94d6ce93
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 0949b0d9ec12eff7edb3d7de738833f29507c332
Original-Change-Id: I8052f86d4d846e5d544911c5b9e323285083fb5c
Original-Signed-off-by: Lin Huang <hl@rock-chips.com>
Original-Reviewed-on: https://chromium-review.googlesource.com/340024
Original-Commit-Ready: Vadim Bendebury <vbendeb@google.com>
Original-Tested-by: Shunqian Zheng <zhengsq@rock-chips.com>
Original-Reviewed-by: Vadim Bendebury <vbendeb@google.com>
Reviewed-on: https://review.coreboot.org/14747
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
This commit is contained in:
Lin Huang 2016-03-31 18:38:48 +08:00 committed by Patrick Georgi
parent 5f4f36116d
commit 03f50720df

View file

@ -27,6 +27,11 @@
_ = ASSERT(size % 4K == 0, \
"DMA buffer should be multiple of smallest page size (4K)!");
#define FRAMEBUFFER(addr, size) \
REGION(framebuffer, addr, size, 1M) \
_ = ASSERT(size % 1M == 0, \
"Framebuffer must fit exactly in 1M!");
/* ARM64 stacks need 16-byte alignment. */
#define STACK(addr, size) \
REGION(stack, addr, size, 16) \