Lines Matching refs:OS
1 PSCI OS-initiated mode
31 OS-initiated.
43 OS-initiated
46 OS-initiated mode is optional.
48 In OS-initiated mode, the calling OS is responsible for coordinating power
55 There are two reasons why OS-initiated mode might be a more suitable option than
65 In OS-initiated mode, the OS has knowledge of the next wakeup event for each
75 In platform-coordinated mode, the OS doesn't have visibility when the last core
76 at a power level enters a low-power state. If the OS wants to perform last man
80 platform-coordinated mode when it should be using OS-initiated mode instead.
82 In OS-initiated mode, the OS can perform last man activity if it selects a
85 the OS and the platform.
92 * For their ARM32 platforms, they're using OS-initiated mode implemented in
94 * For their future ARM64 platforms, they are interested in using OS-initiated
99 * For their mobile platforms, they're using OS-initiated mode implemented in
101 * For their Chrome OS platforms, they're using platform-coordinated mode in
109 Both Qualcomm and Google would like to be able to use OS-initiated mode in TF-A
138 * OS-initiated mode, bit[0]
140 * A value of 0 indicates OS-initiated mode is not supported.
141 * A value of 1 indicates OS-initiated mode is supported.
154 :param mode: 0 indicates platform-coordinated mode, 1 indicates OS-initiated
157 :retval NOT_SUPPORTED: if OS-initiated mode is not supported.
162 Switching from platform-coordinated to OS-initiated is only allowed if the
174 Switching from OS-initiated to platform-coordinated is only allowed if all cores
196 :retval INVALID_PARAMETERS: in OS-initiated mode, this error is returned when
201 :retval DENIED: only in OS-initiated mode; this error is returned when a
209 In OS-initiated mode, the calling OS is making an explicit request for a
237 * In OS-initiated mode, the state ID encoding must allow expressing the
246 Races in OS-initiated mode
249 In OS-initiated mode, there are race windows where the OS's view and
250 implementation's view of the system's state differ. It is possible for the OS to
252 state. For example, the OS might request a powerdown state for a node from one
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
277 coordination mode for suspend is platform-coordinated or OS-initiated. If all
280 In OS-initiated mode, if a subset of the cores in a topology node has called
322 Proposed implementation of OS-initiated mode
325 To add support for OS-initiated mode, the following changes are proposed:
328 optional support for PSCI OS-initiated mode. This build option defaults to 0.
336 OS-initiated mode for CPU_SUSPEND.
360 states requested by the calling OS
684 * OS-initiated mode
711 OS-initiated mode was able to scale better than platform-coordinated mode for
713 idle state) in OS-initiated mode for multiple CPUs were much closer to the