mediatek: fix mt7530 mcm reset
authorJohn Crispin <john@phrozen.org>
Sat, 29 Apr 2017 07:48:35 +0000 (09:48 +0200)
committerJohn Crispin <john@phrozen.org>
Sat, 29 Apr 2017 07:48:35 +0000 (09:48 +0200)
Early SoC versions with an ECO of 1 required the gpio reset.
Mass production SoCs no longer need this work around.

Signed-off-by: John Crispin <john@phrozen.org>
target/linux/mediatek/files/arch/arm/boot/dts/mt7623-NAND-ePHY.dts
target/linux/mediatek/files/arch/arm/boot/dts/mt7623-NAND.dts
target/linux/mediatek/files/arch/arm/boot/dts/mt7623-eMMC.dts

index 035bdf5..1278b8b 100644 (file)
 
                core-supply = <&mt6323_vpa_reg>;
                io-supply = <&mt6323_vemc3v3_reg>;
-               reset-gpios = <&pio 33 0>;
+
+               mediatek,mcm;
+               resets = <&ethsys 2>;
+               reset-names = "mcm";
 
                ports {
                        #address-cells = <1>;
index 072ebe7..6606176 100644 (file)
 
                core-supply = <&mt6323_vpa_reg>;
                io-supply = <&mt6323_vemc3v3_reg>;
-               reset-gpios = <&pio 33 0>;
+
+               mediatek,mcm;
+               resets = <&ethsys 2>;
+               reset-names = "mcm";
 
                ports {
                        #address-cells = <1>;
index 36b0065..fe1a42d 100644 (file)
 
                core-supply = <&mt6323_vpa_reg>;
                io-supply = <&mt6323_vemc3v3_reg>;
-               reset-gpios = <&pio 33 0>;
+
+               mediatek,mcm;
+               resets = <&ethsys 2>;
+               reset-names = "mcm";
 
                ports {
                        #address-cells = <1>;