Lines Matching full:it

19 there are no tasks to run on it except for the special "idle" task associated
20 with it, there is an opportunity to save energy for the processor that it
23 depended on by it into an idle state in which they will draw less power.
26 situation in principle, so it may be necessary to find the most suitable one
33 or platform design details in it is separate from the code that interacts with
34 the hardware.  It generally is divided into three categories of functional
55 below, and a name (string) used for identifying it.
59 a pointer to it passed as the argument.  If successful, that causes the core to
60 add the governor to the global list of available governors and, if it is the
69 Once registered, ``CPUIdle`` governors cannot be unregistered, so it is not
84 	with that CPU (among other things, it should contain the list of
88 	It may fail, in which case it is expected to return a negative error
103 	It is expected to reverse any changes made by the ``->enable()``
104 	callback when it was last invoked for the target CPU, free all memory
122 	array (unless it is a negative error code).
126 	idle state.  When the ``bool`` variable pointed to by it (which is set
130 	stopped on that CPU already, however, it will not be restarted before
143 	selection made by the ``->select()`` callback (when it was invoked last
166 representing it.  Going forward this array will represent the list of available
175 idle state represented by the struct cpuidle_state object holding it, this
184 	enter it (which may be substantial) to save more energy than could
189 	Maximum time it will take a CPU asking the processor to enter this idle
190 	state to start executing the first instruction after a wakeup from it,
210 The first two arguments of it point to the struct cpuidle_device object
219 The difference between in and ``->enter()`` is that it must not re-enable
224 entries in it has to be stored in the :c:member:`state_count` field of the
235 handled by it.
237 A ``CPUIdle`` driver can only be used after it has been registered.  If there
243 However, it also is necessary to register struct cpuidle_device objects for
249 of registering the struct cpuidle_device objects as needed, so it is generally
255 be invoked for the logical CPU represented by it, so it must take place after
267 by it.
276 change.  Next, it can update its :c:member:`states` array in accordance with