arm64: dts: meson: g12a: add secure monitor and efuse
Subsystems (2)
Jerome Brunet
reviewercover arm64: dts: meson: g12a: add secure monitor and efuse
This patchset adds the secure monitor and efuse to the g12a SoC family. These are sent together because the secure monitor is required for the efuse driver to work properly. This is probably something the bindings should show but it was not designed that way when the secure monitor was introduced ... something to look at someday.
Jerome Brunet (2):
arm64: dts: meson: g12a: add secure monitor
arm64: dts: meson: g12a: add efuse
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 13 +++++++++++++ 1 file changed, 13 insertions(+)
Signature · 1 line
2.20.1
Jerome Brunet
reviewerPATCH 1/2 arm64: dts: meson: g12a: add secure monitor
Add the interface to the secure monitor on g12a
--- arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 4 ++++ 1 file changed, 4 insertions(+)
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi +4 -0
@@ -72,6 +72,10 @@ }; }; + sm: secure-monitor { + compatible = "amlogic,meson-gxbb-sm"; + }; + soc { compatible = "simple-bus"; #address-cells = <2>;
Signature · 1 line
2.20.1
Jerome Brunet
reviewerPATCH 2/2 arm64: dts: meson: g12a: add efuse
In reply to Jerome BrunetAdd the g12a SoC efuse device
--- arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 9 +++++++++ 1 file changed, 9 insertions(+)
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi +9 -0
@@ -4,6 +4,7 @@ */ #include <dt-bindings/gpio/gpio.h> +#include <dt-bindings/clock/g12a-clkc.h> #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/interrupt-controller/arm-gic.h>
@@ -55,6 +56,14 @@ }; }; + efuse: efuse { + compatible = "amlogic,meson-gxbb-efuse"; + clocks = <&clkc CLKID_EFUSE>; + #address-cells = <1>; + #size-cells = <1>; + read-only; + }; + psci { compatible = "arm,psci-1.0"; method = "smc";
Signature · 1 line
2.20.1
Quoted 5 lines · Jerome Brunet
This patchset adds the secure monitor and efuse to the g12a SoC family. These are sent together because the secure monitor is required for the efuse driver to work properly. This is probably something the bindings should show but it was not designed that way when the secure monitor was introduced ... something to look at someday.
Queued for v5.2 (branch: v5.2/dt64)
Thanks,
Kevin