Lines Matching +full:buffer +full:- +full:size
5 # SPDX-License-Identifier: Apache-2.0
7 menu "Bluetooth buffer configuration"
10 int "Maximum supported ACL size for outgoing data"
15 Maximum supported ACL size of data packets sent from the Host to the
21 In a Host-only build the Host will read the maximum ACL size supported
25 The Host supports sending of larger L2CAP PDUs than the ACL size and
27 The Controller will return this value in the HCI LE Read Buffer
28 Size command response. If this size if greater than effective Link
29 Layer transmission size then the Controller will perform
31 If this value is less than the effective Link Layer transmission size
32 then this will restrict the maximum Link Layer transmission size.
48 The Controller will return this value in the HCI LE Read Buffer Size
52 int "Maximum supported ACL size for incoming data"
62 Maximum support ACL size of data packets sent from the Controller to
66 Host and the Controller will use this value for buffer sizes, making
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.
77 In a Controller only build this will determine the maximum ACL size
103 buffers by setting this value in the Host Buffer Size command.
109 enforced by a build-time check: BT_BUF_ACL_RX_COUNT needs to be at
113 int "Maximum supported HCI Event buffer length"
120 Maximum supported HCI event buffer size. This value does not include
122 This value is used by both the Host and the Controller for buffer
138 int "Maximum supported discardable HCI Event buffer length"
147 Maximum support discardable HCI event size of buffers in the separate
148 discardable event buffer pool. This value does not include the
150 The minimum size is set based on the Advertising Report. Setting
151 the buffer size different than BT_BUF_EVT_RX_SIZE can save memory.
160 Number of buffers in a separate buffer pool for events which
168 int "Maximum support HCI Command buffer length"
177 Maximum data size for each HCI Command buffer. This value does not
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)
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
217 Enable emitting HCI Vendor-Specific events for system and Controller
252 kernel-wide __ASSERT() when CONFIG_ASSERT is disabled.
299 instead of plain-text output. Requires a special application
317 Use a custom logging protocol over the RTT buffer instead of
318 plain-text output. Requires a special application
325 int "Buffer number used for custom logger output."
329 Select index of up-buffer used for logger output.
330 Make sure the buffer number is not used by other logger,
331 e.g. in LOG_BACKEND_RTT_BUFFER, otherwise the buffer will be
335 string "Buffer name used for custom logger output."
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.