From: Duje Mihanović Date: Thu, 9 Apr 2026 21:17:25 +0000 (+0200) Subject: arm64: dts: marvell: samsung,coreprimevelte: Use memory-region for framebuffer X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cfb4346423eb5dab498546d617a8c444b878bff3;p=thirdparty%2Fkernel%2Flinux.git arm64: dts: marvell: samsung,coreprimevelte: Use memory-region for framebuffer Since the framebuffer resides in system RAM, use the memory-region property preferred in that case over reg. Also, testing showed that reusing most of the region (excluding where the actual framebuffer resides) is perfectly safe, so do that and save ~22.5 MiB of RAM in the process. Signed-off-by: Duje Mihanović --- diff --git a/arch/arm64/boot/dts/marvell/mmp/pxa1908-samsung-coreprimevelte.dts b/arch/arm64/boot/dts/marvell/mmp/pxa1908-samsung-coreprimevelte.dts index bb0a993996241..f71bb856f1e7a 100644 --- a/arch/arm64/boot/dts/marvell/mmp/pxa1908-samsung-coreprimevelte.dts +++ b/arch/arm64/boot/dts/marvell/mmp/pxa1908-samsung-coreprimevelte.dts @@ -23,7 +23,7 @@ fb0: framebuffer@17177000 { compatible = "simple-framebuffer"; - reg = <0 0x17177000 0 (480 * 800 * 4)>; + memory-region = <&fb_mem>; power-domains = <&apmu PXA1908_POWER_DOMAIN_DSI>; width = <480>; height = <800>; @@ -48,8 +48,9 @@ reg = <0 0 0 0x1000000>; }; - framebuffer@17000000 { - reg = <0 0x17000000 0 0x1800000>; + /* The "active buffer" is at 0x17000000 + (size of one buffer). */ + fb_mem: framebuffer@17177000 { + reg = <0 0x17177000 0 (480 * 800 * 4)>; no-map; }; };