blob: 94aeeeabadd5309b809e888605ff5816f8f51df3 [file] [log] [blame]
ZhengShunQianfaf25a92015-09-30 13:56:36 +01001= Rockchip eFuse device tree bindings =
2
3Required properties:
Finley Xiaob3149f42016-09-02 10:14:26 +01004- 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,rk3399-efuse" - for RK3399 SoCs.
ZhengShunQianfaf25a92015-09-30 13:56:36 +01009- reg: Should contain the registers location and exact eFuse size
10- clocks: Should be the clock id of eFuse
11- clock-names: Should be "pclk_efuse"
12
Finley Xiaob3149f42016-09-02 10:14:26 +010013Deprecated properties:
14- compatible: "rockchip,rockchip-efuse"
15 Old efuse compatible value compatible to rk3066a, rk3188 and rk3288
16 efuses
17
ZhengShunQianfaf25a92015-09-30 13:56:36 +010018= Data cells =
19Are child nodes of eFuse, bindings of which as described in
20bindings/nvmem/nvmem.txt
21
22Example:
23
24 efuse: efuse@ffb40000 {
Finley Xiaob3149f42016-09-02 10:14:26 +010025 compatible = "rockchip,rk3288-efuse";
ZhengShunQianfaf25a92015-09-30 13:56:36 +010026 reg = <0xffb40000 0x20>;
27 #address-cells = <1>;
28 #size-cells = <1>;
29 clocks = <&cru PCLK_EFUSE256>;
30 clock-names = "pclk_efuse";
31
32 /* Data cells */
33 cpu_leakage: cpu_leakage {
34 reg = <0x17 0x1>;
35 };
36 };
37
38= Data consumers =
39Are device nodes which consume nvmem data cells.
40
41Example:
42
43 cpu_leakage {
44 ...
45 nvmem-cells = <&cpu_leakage>;
46 nvmem-cell-names = "cpu_leakage";
47 };