Bluetooth: Remove legacy debug symbols
The `BT_DEBUG_*` Kconfig symbols have been deprecated for more than 2 versions, remove them. Update code that was still using them. Remove the Bluetooth specific `Kconfig.template.log_config_bt` and use `Kconfig.template.log_config_inherit` from the logging subsystem instead, now that the legacy symbols can be removed. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
This commit is contained in:
parent
dc376a8bd9
commit
b2e235d530
14 changed files with 105 additions and 813 deletions
|
@ -14,7 +14,8 @@ The Broadcast Assistant will typically be phones or laptops.
|
|||
The Broadcast Assistant scans for periodic advertisements and transfer
|
||||
information to the server.
|
||||
|
||||
It is necessary to have :code:`BT_DEBUG_BAP_BROADCAST_ASSISTANT` enabled for
|
||||
It is necessary to have
|
||||
:kconfig:option:`CONFIG_BT_BAP_BROADCAST_ASSISTANT_LOG_LEVEL_DBG` enabled for
|
||||
using the Broadcast Assistant interactively.
|
||||
|
||||
When the Bluetooth stack has been initialized (:code:`bt init`),
|
||||
|
|
|
@ -11,7 +11,8 @@ synchronization transfer (PAST) protocol.
|
|||
The Scan Delegator server typically resides on devices that have inputs or
|
||||
outputs.
|
||||
|
||||
It is necessary to have :code:`BT_DEBUG_BAP_SCAN_DELEGATOR` enabled for using
|
||||
It is necessary to have
|
||||
:kconfig:option:`CONFIG_BT_BAP_SCAN_DELEGATOR_LOG_LEVEL_DBG` enabled for using
|
||||
the Scan Delegator interactively.
|
||||
|
||||
The Scan Delegator can currently only set the sync state of a receive state, but
|
||||
|
|
|
@ -15,8 +15,8 @@ laptops. The call control client will also thus typically be the advertiser.
|
|||
The client can control the states of calls on a server using the call control
|
||||
point.
|
||||
|
||||
It is necessary to have :code:`BT_DEBUG_TBS_CLIENT` enabled for using the client
|
||||
interactively.
|
||||
It is necessary to have :kconfig:option:`CONFIG_BT_TBS_CLIENT_LOG_LEVEL_DBG`
|
||||
enabled for using the client interactively.
|
||||
|
||||
Using the telephone bearer service client
|
||||
=========================================
|
||||
|
@ -160,8 +160,8 @@ The telephone bearer service is a service that typically resides on devices that
|
|||
can make calls, including calls from apps such as Skype, e.g. (smart)phones and
|
||||
PCs.
|
||||
|
||||
It is necessary to have :code:`BT_DEBUG_TBS` enabled for using the TBS server
|
||||
interactively.
|
||||
It is necessary to have :kconfig:option:`CONFIG_BT_TBS_LOG_LEVEL_DBG` enabled
|
||||
for using the TBS server interactively.
|
||||
|
||||
Using the telephone bearer service
|
||||
==================================
|
||||
|
|
|
@ -36,8 +36,9 @@ read the set information, which is needed to identify other set members.
|
|||
The client can then scan for and connect to the remaining set members, and once
|
||||
all the members has been connected to, it can lock and release the set.
|
||||
|
||||
It is necessary to enable :code:`BT_DEBUG_CSIP_SET_COORDINATOR` to properly use the set
|
||||
coordinator.
|
||||
It is necessary to enable
|
||||
:kconfig:option:`CONFIG_BT_CSIP_SET_COORDINATOR_LOG_LEVEL_DBG` to properly use
|
||||
the set coordinator.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
|
|
|
@ -32,6 +32,12 @@ https://docs.zephyrproject.org/latest/security/vulnerabilities.html
|
|||
API Changes
|
||||
***********
|
||||
|
||||
Removed APIs in this release
|
||||
============================
|
||||
|
||||
* The Bluetooth subsystem specific debug symbols are removed. They have been replaced with the
|
||||
Zephyr logging ones.
|
||||
|
||||
Deprecated in this release
|
||||
==========================
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue