Lines Matching refs:to
1 Kernel CAPI Interface to Hardware Drivers
8 to access ISDN equipment connected to basic rate interfaces (BRI) and primary
13 lingo) with Kernel CAPI to indicate their readiness to provide their service
14 to CAPI applications. CAPI applications also register with Kernel CAPI,
16 application registration to an available device, forwarding it to the
27 Kernel CAPI function register_capi_driver() with a pointer to a struct
29 driver, and optionally a pointer to a callback function, add_card(). The
31 with a pointer to the same struct capi_driver.
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
39 detach_capi_ctr() with a pointer to the same struct capi_ctr.
48 driver has to call capi_ctr_down(). This will prevent further calls to the
54 Kernel CAPI forwards registration requests from applications (calls to 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
62 application may be passed to the driver for the device via calls to the
64 CAPI's capi_ctr_handle_message() function to pass a received CAPI message to
65 Kernel CAPI for forwarding to an application, specifying its ApplID.
68 forwarded as calls to the release_appl() callback function, passing the same
70 messages for that application may be passed to or from the device anymore.
79 the following non-private fields, all to be set by the driver before calling
93 driver. After registration via the attach_capi_ctr() function it is passed to
94 all controller specific lower layer interface and callback functions to
95 identify the controller to operate on.
99 - to be set by the driver before calling attach_capi_ctr():
102 pointer to the driver module owning the device
105 an opaque pointer to driver specific data, not touched by Kernel CAPI
114 (optional) pointer to a callback function for sending firmware and
115 configuration data to the device
117 Completion must be signalled by a call to capi_ctr_ready().
122 (optional) pointer to a callback function for stopping the device,
125 Completion must be signalled by a call to capi_ctr_down().
131 pointers to callback functions for registration and deregistration of
133 Calls to these functions are serialized by Kernel CAPI so that only
134 one call to any of them is active at any time.
137 pointer to a callback function for sending a CAPI message to the
142 non-zero (error) value then ownership of the skb returns to the caller
144 The return value should only be used to signal problems with respect
145 to accepting or queueing the message. Errors occurring during the
149 Calls to this function are not serialized by Kernel CAPI, ie. it must
150 be prepared to be re-entered.
153 pointer to a callback function returning the entry for the device in
157 pointers to callback functions for the device's proc file
158 system entry, /proc/capi/controllers/<n>; pointer to the device's
165 - to be filled in before calling capi_ctr_ready():
168 value to return for CAPI_GET_MANUFACTURER
171 value to return for CAPI_GET_VERSION
174 value to return for CAPI_GET_PROFILE
177 value to return for CAPI_GET_SERIAL
184 (skb). Each skb contains a single CAPI message coded according to the CAPI 2.0
190 parameter may be omitted by setting the length field of the CAPI message to 22
213 are actually used. Unused members should be set to zero.
226 The member is a pointer to a buffer containing the parameter in
228 be taken to represent an empty (zero length) parameter.
239 Functions capi_cmsg2message() and capi_message2cmsg() are provided to convert
243 sure it is big enough to accommodate the resulting CAPI message.
268 pass a received CAPI message to Kernel CAPI
269 for forwarding to the specified application
287 Macros to extract/set element values from/in a CAPI message header
320 parameters with non-default values need to be changed before sending
325 _REQ to _CONF and _IND to _RESP.
328 Returns the CAPI 2.0 message name corresponding to the given command
338 loaded, via a parameter "showcapimsgs=<n>" to the modprobe command, either on
345 parameter controlling how CAPI messages sent from and to tha controller are