Path: blob/main/sys/contrib/device-tree/Bindings/fuse/nvidia,tegra20-fuse.txt
48377 views
NVIDIA Tegra20/Tegra30/Tegr114/Tegra124 fuse block.12Required properties:3- compatible : For Tegra20, must contain "nvidia,tegra20-efuse". For Tegra30,4must contain "nvidia,tegra30-efuse". For Tegra114, must contain5"nvidia,tegra114-efuse". For Tegra124, must contain "nvidia,tegra124-efuse".6For Tegra132 must contain "nvidia,tegra132-efuse", "nvidia,tegra124-efuse".7For Tegra210 must contain "nvidia,tegra210-efuse". For Tegra186 must contain8"nvidia,tegra186-efuse". For Tegra194 must contain "nvidia,tegra194-efuse".9For Tegra234 must contain "nvidia,tegra234-efuse".10Details:11nvidia,tegra20-efuse: Tegra20 requires using APB DMA to read the fuse data12due to a hardware bug. Tegra20 also lacks certain information which is13available in later generations such as fab code, lot code, wafer id,..14nvidia,tegra30-efuse, nvidia,tegra114-efuse and nvidia,tegra124-efuse:15The differences between these SoCs are the size of the efuse array,16the location of the spare (OEM programmable) bits and the location of17the speedo data.18- reg: Should contain 1 entry: the entry gives the physical address and length19of the fuse registers.20- clocks: Must contain an entry for each entry in clock-names.21See ../clocks/clock-bindings.txt for details.22- clock-names: Must include the following entries:23- fuse24- resets: Must contain an entry for each entry in reset-names.25See ../reset/reset.txt for details.26- reset-names: Must include the following entries:27- fuse2829Example:3031fuse@7000f800 {32compatible = "nvidia,tegra20-efuse";33reg = <0x7000f800 0x400>,34<0x70000000 0x400>;35clocks = <&tegra_car TEGRA20_CLK_FUSE>;36clock-names = "fuse";37resets = <&tegra_car 39>;38reset-names = "fuse";39};4041424344