rockchip-efuse.txt 1.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647
  1. = Rockchip eFuse device tree bindings =
  2. Required properties:
  3. - compatible: Should be one of the following.
  4. - "rockchip,rk3066a-efuse" - for RK3066a SoCs.
  5. - "rockchip,rk3188-efuse" - for RK3188 SoCs.
  6. - "rockchip,rk3288-efuse" - for RK3288 SoCs.
  7. - "rockchip,rk3399-efuse" - for RK3399 SoCs.
  8. - reg: Should contain the registers location and exact eFuse size
  9. - clocks: Should be the clock id of eFuse
  10. - clock-names: Should be "pclk_efuse"
  11. Deprecated properties:
  12. - compatible: "rockchip,rockchip-efuse"
  13. Old efuse compatible value compatible to rk3066a, rk3188 and rk3288
  14. efuses
  15. = Data cells =
  16. Are child nodes of eFuse, bindings of which as described in
  17. bindings/nvmem/nvmem.txt
  18. Example:
  19. efuse: efuse@ffb40000 {
  20. compatible = "rockchip,rk3288-efuse";
  21. reg = <0xffb40000 0x20>;
  22. #address-cells = <1>;
  23. #size-cells = <1>;
  24. clocks = <&cru PCLK_EFUSE256>;
  25. clock-names = "pclk_efuse";
  26. /* Data cells */
  27. cpu_leakage: cpu_leakage {
  28. reg = <0x17 0x1>;
  29. };
  30. };
  31. = Data consumers =
  32. Are device nodes which consume nvmem data cells.
  33. Example:
  34. cpu_leakage {
  35. ...
  36. nvmem-cells = <&cpu_leakage>;
  37. nvmem-cell-names = "cpu_leakage";
  38. };