Lines Matching full:host
15 Maximum supported ACL size of data packets sent from the Host to the
18 In a combined build this value will be set in both the Host and the
21 In a Host-only build the Host will read the maximum ACL size supported
23 Host and the Controller.
25 The Host supports sending of larger L2CAP PDUs than the ACL size and
41 Number of outgoing ACL data buffers sent from the Host to the
43 Host can have queued in the Controller before waiting for the
44 to notify the Host that more packets can be queued with the Number of
46 The buffers are shared between all of the connections and the Host
63 the Host. This value does not include the HCI ACL header.
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
71 can send by setting this value in the Host Buffer Size command.
73 If Controller to Host flow control is not enabled then the Controller
74 can assume the Host has to receive and process ACL data faster than
78 that the Controller will send to the Host.
81 # As Host implementation unconditionally references this Kconfig, we
90 the Host.
95 The L2CAP recombination in the Host keeps the first Rx buffer for each
105 Host.
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
111 buffers by setting this value in the Host Buffer Size command.
113 When Controller to Host flow control is not enabled the Controller
114 can assume that the Host has infinite amount of buffers.
130 This value is used by both the Host and the Controller for buffer
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
195 # Host-only builds.
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
203 # Advertising in the receive callback run in the system work queue and as the Host also uses
211 Number of buffers available for outgoing HCI commands from the Host.
214 not enabling Controller to Host data flow control (BT_HCI_ACL_FLOW_CONTROL), Read Remote
221 The Host Number of Completed Packets command does not follow normal flow control of HCI
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,
254 Host and/or Controller. This enables Set Version Information,
284 from the Host) for the NOP opcode to indicate that the Controller is
348 on the host side that can decode this protocol. Currently
367 on the host side that can decode this protocol. Currently