summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/nvmem/qcom,sec-qfprom.yaml
blob: 2ada2099946d5feac37c3a338fb27f7aa20ce45e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/nvmem/qcom,sec-qfprom.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Qualcomm Technologies Inc, Secure QFPROM Efuse

maintainers:
  - Komal Bajaj <quic_kbajaj@quicinc.com>

description:
  For some of the Qualcomm SoC's, it is possible that the qfprom region is
  protected from non-secure access. In such situations, the OS have to use
  secure calls to read the region.

allOf:
  - $ref: nvmem.yaml#
  - $ref: nvmem-deprecated-cells.yaml#

properties:
  compatible:
    items:
      - enum:
          - qcom,qdu1000-sec-qfprom
      - const: qcom,sec-qfprom

  reg:
    items:
      - description: The secure qfprom corrected region.

required:
  - compatible
  - reg

unevaluatedProperties: false

examples:
  - |
    soc {
      #address-cells = <2>;
      #size-cells = <2>;

      efuse@221c8000 {
        compatible = "qcom,qdu1000-sec-qfprom", "qcom,sec-qfprom";
        reg = <0 0x221c8000 0 0x1000>;
        #address-cells = <1>;
        #size-cells = <1>;

        multi_chan_ddr: multi-chan-ddr@12b {
          reg = <0x12b 0x1>;
          bits = <0 2>;
        };
      };
    };