nvmem: rockchip-efuse: add rk3366-efuse support
[firefly-linux-kernel-4.4.55.git] / 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,rk3366-efuse" - for RK3366 SoCs.
9   - "rockchip,rk3399-efuse" - for RK3399 SoCs.
10 - reg: Should contain the registers location and exact eFuse size
11 - clocks: Should be the clock id of eFuse
12 - clock-names: Should be "pclk_efuse"
13
14 Deprecated properties:
15 - compatible: "rockchip,rockchip-efuse"
16   Old efuse compatible value compatible to rk3066a, rk3188 and rk3288
17   efuses
18
19 = Data cells =
20 Are child nodes of eFuse, bindings of which as described in
21 bindings/nvmem/nvmem.txt
22
23 Example:
24
25         efuse: efuse@ffb40000 {
26                 compatible = "rockchip,rk3288-efuse";
27                 reg = <0xffb40000 0x20>;
28                 #address-cells = <1>;
29                 #size-cells = <1>;
30                 clocks = <&cru PCLK_EFUSE256>;
31                 clock-names = "pclk_efuse";
32
33                 /* Data cells */
34                 cpu_leakage: cpu_leakage {
35                         reg = <0x17 0x1>;
36                 };
37         };
38
39 = Data consumers =
40 Are device nodes which consume nvmem data cells.
41
42 Example:
43
44         cpu_leakage {
45                 ...
46                 nvmem-cells = <&cpu_leakage>;
47                 nvmem-cell-names = "cpu_leakage";
48         };