nvidia,tegra20-fuse.txt 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. NVIDIA Tegra20/Tegra30/Tegr114/Tegra124 fuse block.
  2. Required properties:
  3. - compatible : For Tegra20, must contain "nvidia,tegra20-efuse". For Tegra30,
  4. must contain "nvidia,tegra30-efuse". For Tegra114, must contain
  5. "nvidia,tegra114-efuse". For Tegra124, must contain "nvidia,tegra124-efuse".
  6. Otherwise, must contain "nvidia,<chip>-efuse", plus one of the above, where
  7. <chip> is tegra132.
  8. Details:
  9. nvidia,tegra20-efuse: Tegra20 requires using APB DMA to read the fuse data
  10. due to a hardware bug. Tegra20 also lacks certain information which is
  11. available in later generations such as fab code, lot code, wafer id,..
  12. nvidia,tegra30-efuse, nvidia,tegra114-efuse and nvidia,tegra124-efuse:
  13. The differences between these SoCs are the size of the efuse array,
  14. the location of the spare (OEM programmable) bits and the location of
  15. the speedo data.
  16. - reg: Should contain 1 entry: the entry gives the physical address and length
  17. of the fuse registers.
  18. - clocks: Must contain an entry for each entry in clock-names.
  19. See ../clocks/clock-bindings.txt for details.
  20. - clock-names: Must include the following entries:
  21. - fuse
  22. - resets: Must contain an entry for each entry in reset-names.
  23. See ../reset/reset.txt for details.
  24. - reset-names: Must include the following entries:
  25. - fuse
  26. Example:
  27. fuse@7000f800 {
  28. compatible = "nvidia,tegra20-efuse";
  29. reg = <0x7000f800 0x400>,
  30. <0x70000000 0x400>;
  31. clocks = <&tegra_car TEGRA20_CLK_FUSE>;
  32. clock-names = "fuse";
  33. resets = <&tegra_car 39>;
  34. reset-names = "fuse";
  35. };