Lines Matching full:callback

156 callback.
168 If a usage site requires only a callback in one direction of the hotplug
169 operations (CPU online or CPU offline) then the other not-required callback
192   The startup callbacks are allowed to fail. If a callback fails, the CPU
227   The callbacks are allowed to fail. When a callback fails the hotplug
347   startup callback has to be invoked before the PERF driver startup
350   callback. The statically allocated states are described by constants in
404          a startup callback
409          a startup callback
414          a startup callback
424 The @startup argument is a function pointer to the callback which should be
426 startup callback set the pointer to NULL.
428 The @teardown argument is a function pointer to the callback which should
430 require a teardown callback set the pointer to NULL.
438     callbacks and invoke the @startup callback (if not NULL) for all online
440     state. Depending on the state section the callback is either invoked on
444     If a callback fails for CPU N then the teardown callback for CPU
449 The state setup and the callback invocations are serialized against CPU
492     callback (if not NULL) for all online CPUs which have currently a state
494     callback is either invoked on the current CPU (PREPARE section) or on
498     In order to complete the removal, the teardown callback should not fail.
500 The state removal and the callback invocations are serialized against CPU
522 state callbacks and can be used by the callback to retrieve the instance
531     callback (if not NULL) associated with @state for all online CPUs which
532     have currently a state greater than @state. The callback is only
534     the callback is either invoked on the current CPU (PREPARE section) or
538     If a callback fails for CPU N then the teardown callback for CPU
557     teardown callback (if not NULL) associated with @state for all online
558     CPUs which have currently a state greater than @state.  The callback is
560     section the callback is either invoked on the current CPU (PREPARE
564     In order to complete the removal, the teardown callback should not fail.
566 The node list add/remove operations and the callback invocations are
653 It is important to note that the teardown callback of state 140 have been