Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt

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