Lines Matching full:states

25 However, there may be multiple different idle states that can be used in such a
35 units: *governors* responsible for selecting idle states to ask the processor
85 	struct cpuidle_state objects representing idle states that the
117 	The list of idle states to take into consideration is represented by the
118 	:c:member:`states` array of struct cpuidle_state objects held by the
149 account when selecting idle states.  In order to obtain the current effective
164 First of all, a ``CPUIdle`` driver has to populate the :c:member:`states` array
167 idle states that the processor hardware can be asked to enter shared by all of
170 The entries in the :c:member:`states` array are expected to be sorted by the
214 :c:member:`states` array representing the idle state to ask the processor to
220 interrupts at any point (even temporarily) or attempt to change the states of
223 Once the :c:member:`states` array has been populated, the number of valid
226 entries in the :c:member:`states` array represent "coupled" idle states (that
227 is, idle states that can only be asked for if multiple related logical CPUs are
238 are no "coupled" idle state entries in the driver's :c:member:`states` array,
270 lead to modifications of the list of available processor idle states (which can
276 change.  Next, it can update its :c:member:`states` array in accordance with