BCM270X: Drop position requirement for CMA in VC4 overlay.

No longer necessary since 2aefcd576195a739a7a256099571c9c4a401005f,
and will probably let peeople that want to choose a larger CMA
allocation (particularly on pi0/1).

Signed-off-by: Eric Anholt <eric@anholt.net>

diff --git a/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts b/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts
index c57e795824e9261e0f60bcb40d6a57241019fd91..bf9395041face775d335177583e0b222eb735189 100644 (file)
--- a/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts
+++ b/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts
@@ -13,35 +13,35 @@
        fragment@0 {
                target-path = "/chosen";
                __overlay__ {
-                       bootargs = "cma=256M@256M";
+                       bootargs = "cma=256M";
                };
        };
 
        fragment@1 {
                target-path = "/chosen";
                __dormant__ {
-                       bootargs = "cma=192M@256M";
+                       bootargs = "cma=192M";
                };
        };
 
        fragment@2 {
                target-path = "/chosen";
                __dormant__ {
-                       bootargs = "cma=128M@128M";
+                       bootargs = "cma=128M";
                };
        };
 
        fragment@3 {
                target-path = "/chosen";
                __dormant__ {
-                       bootargs = "cma=96M@128M";
+                       bootargs = "cma=96M";
                };
        };
 
        fragment@4 {
                target-path = "/chosen";
                __dormant__ {
-                       bootargs = "cma=64M@64M";
+                       bootargs = "cma=64M";
                };
        };