Bluetooth: Host: deprecate bt_le_set_auto_conn()
bt_le_set_auto_conn() function is not working as expected. Also, it doesn't have any test coverage and any usage in sample applications. The function is deprecated Fixes #81597 Signed-off-by: Ivan Iushkov <ivan.iushkov@nordicsemi.no>
This commit is contained in:
parent
a53cb73587
commit
75fc0a0776
6 changed files with 8 additions and 48 deletions
|
@ -73,9 +73,7 @@ To initially discover a device to connect to the application will likely
|
|||
use the :c:func:`bt_le_scan_start` API, wait for an appropriate device
|
||||
to be found (using the scan callback), stop scanning using
|
||||
:c:func:`bt_le_scan_stop` and then connect to the device using
|
||||
:c:func:`bt_conn_le_create`. If the central wants to keep
|
||||
automatically reconnecting to the peripheral it should use the
|
||||
:c:func:`bt_le_set_auto_conn` API.
|
||||
:c:func:`bt_conn_le_create`.
|
||||
|
||||
There are some sample applications for the central role available in the
|
||||
tree, such as :zephyr_file:`samples/bluetooth/central_hr`.
|
||||
|
|
|
@ -33,6 +33,10 @@ Removed APIs in this release
|
|||
Deprecated in this release
|
||||
==========================
|
||||
|
||||
* Deprecated the :c:func:`bt_le_set_auto_conn` API function. Application developers can achieve
|
||||
the same functionality in their application code by reconnecting to the peer when the
|
||||
:c:member:`bt_conn_cb.disconnected` callback is invoked.
|
||||
|
||||
Architectures
|
||||
*************
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue