summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2013-10-13 15:12:47 (GMT)
committerJohan Hedberg <johan.hedberg@intel.com>2013-10-13 15:52:01 (GMT)
commit7eafc59e2f547fce3a31b3e2d03c14d57e9162b2 (patch)
treea4c694fb05f051d3dda4a50f7dcf0a021d6ac039 /include
parent4637f7c0d0e95361f25f456b34cc2138fdfe95f8 (diff)
downloadlinux-fsl-qoriq-7eafc59e2f547fce3a31b3e2d03c14d57e9162b2.tar.xz
Bluetooth: Store address information in L2CAP channel structure
With the effort of abstracting the L2CAP socket from the underlying L2CAP channel it is important to store the source and destination address information directly in the L2CAP channel structure. Direct access to the HCI connection address information is not possible since they might not be avaiable at L2CAP channel creation time. The address information will be updated when the underlying BR/EDR or LE connection status changes. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Diffstat (limited to 'include')
-rw-r--r--include/net/bluetooth/l2cap.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
index 1a929af..26b5066 100644
--- a/include/net/bluetooth/l2cap.h
+++ b/include/net/bluetooth/l2cap.h
@@ -444,6 +444,8 @@ struct l2cap_chan {
__u8 state;
+ bdaddr_t dst;
+ bdaddr_t src;
__le16 psm;
__u16 dcid;
__u16 scid;