Bluetooth: drivers: make H4 and H5 follow CONFIG_BT_HCI_INIT_PRIORITY

In some cases UART drivers might have too high init priorities
so HCI must be initialized even later if used with those.

One example is zephyr,native-tty-uart.

Signed-off-by: Dmitrii Sharshakov <d3dx12.xx@gmail.com>

Author: dsseng

drivers/bluetooth/hci/h4.c

@@ -612,6 +612,6 @@ static DEVICE_API(bt_hci, h4_driver_api) = {
 		}, \
 	}; \
 	DEVICE_DT_INST_DEFINE(inst, NULL, NULL, &h4_data_##inst, &h4_config_##inst, \
-			      POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEVICE, &h4_driver_api)
+			      POST_KERNEL, CONFIG_BT_HCI_INIT_PRIORITY, &h4_driver_api)
 
 DT_INST_FOREACH_STATUS_OKAY(BT_UART_DEVICE_INIT)

drivers/bluetooth/hci/h5.c

@@ -804,7 +804,7 @@ static DEVICE_API(bt_hci, h5_driver_api) = {
 	}; \
 	static struct h5_data h5_##inst; \
 	DEVICE_DT_INST_DEFINE(inst, NULL, NULL, &h5_##inst, &h5_config_##inst, \
-			      POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEVICE, &h5_driver_api)
+			      POST_KERNEL, CONFIG_BT_HCI_INIT_PRIORITY, &h5_driver_api)
 
 
 DT_INST_FOREACH_STATUS_OKAY(BT_UART_DEVICE_INIT)