Commit 3b6a15a2 authored by Emil Gydesen's avatar Emil Gydesen Committed by Benjamin Cabé
Browse files

samples: Bluetooth: Rename BLE to Bluetooth (LE) where applicable 



The BLE acronym is not an official description of Bluetooth
LE, and the Bluetooth SIG only ever refers to it as Bluetooth
Low Energy or Bluetooth LE, so Zephyr should as well.

This commit does not change any board or vendor specific
samples, and the term BLE may still be used in those.
It will be up to the vendors to update it if they want,
since many of them are using the term BLE in their
products.

Signed-off-by: default avatarEmil Gydesen <emil.gydesen@nordicsemi.no>
parent bf95ad47

samples/bluetooth/central_multilink/README.rst

+1 −1
Original line number Diff line number Diff line
@@ -8,7 +8,7 @@ Overview 
********



Application demonstrating Bluetooth LE Central role functionality by scanning for other

BLE devices and establishing connection to up to 62 peripherals with a strong

Bluetooth LE devices and establishing connection to up to 62 peripherals with a strong

enough signal.



Requirements

samples/bluetooth/hci_uart/README.rst

+2 −2
Original line number Diff line number Diff line
@@ -33,11 +33,11 @@ Zephyr tree, and it is built as a standard Zephyr application. 
Using the controller with emulators and BlueZ

*********************************************



The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE

The instructions below show how to use a Nordic nRF5x device as a Zephyr Bluetooth

controller and expose it to Linux's BlueZ. This can be very useful for testing

the Zephyr Link Layer with the BlueZ Host. The Zephyr Bluetooth LE controller can also

provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native

BLE support or QEMU-based development.

Bluetooth support or QEMU-based development.



First, make sure you have a recent BlueZ version installed by following the

instructions in the :ref:`bluetooth_bluez` section.

samples/bluetooth/hci_uart/src/main.c

+1 −1
Original line number Diff line number Diff line
@@ -54,7 +54,7 @@ static K_FIFO_DEFINE(uart_tx_queue); 
#define ST_DISCARD 3	/* Dropping packet. */



/* Length of a discard/flush buffer.

 * This is sized to align with a BLE HCI packet:

 * This is sized to align with a Bluetooth HCI packet:

 * 1 byte H:4 header + 32 bytes ACL/event data

 * Bigger values might overflow the stack since this is declared as a local

 * variable, smaller ones will force the caller to call into discard more

samples/bluetooth/hci_uart_3wire/README.rst

+2 −2
Original line number Diff line number Diff line
@@ -33,11 +33,11 @@ Zephyr tree, and it is built as a standard Zephyr application. 
Using the controller with emulators and BlueZ

*********************************************



The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE

The instructions below show how to use a Nordic nRF5x device as a Zephyr Bluetooth

controller and expose it to Linux's BlueZ. This can be very useful for testing

the Zephyr Link Layer with the BlueZ Host. The Zephyr Bluetooth LE controller can also

provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native

BLE support or QEMU-based development.

Bluetooth support or QEMU-based development.



First, make sure you have a recent BlueZ version installed by following the

instructions in the :ref:`bluetooth_bluez` section.

samples/bluetooth/hci_uart_async/README.rst

+1 −1
Original line number Diff line number Diff line
@@ -36,7 +36,7 @@ in the Zephyr tree and is built as a standard Zephyr application. 
Using the controller with emulators and BlueZ

*********************************************



The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE

The instructions below show how to use a Nordic nRF5x device as a Zephyr Bluetooth

controller and expose it to Linux's BlueZ.



First, make sure you have a recent BlueZ version installed by following the

CRA Git | Maintained and supported by SUSTech CRA and CCSE