Lines Matching full:member

53 containing four callback pointers, :c:member:`enable`, :c:member:`disable`,
54 :c:member:`select`, :c:member:`reflect`, a :c:member:`rating` field described
62 :c:member:`rating` field is greater than the value of that field for the
75 :c:member:`enable`
94 :c:member:`disable`
107 :c:member:`select`
118 	:c:member:`states` array of struct cpuidle_state objects held by the
133 	This callback is mandatory (i.e. the :c:member:`select` callback pointer
137 :c:member:`reflect`
154 :c:member:`exit_latency` value is greater than the number returned by that
164 First of all, a ``CPUIdle`` driver has to populate the :c:member:`states` array
170 The entries in the :c:member:`states` array are expected to be sorted by the
171 value of the :c:member:`target_residency` field in struct cpuidle_state in
173 the minimum value of :c:member:`target_residency`).  [Since the
174 :c:member:`target_residency` value is expected to reflect the "depth" of the
182 :c:member:`target_residency`
188 :c:member:`exit_latency`
193 :c:member:`flags`
201 The :c:member:`enter` callback pointer in struct cpuidle_state, which must not
214 :c:member:`states` array representing the idle state to ask the processor to
223 Once the :c:member:`states` array has been populated, the number of valid
224 entries in it has to be stored in the :c:member:`state_count` field of the
226 entries in the :c:member:`states` array represent "coupled" idle states (that
228 idle), the :c:member:`safe_state_index` field in struct cpuidle_driver needs
233 subset of logical CPUs in the system, the :c:member:`cpumask` field in its
238 are no "coupled" idle state entries in the driver's :c:member:`states` array,
276 change.  Next, it can update its :c:member:`states` array in accordance with