Lines Matching +full:other +full:- +full:controller
5 # SPDX-License-Identifier: Apache-2.0
16 Controller. This value does not include the HCI ACL header.
19 Controller.
21 In a Host-only build the Host will read the maximum ACL size supported
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.
85 Number of incoming extra ACL data buffers sent from the Controller to
96 Number or incoming ACL data buffers sent from the Controller to the
98 In a combined Host and Controller build the buffers are shared and
99 therefore Controller to Host flow control is not needed.
101 In a Host only build with Controller to Host flow control enabled
102 the Host will inform the Controller about the maximum number of
105 When Controller to Host flow control is not enabled the Controller
109 enforced by a build-time check: BT_BUF_ACL_RX_COUNT needs to be at
122 This value is used by both the Host and the Controller for buffer
135 Controller.
164 it will not cause the allocation for other critical events to
171 # of antenna ids for platforms other than Nordic.
179 This value is used by both the Host and the Controller for buffer
195 ZEPHYR_BT_HCI := zephyr,bt-hci
199 default $(dt_chosen_bool_prop,$(ZEPHYR_BT_HCI),bt-hci-vs-ext)
201 This option is set by the Bluetooth controller to indicate support
202 for the Zephyr HCI Vendor-Specific Commands and Event.
205 bool "Zephyr HCI Vendor-Specific Commands"
209 Enable support for the Zephyr HCI Vendor-Specific Commands in the
210 Host and/or Controller. This enables Set Version Information,
217 Enable emitting HCI Vendor-Specific events for system and Controller
225 Use some heuristics to try to guess in advance whether the controller
227 sending vendor commands to controller which may interpret them in
239 Emit a Command Complete event from the Controller (and wait for it
240 from the Host) for the NOP opcode to indicate that the Controller is
252 kernel-wide __ASSERT() when CONFIG_ASSERT is disabled.
299 instead of plain-text output. Requires a special application
318 plain-text output. Requires a special application
329 Select index of up-buffer used for logger output.
330 Make sure the buffer number is not used by other logger,
338 Select index of up-buffer used for logger output.
341 int "Size of reserved up-buffer for custom logger output."
344 Specify reserved size of up-buffer used for custom logger output.