diff options
| author | Jaikumar Ganesh <jaikumar@google.com> | 2010-11-09 19:07:45 -0800 |
|---|---|---|
| committer | Jaikumar Ganesh <jaikumar@google.com> | 2010-11-10 15:59:50 -0800 |
| commit | 901204dc1797ec61c066ce9afecc56d6e874c187 (patch) | |
| tree | b14fbd9642c6a64b4a33594f437492122e608ac9 /include/net/bluetooth/l2cap.h | |
| parent | dfa196f0e99696d22a4329ea3494175740904a26 (diff) | |
Bluetooth: Add BT_POWER L2CAP socket option.
Add BT_POWER socket option used to control the power
characteristics of the underlying ACL link. When the remote end
has put the link in sniff mode and the host stack wants to send
data we need need to explicitly exit sniff mode to work well with
certain devices (For example, A2DP on Plantronics Voyager 855).
However, this causes problems with HID devices.
Hence, moving into active mode when sending data, irrespective
of who set the sniff mode has been made as a socket option. By
default, we will move into active mode. HID devices can set the
L2CAP socket option to prevent this from happening.
Currently, this has been implemented for L2CAP sockets. This has been
tested with incoming and outgoing L2CAP sockets for HID and A2DP.
Based on discussions on linux-bluetooth and patches submitted by
Andrei Emeltchenko.
Signed-off-by: Jaikumar Ganesh <jaikumar@google.com>
Diffstat (limited to 'include/net/bluetooth/l2cap.h')
| -rw-r--r-- | include/net/bluetooth/l2cap.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h index 8f8e648032e8..22885e05a826 100644 --- a/include/net/bluetooth/l2cap.h +++ b/include/net/bluetooth/l2cap.h @@ -329,6 +329,7 @@ struct l2cap_pinfo { __u8 role_switch; __u8 force_reliable; __u8 flushable; + __u8 force_active; __u8 conf_req[64]; __u8 conf_len; |