summaryrefslogtreecommitdiff
path: root/net/bluetooth/hci_sock.c
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2015-03-06 21:11:21 +0300
committerJohan Hedberg <johan.hedberg@intel.com>2015-03-06 21:43:07 +0300
commit93690c227acf08a2a19cbaf9acbcd2210fbb8ded (patch)
treead2744a305b0e5c907a694cdb64984d4143d79cf /net/bluetooth/hci_sock.c
parent82f8b651a94d5c7090563fe55cfdb286c461a16c (diff)
downloadlinux-93690c227acf08a2a19cbaf9acbcd2210fbb8ded.tar.xz
Bluetooth: Introduce controller setting information for static address
Currently it is not possible to determine if the static address is used by the controller. It is also not possible to determine if using a static on a dual-mode controller with disabled BR/EDR is possible or not. To address this issue, introduce a new setting called static-address. If support for this setting is signaled that means that the kernel supports using static addresses. And if used on dual-mode controllers with BR/EDR disabled it means that a configured static address can be used. In addition utilize the same setting for the list of current active settings that indicates if a static address is configured and if that address will be actually used. With this in mind the existing Set Static Address management command has been extended to return the current settings. That way the caller of that command can easily determine if the programmed address will be used or if extra steps are required. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Diffstat (limited to 'net/bluetooth/hci_sock.c')
0 files changed, 0 insertions, 0 deletions