linux-toradex.git/net/bluetooth/hci_sysfs.c, branch v2.6.27.20

[Bluetooth] Fix userspace breakage due missing class links

2008-08-18T11:23:53+00:00

The Bluetooth adapters and connections are best presented via a class
in sysfs. The removal of the links inside the Bluetooth class broke
assumptions by userspace programs on how to find attached adapters.

This patch creates adapters and connections as part of the Bluetooth
class, but it uses different device types to distinguish them. The
userspace programs can now easily navigate in the sysfs device tree.

The unused platform device and bus have been removed to keep the
code simple and clean.

Signed-off-by: Marcel Holtmann

bluetooth: remove improper bluetooth class symlinks.

2008-07-22T04:54:51+00:00

Don't create symlinks in a class to a device that is not owned by the
class.  If the bluetooth subsystem really wants to point to all of the
devices it controls, it needs to create real devices, not fake symlinks.

Cc: Maxim Krasnyansky 
Cc: Kay Sievers 
Acked-by: Marcel Holtmann 
Signed-off-by: Greg Kroah-Hartman

[Bluetooth] Use a more unique bus name for connections

2008-07-14T18:13:51+00:00

When attaching Bluetooth low-level connections to the bus, the bus name
is constructed from the remote address since at that time the connection
handle is not assigned yet. This has worked so far, but also caused a
lot of troubles. It is better to postpone the creation of the sysfs
entry to the time when the connection actually has been established
and then use its connection handle as unique identifier.

This also fixes the case where two different adapters try to connect
to the same remote device.

Signed-off-by: Marcel Holtmann

[Bluetooth] Export remote Simple Pairing mode via sysfs

2008-07-14T18:13:49+00:00

Since the remote Simple Pairing mode is stored together with the
inquiry cache, it makes sense to show it together with the other
information.

Signed-off-by: Marcel Holtmann

bluetooth: do not move child device other than rfcomm

2008-02-19T04:45:41+00:00

hci conn child devices other than rfcomm tty should not be moved here.
This is my lost, thanks for Barnaby's reporting and testing.

Signed-off-by: Dave Young  
Signed-off-by: David S. Miller

bluetooth: put hci dev after del conn

2008-02-19T04:44:01+00:00

Move hci_dev_put to del_conn to avoid hci dev going away before hci conn.

Signed-off-by: Dave Young 
Signed-off-by: David S. Miller

[BLUETOOTH] hci_sysfs.c: Kill build warning.

2008-02-18T08:20:50+00:00

net/bluetooth/hci_sysfs.c: In function ‘del_conn’:
net/bluetooth/hci_sysfs.c:339: warning: suggest parentheses around assignment used as truth value

Signed-off-by: David S. Miller

[BLUETOOTH]: Fix bugs in previous conn add/del workqueue changes.

2008-02-01T03:28:33+00:00

Jens Axboe noticed that we were queueing &conn->work on both btaddconn
and keventd_wq.

Signed-off-by: Dave Young 
Signed-off-by: David S. Miller

[BLUETOOTH]: Add conn add/del workqueues to avoid connection fail.

2008-02-01T03:27:12+00:00

The bluetooth hci_conn sysfs add/del executed in the default
workqueue.  If the del_conn is executed after the new add_conn with
same target, add_conn will failed with warning of "same kobject name".

Here add btaddconn & btdelconn workqueues, flush the btdelconn
workqueue in the add_conn function to avoid the issue.

Signed-off-by: Dave Young 
Signed-off-by: David S. Miller

[BLUETOOTH]: Move children of connection device to NULL before connection down.

2008-01-23T11:11:39+00:00

The rfcomm tty device will possibly retain even when conn is down, and
sysfs doesn't support zombie device moving, so this patch move the tty
device before conn device is destroyed.

For the bug refered please see :
http://lkml.org/lkml/2007/12/28/87

Signed-off-by: Dave Young 
Signed-off-by: David S. Miller