Bluetooth: Store address information in L2CAP channel structure

Browse source

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>

...

This commit is contained in:

Marcel Holtmann 2013-10-13 08:12:47 -07:00 • committed by Johan Hedberg

parent 4637f7c0d0

commit 7eafc59e2f

3 changed files with 29 additions and 40 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

include/net/bluetooth/l2cap.h

View file

61

net/bluetooth/l2cap_core.c

View file

6

net/bluetooth/l2cap_sock.c

View file