Lines Matching refs:s
133 module and the functionality of their device(s) can be used through these
150 validation during certain operations such as binding to a module's API.
155 framework's module interface so that other modules can bind to it. It does not
260 - Identifying a module's elements, events or APIs from the context of another
293 An API is declared in the module's public header as a structure containing one
297 Within the module's source files each declared API is then defined, with each of
298 the API's declared function pointers pointing to a function within the module.
303 API identifier so that it can uniquely identify which of the target module's
308 latter is used to specify which of the target module's APIs is requested.
371 Apart from this, from the user's view the *Light Events* behaves as same as
432 satisfy the *init()* function pointer of the framework's module API. During this
439 *element_init()* function pointer of the framework's module API. This function
440 is invoked once for each element that is defined in the firmware's element table
448 referred to in an element's descriptor.
460 initialization that requires comparisons between the module's elements as this
473 other's APIs. Until modules are bound they have no direct way to call functions
497 processing the pending events. Then, it's up to the system to call the function
533 framework allows a module to reject a binding request if the module's criteria