blob: 194926f77194c4d3fea8e73942bd1f20ae361815 [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.
Finley Xiao820de1f2017-06-09 10:59:10 +01007 - "rockchip,rk322x-efuse" - for RK322x SoCs.
Finley Xiaob3149f42016-09-02 10:14:26 +01008 - "rockchip,rk3288-efuse" - for RK3288 SoCs.
9 - "rockchip,rk3399-efuse" - for RK3399 SoCs.
ZhengShunQianfaf25a92015-09-30 13:56:36 +010010- 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
Finley Xiaob3149f42016-09-02 10:14:26 +010014Deprecated properties:
15- compatible: "rockchip,rockchip-efuse"
16 Old efuse compatible value compatible to rk3066a, rk3188 and rk3288
17 efuses
18
ZhengShunQianfaf25a92015-09-30 13:56:36 +010019= Data cells =
20Are child nodes of eFuse, bindings of which as described in
21bindings/nvmem/nvmem.txt
22
23Example:
24
25 efuse: efuse@ffb40000 {
Finley Xiaob3149f42016-09-02 10:14:26 +010026 compatible = "rockchip,rk3288-efuse";
ZhengShunQianfaf25a92015-09-30 13:56:36 +010027 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 =
40Are device nodes which consume nvmem data cells.
41
42Example:
43
44 cpu_leakage {
45 ...
46 nvmem-cells = <&cpu_leakage>;
47 nvmem-cell-names = "cpu_leakage";
48 };