blob: 2ada2099946d5feac37c3a338fb27f7aa20ce45e [file] [log] [blame]
Tom Rini53633a82024-02-29 12:33:36 -05001# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2%YAML 1.2
3---
4$id: http://devicetree.org/schemas/nvmem/qcom,sec-qfprom.yaml#
5$schema: http://devicetree.org/meta-schemas/core.yaml#
6
7title: Qualcomm Technologies Inc, Secure QFPROM Efuse
8
9maintainers:
10 - Komal Bajaj <quic_kbajaj@quicinc.com>
11
12description:
13 For some of the Qualcomm SoC's, it is possible that the qfprom region is
14 protected from non-secure access. In such situations, the OS have to use
15 secure calls to read the region.
16
17allOf:
18 - $ref: nvmem.yaml#
19 - $ref: nvmem-deprecated-cells.yaml#
20
21properties:
22 compatible:
23 items:
24 - enum:
25 - qcom,qdu1000-sec-qfprom
26 - const: qcom,sec-qfprom
27
28 reg:
29 items:
30 - description: The secure qfprom corrected region.
31
32required:
33 - compatible
34 - reg
35
36unevaluatedProperties: false
37
38examples:
39 - |
40 soc {
41 #address-cells = <2>;
42 #size-cells = <2>;
43
44 efuse@221c8000 {
45 compatible = "qcom,qdu1000-sec-qfprom", "qcom,sec-qfprom";
46 reg = <0 0x221c8000 0 0x1000>;
47 #address-cells = <1>;
48 #size-cells = <1>;
49
50 multi_chan_ddr: multi-chan-ddr@12b {
51 reg = <0x12b 0x1>;
52 bits = <0 2>;
53 };
54 };
55 };
56