Lines Matching refs:by

26 CAPI drivers optionally register themselves with Kernel CAPI by calling the
30 registration can be revoked by calling the function unregister_capi_driver()
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
37 pointers which are subsequently used by Kernel CAPI for communicating with the
38 driver. The registration can be revoked by calling the function
43 structure of the device, and signal its readiness by calling capi_ctr_ready().
49 callback functions by Kernel CAPI.
55 operation CAPI_REGISTER) to an appropriate hardware driver by calling its
57 allocated by Kernel CAPI and passed to register_appl() along with the
58 parameter structure provided by the application. This is analogous to the
79 the following non-private fields, all to be set by the driver before calling
92 This structure describes an ISDN device (controller) handled by a Kernel CAPI
99 - to be set by the driver before calling attach_capi_ctr():
105 	an opaque pointer to driver specific data, not touched by Kernel CAPI
117 	Completion must be signalled by a call to capi_ctr_ready().
125 	Completion must be signalled by a call to capi_ctr_down().
133 	Calls to these functions are serialized by Kernel CAPI so that only
149 	Calls to this function are not serialized by Kernel CAPI, ie. it must
190 parameter may be omitted by setting the length field of the CAPI message to 22
337 debugging output produced by the module. It can only be set when the module is