Lines Matching refs:power
17 A power domain topology is a logical hierarchy of power domains in a system that
18 arises from the physical dependencies between power domains.
20 Local power states describe power states for an individual node, and composite
21 power states describe the combined power states for an individual node and its
24 Entry into low-power states for a topology node above the core level requires
25 coordinating its children nodes. For example, in a system with a power domain
26 that encompasses a shared cache, and a separate power domain for each core that
27 uses the shared cache, the core power domains must be powered down before the
28 shared cache power domain can be powered down.
30 PSCI supports two modes of power state coordination: platform-coordinated and
36 Platform-coordinated mode is the default mode of power state coordination, and
39 In platform-coordinated mode, the platform is responsible for coordinating power
40 states, and chooses the deepest power state for a topology node that can be
48 In OS-initiated mode, the calling OS is responsible for coordinating power
49 states, and may request for a topology node to enter a low-power state when
50 its last child enters the low-power state.
62 power states, and doesn't account for composite power states that are shared
67 latencies when deciding if a composite power state (e.g. for a cluster) is
70 different power efficiencies.
76 at a power level enters a low-power state. If the OS wants to perform last man
83 composite power state when the last core enters a low-power state. This
148 PSCI_SET_SUSPEND_MODE is for switching between the two different modes of power
185 CPU_SUSPEND is for moving a topology node into a low-power state.
190 :param power_state: the requested low-power state to enter.
197 a low-power state is requested for a topology node above the core level,
198 and at least one of the node's children is in a local low-power state
202 low-power state is requested for a topology node above the core level,
204 low-power state.
207 all cores to determine the deepest power state to enter.
210 specific power state, as opposed to expressing a vote. The PSCI implementation
224 * The requested level in the power domain topology to enter a low-power
234 * Field to specify the requested composite power state.
236 power state.
238 power level at which the calling core is the last to enter a powerdown
256 To address potential race conditions in power state requests:
258 * The calling OS must specify in each CPU_SUSPEND request the deepest power
260 This is required even if the OS doesn't want the node at that power level to
261 enter a low-power state.
262 * The implementation must validate that the requested power states in the
264 calling core is the last core running at the requested power level, or deny
276 CPU_OFF is always platform-coordinated, regardless of whether the power state
278 cores in a topology node call CPU_OFF, the last core will power down the node.
282 at or above that node's power level.
292 Platform-coordinated is currently the only supported power state coordination
301 object with the requested states for each power level.
305 * This function takes the ``state_info`` object containing the requested power
306 states for each power level, and returns the deepest power level that was
307 requested to enter a low power state, i.e. the target power level.
311 * This function takes the target power level and the ``state_info`` object
312 containing the requested power states for each power level, and updates the
313 ``state_info`` object with the coordinated target power state for each
319 containing the target power states for each power level, and transitions
320 each power level to the specified power state.
351 * The requested power states for each power level are consistent with the
353 * The calling core is the last core running at the requested power level
359 * The ``state_info`` argument is never modified since it contains the power
411 power-domains = <&CPU_PD0>;
412 power-domain-names = "psci";
419 power-domains = <&CPU_PD1>;
420 power-domain-names = "psci";
435 CLUSTER_STOP: core-power-domain {
450 CPU_PD0: power-domain-cpu0 {
451 #power-domain-cells = <0>;
452 power-domains = <&pd_core>;
456 CPU_PD1: power-domain-cpu1 {
457 #power-domain-cells = <0>;
458 power-domains = <&pd_core>;
462 pd_core: power-domain-cluster {
463 #power-domain-cells = <0>;
486 power-domains = <&CPU_PD0>;
487 power-domain-names = "psci";
495 power-domains = <&CPU_PD1>;
496 power-domain-names = "psci";
504 power-domains = <&CPU_PD2>;
505 power-domain-names = "psci";
513 power-domains = <&CPU_PD3>;
514 power-domain-names = "psci";
522 power-domains = <&CPU_PD4>;
523 power-domain-names = "psci";
531 power-domains = <&CPU_PD5>;
532 power-domain-names = "psci";
540 power-domains = <&CPU_PD6>;
541 power-domain-names = "psci";
549 power-domains = <&CPU_PD7>;
550 power-domain-names = "psci";
558 idle-state-name = "little-power-down";
568 idle-state-name = "little-rail-power-down";
578 idle-state-name = "big-power-down";
588 idle-state-name = "big-rail-power-down";
600 idle-state-name = "cluster-power-down";
615 #power-domain-cells = <0>;
616 power-domains = <&CLUSTER_PD>;
621 #power-domain-cells = <0>;
622 power-domains = <&CLUSTER_PD>;
627 #power-domain-cells = <0>;
628 power-domains = <&CLUSTER_PD>;
633 #power-domain-cells = <0>;
634 power-domains = <&CLUSTER_PD>;
639 #power-domain-cells = <0>;
640 power-domains = <&CLUSTER_PD>;
645 #power-domain-cells = <0>;
646 power-domains = <&CLUSTER_PD>;
651 #power-domain-cells = <0>;
652 power-domains = <&CLUSTER_PD>;
657 #power-domain-cells = <0>;
658 power-domains = <&CLUSTER_PD>;
663 #power-domain-cells = <0>;
704 * Count refers to the number of times a CPU or cluster entered power collapse.
705 * Residency refers to the time in seconds a CPU or cluster stayed in power