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ć <duje@dujemihanovic.xyz>

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 bb0a993996241d7d849a35107c3bbc87c0df5384..f71bb856f1e7a9ef22a1e3cbbf64bfff636737b0 100644 (file)
--- 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;
                };
        };