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,rk3228-efuse" - for RK3228 SoCs.
   8   - "rockchip,rk3288-efuse" - for RK3288 SoCs.
   9   - "rockchip,rk3328-efuse" - for RK3328 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 Optional properties:
  17 - rockchip,efuse-size: Should be exact eFuse size in byte, the eFuse
  18   size in property <reg> will be invalid if define this property.
  19
  20 Deprecated properties:
  21 - compatible: "rockchip,rockchip-efuse"
  22   Old efuse compatible value compatible to rk3066a, rk3188 and rk3288
  23   efuses
  24
  25 = Data cells =
  26 Are child nodes of eFuse, bindings of which as described in
  27 bindings/nvmem/nvmem.txt
  28
  29 Example:
  30
  31         efuse: efuse@ffb40000 {
  32                 compatible = "rockchip,rk3288-efuse";
  33                 reg = <0xffb40000 0x20>;
  34                 #address-cells = <1>;
  35                 #size-cells = <1>;
  36                 clocks = <&cru PCLK_EFUSE256>;
  37                 clock-names = "pclk_efuse";
  38
  39                 /* Data cells */
  40                 cpu_leakage: cpu_leakage {
  41                         reg = <0x17 0x1>;
  42                 };
  43         };
  44
  45 = Data consumers =
  46 Are device nodes which consume nvmem data cells.
  47
  48 Example:
  49
  50         cpu_leakage {
  51                 ...
  52                 nvmem-cells = <&cpu_leakage>;
  53                 nvmem-cell-names = "cpu_leakage";
  54         };