>> >> Should "arg" be removed from the typedefs for cpu_idle_enter_cbfn >> and cpu_idle_exit_cbfn and also removed from >> cpu_idle_register_callback and cpu_idle_unregister_callback? >> There is no purpose for arg in the new version of the interface. >The arg is used to pass context info back to callbacks. >It's useful when the same callback handler will be registered more than one >time. If no such usage >scenario, we can remove it.
The purpose of "arg" is not necessarily for registration more than once, but if the caller has to save/check other architecture specific things not covered in the generic info we provide like idle_state, next expected waketime etc..say I would like to get some perf counter and store etc.. Bill/Eric: Do you think we should return a handle for the registration? And the caller passes the handle back during de-registration instead?
