summaryrefslogtreecommitdiff
path: root/drivers/bluetooth/ath3k.c
diff options
context:
space:
mode:
authorDaniel Drake <drake@endlessm.com>2017-01-05 20:10:54 +0300
committerMarcel Holtmann <marcel@holtmann.org>2017-02-16 19:34:17 +0300
commit89ab37b489d11e2ec3a70635139dcda076c16354 (patch)
treeb35600cfdced3408ac00ce11e0a5f6f05eaa337d /drivers/bluetooth/ath3k.c
parent3af3a594e111474fab03d872f41760e10d4c17c4 (diff)
downloadlinux-89ab37b489d11e2ec3a70635139dcda076c16354.tar.xz
Bluetooth: hci_bcm: Add support for BCM2E95 and BCM2E96
The BCM2E96 ID is used by the ECS EF20 laptop, and BCM2E95 is present in the Weibu F3C. Both are now logged as: hci0: BCM: chip id 82 hci0: BCM43341B0 (002.001.014) build 0000 hci0: BCM (002.001.014) build 0158 The ECS vendor kernel predates the host-wakeup support in hci_bcm but it explicitly has a comment saying that the GPIO assignment needs to be reordered for BCM2E96: 1. (not used in vendor driver) 2. Device wakeup 3. Shutdown For both devices in question, the DSDT has these GPIOs listed in order of GpioInt, GpioIo, GpioIo. And if we use the first one listed (GpioInt) as the host wakeup, that interrupt handler fires while doing bluetooth I/O. I am assuming the convention of GPIO ordering has been changed for these new device IDs, so lets use the new ordering on such devices. Signed-off-by: Daniel Drake <drake@endlessm.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth/ath3k.c')
0 files changed, 0 insertions, 0 deletions