OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/bluetooth/host_long_adv_recv/prj.conf

19 lines
328 B
Plaintext
Raw Normal View History

Bluetooth: Host: Reassemble extended advertising reports The host reassembles fragmented advertising reports from the controller. Non-complete advertising reports from different advertisers may not be interleaved. If non-complete advertising reports from an advertiser is received while advertising reports from another advertiser is reassembled, an error message is logged and the advertising report is discarded. Future scan results may be incomplete. Advertising reports from legacy PDUs or complete extended advertising reports may be interleaved as these do not require reassembly. If the controller sends more advertising data than fits in the reassembly buffer, the data is truncated. Further advertising reports from the advertiser are discarded until the final complete advertising report is received and discarded. Signed-off-by: Herman Berget <herman.berget@nordicsemi.no>
2021-12-20 23:33:49 +08:00
CONFIG_TEST=y
CONFIG_ZTEST=y
CONFIG_BT=y
CONFIG_BT_CTLR=n
CONFIG_BT_HCI=n
CONFIG_BT_HCI_RAW=n
CONFIG_BT_OBSERVER=y
CONFIG_BT_NO_DRIVER=y
Bluetooth: Host: Add choice select whether BT RX Change CONFIG_BT_RECV_IS_RX_THREAD into a choice:CONFIG_BT_RECV_CONTEXT with the following options (names can be discussed further of course): CONFIG_BT_RECV_BLOCKING CONFIG_BT_RECV_WORKQ_BT CONFIG_BT_RECV_WORKQ_SYS This way users would be able to choose what to run most of the BLE stack on, they wouldn't be forced to a single model. We would default to CONFIG_BT_RECV_BLOCKING so that we wouldn't need to change the system workqueue stack size by default, instead asking users to do so if they select the CONFIG_BT_RECV_WORKQ_SYS option Signed-off-by: Lingao Meng <menglingao@xiaomi.com>
2022-03-11 11:12:59 +08:00
CONFIG_BT_RECV_BLOCKING=y
Bluetooth: Host: Reassemble extended advertising reports The host reassembles fragmented advertising reports from the controller. Non-complete advertising reports from different advertisers may not be interleaved. If non-complete advertising reports from an advertiser is received while advertising reports from another advertiser is reassembled, an error message is logged and the advertising report is discarded. Future scan results may be incomplete. Advertising reports from legacy PDUs or complete extended advertising reports may be interleaved as these do not require reassembly. If the controller sends more advertising data than fits in the reassembly buffer, the data is truncated. Further advertising reports from the advertiser are discarded until the final complete advertising report is received and discarded. Signed-off-by: Herman Berget <herman.berget@nordicsemi.no>
2021-12-20 23:33:49 +08:00
CONFIG_BT_EXT_ADV=y
Bluetooth: Tests: Remove usage of `BT_DEBUG_LOG` Remove usage of Kconfig symbol `CONFIG_BT_DEBUG_LOG` from tests. It has been deprecated since this PR: https://github.com/zephyrproject-rtos/zephyr/pull/56183 The Kconfig symbols has been replaced by `CONFIG_LOG=y` on most of the cases. Or it has been removed when not needed anymore. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
2023-06-07 14:10:39 +08:00
CONFIG_LOG=y
Bluetooth: Use Zephyr standard log system instead of `bluetooth/common/log` The `bluetooth/common/log.h` and `bluetooth/common/log.c` files have been removed. Files that were using them have been updated to use `zephyr/logging/log.h` instead. Those replacement have been done consequently: - `/BT_DBG/LOG_DBG/` - `/BT_ERR/LOG_ERR/` - `/BT_WARN/LOG_WRN/` - `/BT_INFO/LOG_INF/` - `/BT_HEXDUMP_DBG/LOG_HEXDUMP_DBG/` - `/BT_DBG_OBJ_ID/LOG_DBG_OBJ_ID/` Also, some files were relying on the `common/log.h` include to include `zephyr/bluetooth/hci.h`, in those cases the include of `hci.h` has been added. For files that were including `common/log.h` but not using any logs, the include has been removed and not replaced. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
2022-11-02 21:31:13 +08:00
CONFIG_BT_HCI_CORE_LOG_LEVEL_DBG=n
CONFIG_BT_HCI_DRIVER_LOG_LEVEL_DBG=n
Bluetooth: Host: Reassemble extended advertising reports The host reassembles fragmented advertising reports from the controller. Non-complete advertising reports from different advertisers may not be interleaved. If non-complete advertising reports from an advertiser is received while advertising reports from another advertiser is reassembled, an error message is logged and the advertising report is discarded. Future scan results may be incomplete. Advertising reports from legacy PDUs or complete extended advertising reports may be interleaved as these do not require reassembly. If the controller sends more advertising data than fits in the reassembly buffer, the data is truncated. Further advertising reports from the advertiser are discarded until the final complete advertising report is received and discarded. Signed-off-by: Herman Berget <herman.berget@nordicsemi.no>
2021-12-20 23:33:49 +08:00
CONFIG_BT_LOG_LEVEL_DBG=y
CONFIG_BT_EXT_SCAN_BUF_SIZE=91