summaryrefslogtreecommitdiff
path: root/drivers/bluetooth/Kconfig
diff options
context:
space:
mode:
authorJohan Hovold <johan@kernel.org>2017-10-10 11:01:52 +0300
committerMarcel Holtmann <marcel@holtmann.org>2017-10-10 11:06:26 +0300
commit4294625e029028854596865be401b9c5c1f906ef (patch)
tree9f32ff5e75a3826147be43e7c656cf10dac20a5b /drivers/bluetooth/Kconfig
parente8bfe868cf2cf364f3f52df8fa01aa6d28927aaf (diff)
downloadlinux-4294625e029028854596865be401b9c5c1f906ef.tar.xz
Bluetooth: avoid silent hci_bcm ACPI PM regression
The hci_bcm platform-device hack which was used to implement power management for ACPI devices is being replaced by a serial-device-bus implementation. Unfortunately, when the corresponding change to the ACPI code lands (a change that will stop enumerating and registering the serial-device-node child as a platform device) PM will break silently unless serdev TTY-port controller support has been enabled. Specifically, hciattach (btattach) would still succeed, but power management would no longer work. Although this is strictly a runtime dependency, let's make the driver depend on SERIAL_DEV_CTRL_TTYPORT, which is the particular serdev controller implementation used by the ACPI devices currently managed by this driver, to avoid breaking PM without anyone noticing. Note that the driver already has a (build-time) dependency on the serdev bus code. Signed-off-by: Johan Hovold <johan@kernel.org> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth/Kconfig')
-rw-r--r--drivers/bluetooth/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/bluetooth/Kconfig b/drivers/bluetooth/Kconfig
index fae5a74dc737..082e1c7329de 100644
--- a/drivers/bluetooth/Kconfig
+++ b/drivers/bluetooth/Kconfig
@@ -169,6 +169,7 @@ config BT_HCIUART_BCM
bool "Broadcom protocol support"
depends on BT_HCIUART
depends on BT_HCIUART_SERDEV
+ depends on (!ACPI || SERIAL_DEV_CTRL_TTYPORT)
select BT_HCIUART_H4
select BT_BCM
help