From 4c33a85d6ba5288969e606013ee99db37990812f Mon Sep 17 00:00:00 2001 From: Javier Viguera Date: Fri, 30 Aug 2024 18:22:37 +0200 Subject: [PATCH] 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 --- .../bluez/bluez5-init/ccimx9/bluetooth-init.service | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta-digi-dey/recipes-connectivity/bluez/bluez5-init/ccimx9/bluetooth-init.service b/meta-digi-dey/recipes-connectivity/bluez/bluez5-init/ccimx9/bluetooth-init.service index 7766720e2..80e0d1f7a 100644 --- a/meta-digi-dey/recipes-connectivity/bluez/bluez5-init/ccimx9/bluetooth-init.service +++ b/meta-digi-dey/recipes-connectivity/bluez/bluez5-init/ccimx9/bluetooth-init.service @@ -1,8 +1,7 @@ [Unit] Description=Initialization of the IW612 bluetooth chip ConditionPathIsDirectory=/proc/device-tree/bluetooth -Before=bluetooth.service -After=systemd-modules-load.service +After=systemd-udev-settle.service,bluetooth.service [Service] Type=oneshot