Lines Matching full:controller

16 	  Controller. This value does not include the HCI ACL header.
19 	  Controller.
22 	  by the Controller and use the smallest value supported by both the
23 	  Host and the Controller.
27 	  The Controller will return this value in the HCI LE Read Buffer
29 	  Layer transmission size then the Controller will perform
42 	  Controller. This determines the maximum amount of data packets the
43 	  Host can have queued in the Controller before waiting for the
48 	  The Controller will return this value in the HCI LE Read Buffer Size
62 	  Maximum support ACL size of data packets sent from the Controller to
65 	  In a combined Host and Controller build, both the
66 	  Host and the Controller will use this value for buffer sizes, making
67 	  Controller to Host flow control not strictly necessary.
69 	  In a Host only build with Controller to Host flow control enabled
70 	  the Host will inform the Controller about the maximum ACL data size it
73 	  If Controller to Host flow control is not enabled then the Controller
75 	  the controller can produce it.
77 	  In a Controller only build this will determine the maximum ACL size
78 	  that the Controller will send to the Host.
89 	  Number of incoming extra ACL data buffers sent from the Controller to
97 	  fragment from the Controller.
104 	  Number or incoming ACL data buffers sent from the Controller to the
106 	  In a combined Host and Controller build the buffers are shared and
107 	  therefore Controller to Host flow control is not needed.
109 	  In a Host only build with Controller to Host flow control enabled
110 	  the Host will inform the Controller about the maximum number of
113 	  When Controller to Host flow control is not enabled the Controller
130 	  This value is used by both the Host and the Controller for buffer
143 	  Controller.
187 	  This value is used by both the Host and the Controller for buffer
194 	# This option is only visible for a user when Host and Controller are build together, or for
197 	# This option is present when Host and Controller are build together, or
198 	# for Host only builds, or when Controller-to-Host ACL data flow control
204 	# the system work queue for HCI command Tx towards the Controller, one additional HCI
214 	  not enabling Controller to Host data flow control (BT_HCI_ACL_FLOW_CONTROL), Read Remote
222 	  commands and the Controller side HCI drivers that allocates HCI command buffers with
225 	  When Controller to Host data flow control is enabled in the Host-only or combined
226 	  Host plus Controller build, the internal BT_BUF_CMD_TX_COUNT is adjusted accordingly
229 	  BT_BUF_ACL_RX_COUNT of Host Number of Completed Packets command down to the Controller.
231 	  When Controller to Host data flow control is supported in the Controller-only build,
234 	  Where Ncmd is supported maximum Num_HCI_Command_Packets in the Controller implementation.
245 	  This option is set by the Bluetooth controller to indicate support
254 	  Host and/or Controller. This enables Set Version Information,
261 	  Enable emitting HCI Vendor-Specific events for system and Controller
269 	  Use some heuristics to try to guess in advance whether the controller
271 	  sending vendor commands to controller which may interpret them in
283 	  Emit a Command Complete event from the Controller (and wait for it
284 	  from the Host) for the NOP opcode to indicate that the Controller is