linux/include/net/bluetooth
Johan Hedberg cb1d68f7a3 Bluetooth: Track LE initiator and responder address information
For SMP we need the local and remote addresses (and their types) that
were used to establish the connection. These may be different from the
Identity Addresses or even the current RPA. To guarantee that we have
this information available and it is correct track these values
separately from the very beginning of the connection.

For outgoing connections we set the values as soon as we get a
successful command status for HCI_LE_Create_Connection (for which the
patch adds a command status handler function) and for incoming
connections as soon as we get a LE Connection Complete HCI event.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
2014-02-28 07:53:07 -08:00
..
bluetooth.h Bluetooth: Introduce requirements for security level 4 2014-02-13 09:51:35 +02:00
hci_core.h Bluetooth: Track LE initiator and responder address information 2014-02-28 07:53:07 -08:00
hci_mon.h Bluetooth: Fix coding style in all .h files 2012-03-07 00:04:25 -03:00
hci.h Bluetooth: Use __le64 type for LE random numbers 2014-02-28 12:36:04 +02:00
l2cap.h Bluetooth: Fix updating Identity Address in L2CAP channels 2014-02-18 11:48:55 -08:00
mgmt.h Bluetooth: Use __le64 type for LE random numbers 2014-02-28 12:36:04 +02:00
rfcomm.h Bluetooth: Don't fail RFCOMM tty writes 2014-02-14 13:39:32 -08:00
sco.h Bluetooth: Store SCO address information in its own socket structure 2013-10-13 21:11:20 +03:00