summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2008-07-14 20:13:46 +0200
committerMarcel Holtmann <marcel@holtmann.org>2008-07-14 20:13:46 +0200
commit9dc0a3afc08d6c20c284994dcd84531787d00ec2 (patch)
tree16658484ca53d7fbbf60d0a6c12590a5d3043de9
parentae29319649b80ed9d28d7b4f164e3f5f75020fc8 (diff)
downloadop-kernel-dev-9dc0a3afc08d6c20c284994dcd84531787d00ec2.zip
op-kernel-dev-9dc0a3afc08d6c20c284994dcd84531787d00ec2.tar.gz
[Bluetooth] Support the case when headset falls back to SCO link
When trying to establish an eSCO link between two devices then it can happen that the remote device falls back to a SCO link. Currently this case is not handled correctly and the message dispatching will break since it is looking for eSCO packets. So in case the configured link falls back to SCO overwrite the link type with the correct value. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
-rw-r--r--net/bluetooth/hci_event.c12
1 files changed, 10 insertions, 2 deletions
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
index 0aba21a..6bc5a05 100644
--- a/net/bluetooth/hci_event.c
+++ b/net/bluetooth/hci_event.c
@@ -1314,8 +1314,16 @@ static inline void hci_sync_conn_complete_evt(struct hci_dev *hdev, struct sk_bu
hci_dev_lock(hdev);
conn = hci_conn_hash_lookup_ba(hdev, ev->link_type, &ev->bdaddr);
- if (!conn)
- goto unlock;
+ if (!conn) {
+ if (ev->link_type == ESCO_LINK)
+ goto unlock;
+
+ conn = hci_conn_hash_lookup_ba(hdev, ESCO_LINK, &ev->bdaddr);
+ if (!conn)
+ goto unlock;
+
+ conn->type = SCO_LINK;
+ }
if (!ev->status) {
conn->handle = __le16_to_cpu(ev->handle);
OpenPOWER on IntegriCloud