INTERFACE.CAPI 8.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207
  1. Kernel CAPI Interface to Hardware Drivers
  2. -----------------------------------------
  3. 1. Overview
  4. Kernel CAPI operates as a dispatching layer between CAPI applications and CAPI
  5. hardware drivers. Hardware drivers register ISDN devices (controllers, in CAPI
  6. lingo) with Kernel CAPI to indicate their readiness to provide their service
  7. to CAPI applications. CAPI applications also register with Kernel CAPI,
  8. requesting association with a CAPI device. Kernel CAPI then dispatches the
  9. application registration to an available device, forwarding it to the
  10. corresponding hardware driver. Kernel CAPI then forwards CAPI messages in both
  11. directions between the application and the hardware driver.
  12. 2. Driver and Device Registration
  13. CAPI drivers optionally register themselves with Kernel CAPI by calling the
  14. Kernel CAPI function register_capi_driver() with a pointer to a struct
  15. capi_driver. This structure must be filled with the name and revision of the
  16. driver, and optionally a pointer to a callback function, add_card(). The
  17. registration can be revoked by calling the function unregister_capi_driver()
  18. with a pointer to the same struct capi_driver.
  19. CAPI drivers must register each of the ISDN devices they control with Kernel
  20. CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
  21. struct capi_ctr before they can be used. This structure must be filled with
  22. the names of the driver and controller, and a number of callback function
  23. pointers which are subsequently used by Kernel CAPI for communicating with the
  24. driver. The registration can be revoked by calling the function
  25. detach_capi_ctr() with a pointer to the same struct capi_ctr.
  26. Before the device can be actually used, the driver must fill in the device
  27. information fields 'manu', 'version', 'profile' and 'serial' in the capi_ctr
  28. structure of the device, and signal its readiness by calling capi_ctr_ready().
  29. From then on, Kernel CAPI may call the registered callback functions for the
  30. device.
  31. If the device becomes unusable for any reason (shutdown, disconnect ...), the
  32. driver has to call capi_ctr_reseted(). This will prevent further calls to the
  33. callback functions by Kernel CAPI.
  34. 3. Application Registration and Communication
  35. Kernel CAPI forwards registration requests from applications (calls to CAPI
  36. operation CAPI_REGISTER) to an appropriate hardware driver by calling its
  37. register_appl() callback function. A unique Application ID (ApplID, u16) is
  38. allocated by Kernel CAPI and passed to register_appl() along with the
  39. parameter structure provided by the application. This is analogous to the
  40. open() operation on regular files or character devices.
  41. After a successful return from register_appl(), CAPI messages from the
  42. application may be passed to the driver for the device via calls to the
  43. send_message() callback function. The CAPI message to send is stored in the
  44. data portion of a skb. Conversely, the driver may call Kernel CAPI's
  45. capi_ctr_handle_message() function to pass a received CAPI message to Kernel
  46. CAPI for forwarding to an application, specifying its ApplID.
  47. Format and semantics of CAPI messages are specified in the CAPI 2.0 standard.
  48. Deregistration requests (CAPI operation CAPI_RELEASE) from applications are
  49. forwarded as calls to the release_appl() callback function, passing the same
  50. ApplID as with register_appl(). After return from release_appl(), no CAPI
  51. messages for that application may be passed to or from the device anymore.
  52. 4. Data Structures
  53. 4.1 struct capi_driver
  54. This structure describes a Kernel CAPI driver itself. It is used in the
  55. register_capi_driver() and unregister_capi_driver() functions, and contains
  56. the following non-private fields, all to be set by the driver before calling
  57. register_capi_driver():
  58. char name[32]
  59. the name of the driver, as a zero terminated ASCII string
  60. char revision[32]
  61. the revision number of the driver, as a zero terminated ASCII string
  62. int (*add_card)(struct capi_driver *driver, capicardparams *data)
  63. a callback function pointer (may be NULL)
  64. 4.2 struct capi_ctr
  65. This structure describes an ISDN device (controller) handled by a Kernel CAPI
  66. driver. After registration via the attach_capi_ctr() function it is passed to
  67. all controller specific lower layer interface and callback functions to
  68. identify the controller to operate on.
  69. It contains the following non-private fields:
  70. - to be set by the driver before calling attach_capi_ctr():
  71. struct module *owner
  72. pointer to the driver module owning the device
  73. void *driverdata
  74. an opaque pointer to driver specific data, not touched by Kernel CAPI
  75. char name[32]
  76. the name of the controller, as a zero terminated ASCII string
  77. char *driver_name
  78. the name of the driver, as a zero terminated ASCII string
  79. int (*load_firmware)(struct capi_ctr *ctrlr, capiloaddata *ldata)
  80. (optional) pointer to a callback function for sending firmware and
  81. configuration data to the device
  82. void (*reset_ctr)(struct capi_ctr *ctrlr)
  83. pointer to a callback function for performing a reset on the device,
  84. releasing all registered applications
  85. void (*register_appl)(struct capi_ctr *ctrlr, u16 applid,
  86. capi_register_params *rparam)
  87. void (*release_appl)(struct capi_ctr *ctrlr, u16 applid)
  88. pointers to callback functions for registration and deregistration of
  89. applications with the device
  90. u16 (*send_message)(struct capi_ctr *ctrlr, struct sk_buff *skb)
  91. pointer to a callback function for sending a CAPI message to the
  92. device
  93. char *(*procinfo)(struct capi_ctr *ctrlr)
  94. pointer to a callback function returning the entry for the device in
  95. the CAPI controller info table, /proc/capi/controller
  96. read_proc_t *ctr_read_proc
  97. pointer to the read_proc callback function for the device's proc file
  98. system entry, /proc/capi/controllers/<n>; will be called with a
  99. pointer to the device's capi_ctr structure as the last (data) argument
  100. - to be filled in before calling capi_ctr_ready():
  101. u8 manu[CAPI_MANUFACTURER_LEN]
  102. value to return for CAPI_GET_MANUFACTURER
  103. capi_version version
  104. value to return for CAPI_GET_VERSION
  105. capi_profile profile
  106. value to return for CAPI_GET_PROFILE
  107. u8 serial[CAPI_SERIAL_LEN]
  108. value to return for CAPI_GET_SERIAL
  109. 5. Lower Layer Interface Functions
  110. (declared in <linux/isdn/capilli.h>)
  111. void register_capi_driver(struct capi_driver *drvr)
  112. void unregister_capi_driver(struct capi_driver *drvr)
  113. register/unregister a driver with Kernel CAPI
  114. int attach_capi_ctr(struct capi_ctr *ctrlr)
  115. int detach_capi_ctr(struct capi_ctr *ctrlr)
  116. register/unregister a device (controller) with Kernel CAPI
  117. void capi_ctr_ready(struct capi_ctr *ctrlr)
  118. void capi_ctr_reseted(struct capi_ctr *ctrlr)
  119. signal controller ready/not ready
  120. void capi_ctr_suspend_output(struct capi_ctr *ctrlr)
  121. void capi_ctr_resume_output(struct capi_ctr *ctrlr)
  122. signal suspend/resume
  123. void capi_ctr_handle_message(struct capi_ctr * ctrlr, u16 applid,
  124. struct sk_buff *skb)
  125. pass a received CAPI message to Kernel CAPI
  126. for forwarding to the specified application
  127. 6. Helper Functions and Macros
  128. Library functions (from <linux/isdn/capilli.h>):
  129. void capilib_new_ncci(struct list_head *head, u16 applid,
  130. u32 ncci, u32 winsize)
  131. void capilib_free_ncci(struct list_head *head, u16 applid, u32 ncci)
  132. void capilib_release_appl(struct list_head *head, u16 applid)
  133. void capilib_release(struct list_head *head)
  134. void capilib_data_b3_conf(struct list_head *head, u16 applid,
  135. u32 ncci, u16 msgid)
  136. u16 capilib_data_b3_req(struct list_head *head, u16 applid,
  137. u32 ncci, u16 msgid)
  138. Macros to extract/set element values from/in a CAPI message header
  139. (from <linux/isdn/capiutil.h>):
  140. Get Macro Set Macro Element (Type)
  141. CAPIMSG_LEN(m) CAPIMSG_SETLEN(m, len) Total Length (u16)
  142. CAPIMSG_APPID(m) CAPIMSG_SETAPPID(m, applid) ApplID (u16)
  143. CAPIMSG_COMMAND(m) CAPIMSG_SETCOMMAND(m,cmd) Command (u8)
  144. CAPIMSG_SUBCOMMAND(m) CAPIMSG_SETSUBCOMMAND(m, cmd) Subcommand (u8)
  145. CAPIMSG_CMD(m) - Command*256
  146. + Subcommand (u16)
  147. CAPIMSG_MSGID(m) CAPIMSG_SETMSGID(m, msgid) Message Number (u16)
  148. CAPIMSG_CONTROL(m) CAPIMSG_SETCONTROL(m, contr) Controller/PLCI/NCCI
  149. (u32)
  150. CAPIMSG_DATALEN(m) CAPIMSG_SETDATALEN(m, len) Data Length (u16)