Bluetooth update for 2.6

Hi Dave,

here are the pending patches that didn't make it into the 2.6.18 kernel release. I have some additional fixes, but all of them need some more additional testing from my side.

Regards

Marcel

Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git

This will update the following files:

 drivers/bluetooth/bfusb.c        |  316 +++++++++++++++++++--------------------
 drivers/bluetooth/hci_ldisc.c    |   13 -
 drivers/bluetooth/hci_usb.c      |    3 
 drivers/bluetooth/hci_vhci.c     |   99 ++++++------
 include/net/bluetooth/hci.h      |    5 
 include/net/bluetooth/hci_core.h |    6 
 net/bluetooth/bnep/core.c        |   26 ++-
 net/bluetooth/hci_conn.c         |    8 
 net/bluetooth/hci_event.c        |    1 
 net/bluetooth/hci_sysfs.c        |  117 ++++++++++++--
 net/bluetooth/hidp/core.c        |   23 ++
 net/bluetooth/rfcomm/tty.c       |   21 ++
 12 files changed, 400 insertions(+), 238 deletions(-)

through these ChangeSets:

Marcel Holtmann <[email protected]> Thu, 21 Sep 2006 16:23:19 +0200

[Bluetooth] Code cleanup for the HCI UART driver

This patch cleans up the Bluetooth HCI UART driver a bit.

Marcel Holtmann <[email protected]> Thu, 21 Sep 2006 16:19:55 +0200

[Bluetooth] Add support for Canyon CN-BTU1 dongle

This patch adds the vendor and product id of the Canycon CN-BTU1 dongle and sets a flag to send HCI_Reset as the first command.

Marcel Holtmann <[email protected]> Thu, 21 Sep 2006 16:04:00 +0200

[Bluetooth] Handle command complete event for exit periodic inquiry

The command complete event of the exit periodic inquiry command must clear the HCI_INQUIRY flag and finish the HCI request.

Marcel Holtmann <[email protected]> Sat, 08 Jul 2006 13:57:15 +0200

[Bluetooth] Add HCI device identifier for SDIO cards

This patch assigns the next free HCI device identifier to Bluetooth devices based on the SDIO interface.

Marcel Holtmann <[email protected]> Thu, 06 Jul 2006 15:45:23 +0200

[Bluetooth] Code cleanup of the drivers source code

This patch is an attempt to cleanup the drivers source code to make all Bluetooth drivers look more unique.

Marcel Holtmann <[email protected]> Thu, 06 Jul 2006 13:09:02 +0200

[Bluetooth] Integrate services into the driver model

This patch integrates the services of the Bluetooth protocols RFCOMM, BNEP and HIDP into the driver model. This makes it possible to assign the virtual TTY, network and input devices to a specific Bluetooth connection.

Marcel Holtmann <[email protected]> Thu, 06 Jul 2006 12:38:46 +0200

[Bluetooth] Integrate low-level connections into the driver model

This patch integrates the low-level connections (ACL and SCO) into the driver model. Every connection is presented as device with the parent set to its host controller device.

Marcel Holtmann <[email protected]> Thu, 06 Jul 2006 12:34:41 +0200

[Bluetooth] Remove unused host controller attributes

This patch removes the unused device attribute entries for the Bluetooth host controllers.

Hi Dave,

it seems that you haven't pulled in these changes so far. So I didn't rebase the tree and simply pushed some additional ones on top of it. All three of them address the issues we had with non-blocking connects.

Regards

Marcel

Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git

This will update the following files:

 include/net/bluetooth/hci.h      |    6 ++++++
 include/net/bluetooth/hci_core.h |   12 +++++++++---
 net/bluetooth/af_bluetooth.c     |    2 +-
 net/bluetooth/hci_conn.c         |   31 +++++++++++++++++++++++++++----
 net/bluetooth/hci_core.c         |    3 +++
 net/bluetooth/hci_event.c        |   25 ++++++++++++++++++++++++-
 net/bluetooth/hci_sysfs.c        |   24 ++++++++++++++++++++++++
 net/bluetooth/rfcomm/core.c      |    2 +-
 8 files changed, 95 insertions(+), 10 deletions(-)

through these ChangeSets:

Marcel Holtmann <[email protected]> Tue, 26 Sep 2006 09:43:48 +0200

[Bluetooth] Support create connection cancel command

In case of non-blocking connects it is possible that the last user of an ACL link quits before the connection has been fully established. This will lead to a race condition where the internal state of a connection is closed, but the actual link has been established and is active. In case of Bluetooth 1.2 and later devices it is possible to call create connection cancel to abort the connect. For older devices the disconnect timer will be used to trigger the needed disconnect.

Marcel Holtmann <[email protected]> Sat, 23 Sep 2006 09:57:20 +0200

[Bluetooth] Read local version information on device init

The local version information are needed to identify certain feature sets of devices. They must be read on device init and stored for later use. It is also possible to access them through the device model.

Marcel Holtmann <[email protected]> Sat, 23 Sep 2006 09:54:38 +0200

[Bluetooth] Return EINPROGRESS for non-blocking socket calls

In case of non-blocking socket calls we should return EINPROGRESS and not EAGAIN.

From: Marcel Holtmann <[email protected]>
Date: Tue, 26 Sep 2006 12:46:21 +0200

I applied all of your fixes into my tree, sorry for taking so long.

Hi Dave,

no big problem. If you haven't synced with Linus yet, then I have two small additional fixes that should go in with the others.

Regards

Marcel

Please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git

This will update the following files:

 net/bluetooth/hci_event.c |    8 ++++----
 net/bluetooth/hci_sysfs.c |    2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

through these ChangeSets:

Marcel Holtmann <[email protected]> Thu, 28 Sep 2006 20:23:29 +0200

[Bluetooth] Fix section mismatch of bt_sysfs_cleanup()

The bt_sysfs_cleanup() is marked with __exit attribute, but it will be called from an __init function in the error case. So the __exit attribute must be removed.

Marcel Holtmann <[email protected]> Tue, 26 Sep 2006 22:18:03 +0200

[Bluetooth] Don't update disconnect timer for incoming connections

In the case of device pairing the only safe method is to establish a low-level ACL link. In this case, the remote side should not use the disconnect timer to give the other side the chance to enter the PIN code. If the disconnect timer is used, the connection will be dropped to soon, because it is impossible to identify an actual user of this link.

From: Marcel Holtmann <[email protected]>
Date: Thu, 28 Sep 2006 23:14:44 +0200

I've applied these 2 changes as patches to my tree, thanks a lot.