aboutsummaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorMarcel Holtmann <[email protected]>2013-10-06 01:08:57 -0700
committerJohan Hedberg <[email protected]>2013-10-06 10:50:50 +0200
commita5c8f270e4dae14ea5cb88e477ed1092955f8722 (patch)
treee35aedc474c06bb345c049437b322afbc0a226b5 /include/linux
parenta646bd81945b337b1cf37dea4734847947a0d9ad (diff)
Bluetooth: Reject enabling controllers without valid addresses
In case of a single mode LE-only controller it is possible that no public address is used. These type of controllers require a random address to be configured. Without a configured static random address, such a controller is not functional. So reject powering on the controller in this case until it gets configured with a random address. The controller setup stage is still run since it is the only way to determinate if a public address is available or not. So it is similar on how RFKILL gets handled during initial setup of the controller. Signed-off-by: Marcel Holtmann <[email protected]> Signed-off-by: Johan Hedberg <[email protected]>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions