meta-digi/meta-digi-dey/recipes-connectivity/bluez/bluez5-init
Javier Viguera 4c33a85d6b bluetooth-init: start driver load service after bluetooth daemon
The bluetooth daemon does not need the interface to exist before being
executed. We configure the daemon with AutoEnable=true, which will enable
adapters present on start or that appear later on.

On shutdown, systemd stops services in the opposite order to the boot,
so configuring the driver load service after the bluetooth service,
ensures that on shutdown the driver is unloaded before the bluetooth
daemon is stopped.

The btnxpuart driver needs this order, to prevent a module unload failure
on system reboot/poweroff.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2024-08-30 18:22:37 +02:00
..
ccimx6 bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx6sbc bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx6ul bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx8m bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx8x bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx9 bluetooth-init: start driver load service after bluetooth daemon 2024-08-30 18:22:37 +02:00
use-mainline-bsp bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
bluetooth-init.service bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00