Commit Graph

8 Commits

Author SHA1 Message Date
Gabriel Valcazar 8569d4da9e bluez5: move common files to a common folder for both v5.41 and v5.50
This way, we avoid having to duplicate changes.

https://jira.digi.com/browse/DEL-6448

Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
2019-06-25 17:22:03 +02:00
Isaac Hermida 325c3b9da9 bluez5: add support for qca6564 bluetooth chip
Port the bluez5 qca6564 support based on 5.19 to the current version 5.33.
The ported version is based on qualcomm tag r110048.3.

https://jira.digi.com/browse/DEL-2581

Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
2016-05-31 08:20:51 +02:00
Hector Palacios ee27c907d1 bluez-init: skip BT power GPIO toggling if undefined
The script toggles the BT power GPIO regardless of the value being
undefined.
Check that the GPIO is defined before trying to toggle it.

Signed-off-by: Hector Palacios <hector.palacios@digi.com>
2015-12-28 17:08:18 +01:00
Hector Palacios 84e152f1ca bluez-init: get BT power GPIO basing on compatible module
The BT power GPIOgpio was determined basing on machine name on device tree.
This corresponds to the name of the board, and might be changed by a user
that designs his own carrier board to use the module on.
Besides, the BT power GPIO is a pin that's routed on the module (both on
the ConnectCore 6 and on the ConnectCard for i.MX28) not on the carrier
board.

This commit determines the BT power GPIO basing on the module string inside
the 'compatible' property. This must exactly match the module name and is
a required property for using Digi module's BSP.

Signed-off-by: Hector Palacios <hector.palacios@digi.com>

https://jira.digi.com/browse/DEL-2109
2015-12-28 17:08:18 +01:00
Hector Palacios a10e2a774a bluetooth: bring interface up before launching bluetoothd
If the bluetoothd daemon is launched before the interface is ready
RFCOMM/L2CAP listening socket connections fail (apparently because
the channel is not ready) with BlueZ 5.

Signed-off-by: Hector Palacios <hector.palacios@digi.com>

https://jira.digi.com/browse/DEL-2042
2015-11-30 11:57:34 +01:00
Isaac Hermida 2767f5be7c recipes-connectivity: Splited bluez and btfilter support in two different init scripts
btfilter (abtfilt) and bluetoothd are two independent services. Break the
relationship between them and split the support in independent init scripts

https://jira.digi.com/browse/DEL-1933

Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
2015-11-11 19:54:08 +01:00
Isaac Hermida 599627f214 bluez-init: check on the device tree if the variant has bluetooth
The script was basing on the variant coded in the HWID to determine
if the variant had bluetooth, by comparing to an array of hard-coded variants.
This required the script to be updated with every new variant that supported
Bluetooth.
The patch checks instead if the node 'bluetooth' exists at all in the device tree
to determine if the variant supports Bluetooth.

https://jira.digi.com/browse/DEL-1933

Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
2015-11-11 19:54:08 +01:00
Isaac Hermida 52b4cfe35c recipes-connectivity: moved bluez-init script to bluez recipe
We want to unlink the script from abtfilt application, so moved to a different
recipe (that includes hciattach).

https://jira.digi.com/browse/DEL-1933

Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
2015-11-11 19:54:08 +01:00