xref: /freebsd/sys/contrib/device-tree/Bindings/power/domain-idle-state.yaml (revision c66ec88fed842fbaad62c30d510644ceb7bd2d71)
1*c66ec88fSEmmanuel Vadot# SPDX-License-Identifier: GPL-2.0
2*c66ec88fSEmmanuel Vadot%YAML 1.2
3*c66ec88fSEmmanuel Vadot---
4*c66ec88fSEmmanuel Vadot$id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
5*c66ec88fSEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml#
6*c66ec88fSEmmanuel Vadot
7*c66ec88fSEmmanuel Vadottitle: PM Domain Idle States binding description
8*c66ec88fSEmmanuel Vadot
9*c66ec88fSEmmanuel Vadotmaintainers:
10*c66ec88fSEmmanuel Vadot  - Ulf Hansson <ulf.hansson@linaro.org>
11*c66ec88fSEmmanuel Vadot
12*c66ec88fSEmmanuel Vadotdescription:
13*c66ec88fSEmmanuel Vadot  A domain idle state node represents the state parameters that will be used to
14*c66ec88fSEmmanuel Vadot  select the state when there are no active components in the PM domain.
15*c66ec88fSEmmanuel Vadot
16*c66ec88fSEmmanuel Vadotproperties:
17*c66ec88fSEmmanuel Vadot  $nodename:
18*c66ec88fSEmmanuel Vadot    const: domain-idle-states
19*c66ec88fSEmmanuel Vadot
20*c66ec88fSEmmanuel VadotpatternProperties:
21*c66ec88fSEmmanuel Vadot  "^(cpu|cluster|domain)-":
22*c66ec88fSEmmanuel Vadot    type: object
23*c66ec88fSEmmanuel Vadot    description:
24*c66ec88fSEmmanuel Vadot      Each state node represents a domain idle state description.
25*c66ec88fSEmmanuel Vadot
26*c66ec88fSEmmanuel Vadot    properties:
27*c66ec88fSEmmanuel Vadot      compatible:
28*c66ec88fSEmmanuel Vadot        const: domain-idle-state
29*c66ec88fSEmmanuel Vadot
30*c66ec88fSEmmanuel Vadot      entry-latency-us:
31*c66ec88fSEmmanuel Vadot        description:
32*c66ec88fSEmmanuel Vadot          The worst case latency in microseconds required to enter the idle
33*c66ec88fSEmmanuel Vadot          state. Note that, the exit-latency-us duration may be guaranteed only
34*c66ec88fSEmmanuel Vadot          after the entry-latency-us has passed.
35*c66ec88fSEmmanuel Vadot
36*c66ec88fSEmmanuel Vadot      exit-latency-us:
37*c66ec88fSEmmanuel Vadot        description:
38*c66ec88fSEmmanuel Vadot          The worst case latency in microseconds required to exit the idle
39*c66ec88fSEmmanuel Vadot          state.
40*c66ec88fSEmmanuel Vadot
41*c66ec88fSEmmanuel Vadot      min-residency-us:
42*c66ec88fSEmmanuel Vadot        description:
43*c66ec88fSEmmanuel Vadot          The minimum residency duration in microseconds after which the idle
44*c66ec88fSEmmanuel Vadot          state will yield power benefits, after overcoming the overhead while
45*c66ec88fSEmmanuel Vadot          entering the idle state.
46*c66ec88fSEmmanuel Vadot
47*c66ec88fSEmmanuel Vadot    required:
48*c66ec88fSEmmanuel Vadot      - compatible
49*c66ec88fSEmmanuel Vadot      - entry-latency-us
50*c66ec88fSEmmanuel Vadot      - exit-latency-us
51*c66ec88fSEmmanuel Vadot      - min-residency-us
52*c66ec88fSEmmanuel Vadot
53*c66ec88fSEmmanuel Vadotexamples:
54*c66ec88fSEmmanuel Vadot  - |
55*c66ec88fSEmmanuel Vadot
56*c66ec88fSEmmanuel Vadot    domain-idle-states {
57*c66ec88fSEmmanuel Vadot      domain_retention: domain-retention {
58*c66ec88fSEmmanuel Vadot        compatible = "domain-idle-state";
59*c66ec88fSEmmanuel Vadot        entry-latency-us = <20>;
60*c66ec88fSEmmanuel Vadot        exit-latency-us = <40>;
61*c66ec88fSEmmanuel Vadot        min-residency-us = <80>;
62*c66ec88fSEmmanuel Vadot      };
63*c66ec88fSEmmanuel Vadot    };
64*c66ec88fSEmmanuel Vadot...
65