forked from Minki/linux
598da548ef
Re-using idle state definition provided by arm,idle-state for domain idle states creates a lot of confusion and limits further evolution of the domain idle definition. To keep things clear and simple, define a idle states for domain using a new compatible "domain-idle-state". Fix existing PM domains code to look for the newly defined compatible. Signed-off-by: Lina Iyer <lina.iyer@linaro.org> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
34 lines
1.0 KiB
Plaintext
34 lines
1.0 KiB
Plaintext
PM Domain Idle State Node:
|
|
|
|
A domain idle state node represents the state parameters that will be used to
|
|
select the state when there are no active components in the domain.
|
|
|
|
The state node has the following parameters -
|
|
|
|
- compatible:
|
|
Usage: Required
|
|
Value type: <string>
|
|
Definition: Must be "domain-idle-state".
|
|
|
|
- entry-latency-us
|
|
Usage: Required
|
|
Value type: <prop-encoded-array>
|
|
Definition: u32 value representing worst case latency in
|
|
microseconds required to enter the idle state.
|
|
The exit-latency-us duration may be guaranteed
|
|
only after entry-latency-us has passed.
|
|
|
|
- exit-latency-us
|
|
Usage: Required
|
|
Value type: <prop-encoded-array>
|
|
Definition: u32 value representing worst case latency
|
|
in microseconds required to exit the idle state.
|
|
|
|
- min-residency-us
|
|
Usage: Required
|
|
Value type: <prop-encoded-array>
|
|
Definition: u32 value representing minimum residency duration
|
|
in microseconds after which the idle state will yield
|
|
power benefits after overcoming the overhead in entering
|
|
i the idle state.
|