Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) = Amlogic Meson GX eFuse device tree bindings =
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) Required properties:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) - compatible: should be "amlogic,meson-gxbb-efuse"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) - clocks: phandle to the efuse peripheral clock provided by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) 	  clock controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) - secure-monitor: phandle to the secure-monitor node
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) = Data cells =
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) Are child nodes of eFuse, bindings of which as described in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) bindings/nvmem/nvmem.txt
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) Example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) 	efuse: efuse {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) 		compatible = "amlogic,meson-gxbb-efuse";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) 		clocks = <&clkc CLKID_EFUSE>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) 		#address-cells = <1>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) 		#size-cells = <1>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) 		secure-monitor = <&sm>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) 		sn: sn@14 {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) 			reg = <0x14 0x10>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) 		};
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) 		eth_mac: eth_mac@34 {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) 			reg = <0x34 0x10>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) 		};
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) 		bid: bid@46 {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) 			reg = <0x46 0x30>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) 		};
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) 	};
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) 	sm: secure-monitor {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) 		compatible = "amlogic,meson-gxbb-sm";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) 	};
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) = Data consumers =
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) Are device nodes which consume nvmem data cells.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) For example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) 	eth_mac {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) 		...
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) 		nvmem-cells = <&eth_mac>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) 		nvmem-cell-names = "eth_mac";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) 	};