Searched hist:"162 a3bac" (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/net/bluetooth/ |
H A D | mgmt.c | 162a3bac Wed Jan 14 17:43:11 CST 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Bind the SMP channel registration to management power state
When the controller gets powered on via the management interface, then register the supported SMP channels. There is no point in registering these channels earlier since it is not know what identity address the controller is going to operate with.
When powering down a controller unregister all SMP channels. This is required since a powered down controller is allowed to change its identity address.
In addition the SMP channels are only available when the controller is powered via the management interface. When using legacy ioctl, then Bluetooth Low Energy is not supported and registering kernel side SMP integration may actually cause confusion.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 162a3bac Wed Jan 14 17:43:11 CST 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Bind the SMP channel registration to management power state When the controller gets powered on via the management interface, then register the supported SMP channels. There is no point in registering these channels earlier since it is not know what identity address the controller is going to operate with. When powering down a controller unregister all SMP channels. This is required since a powered down controller is allowed to change its identity address. In addition the SMP channels are only available when the controller is powered via the management interface. When using legacy ioctl, then Bluetooth Low Energy is not supported and registering kernel side SMP integration may actually cause confusion. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|
H A D | hci_core.c | 162a3bac Wed Jan 14 17:43:11 CST 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Bind the SMP channel registration to management power state
When the controller gets powered on via the management interface, then register the supported SMP channels. There is no point in registering these channels earlier since it is not know what identity address the controller is going to operate with.
When powering down a controller unregister all SMP channels. This is required since a powered down controller is allowed to change its identity address.
In addition the SMP channels are only available when the controller is powered via the management interface. When using legacy ioctl, then Bluetooth Low Energy is not supported and registering kernel side SMP integration may actually cause confusion.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 162a3bac Wed Jan 14 17:43:11 CST 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Bind the SMP channel registration to management power state When the controller gets powered on via the management interface, then register the supported SMP channels. There is no point in registering these channels earlier since it is not know what identity address the controller is going to operate with. When powering down a controller unregister all SMP channels. This is required since a powered down controller is allowed to change its identity address. In addition the SMP channels are only available when the controller is powered via the management interface. When using legacy ioctl, then Bluetooth Low Energy is not supported and registering kernel side SMP integration may actually cause confusion. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|