Lines Matching refs:callback

29 driver, and optionally a pointer to a callback function, add_card(). The
36 the names of the driver and controller, and a number of callback function
44 From then on, Kernel CAPI may call the registered callback functions for the
49 callback functions by Kernel CAPI.
56 register_appl() callback function. A unique Application ID (ApplID, u16) is
63 send_message() callback function. Conversely, the driver may call Kernel
68 forwarded as calls to the release_appl() callback function, passing the same
87 	a callback function pointer (may be NULL)
94 all controller specific lower layer interface and callback functions to
114 	(optional) pointer to a callback function for sending firmware and
122 	(optional) pointer to a callback function for stopping the device,
131 	pointers to callback functions for registration and deregistration of
137 	pointer to a callback function for sending a CAPI message to the
153 	pointer to a callback function returning the entry for the device in
157 	pointers to callback functions for the device's proc file