summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/reset/ti,sci-reset.yaml
blob: 1db08ce9ae270d5d1422f2956226d9a47d279dd0 (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
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/reset/ti,sci-reset.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: TI-SCI reset controller

maintainers:
  - Nishanth Menon <nm@ti.com>

description: |
  Some TI SoCs contain a system controller (like the Power Management Micro
  Controller (PMMC) on Keystone 66AK2G SoC) that are responsible for controlling
  the state of the various hardware modules present on the SoC. Communication
  between the host processor running an OS and the system controller happens
  through a protocol called TI System Control Interface (TI-SCI protocol).

  This reset controller node uses the TI SCI protocol to perform the reset
  management of various hardware modules present on the SoC. Must be a child
  node of the associated TI-SCI system controller node.

properties:
  $nodename:
    pattern: "^reset-controller$"

  compatible:
    const: ti,sci-reset

  "#reset-cells":
    const: 2
    description:
      The two cells represent values that the TI-SCI controller defines.

      The first cell should contain the device ID.

      The second cell should contain the reset mask corresponding to the device
      used by system controller.

      Please see https://software-dl.ti.com/tisci/esd/latest/index.html for
      protocol documentation for the values to be used for different devices.


additionalProperties: false

examples:
  - |
    k3_reset: reset-controller {
        compatible = "ti,sci-reset";
        #reset-cells = <2>;
    };