diff options
author | Hans de Goede <hdegoede@redhat.com> | 2018-03-21 15:53:18 +0300 |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2018-04-01 15:25:32 +0300 |
commit | 6112150261247d9a7d85dda476143985f44f8859 (patch) | |
tree | 17d0cb09c2853a6005f04fc3e0d4d337a21f9526 /drivers/bluetooth/Kconfig | |
parent | a4de1567be322f4fca75e47bb7bd4cd8e3d79657 (diff) | |
download | linux-6112150261247d9a7d85dda476143985f44f8859.tar.xz |
Bluetooth: hci_bcm: Add ACPI HIDs found in Windows .inf files and DSTDs
Now that we need just an ACPI HID in the table, and the driver auto-
configures itself otherwise, we can easily add a bunch of known ACPI HIDs.
This avoids having to add these 1 by 1 as devices with one are encountered
by users.
This commit may seem as if it simply adds all IDs between BCM2E00-BCM2EAC,
but that is not true, all these IDs were found in actual .inf files and
the range is not entirely continuous, the following IDs are not added:
BCM2E6A, BCM2E6C, BCM2E8F and BCM2E91 because I did not see these in any
.inf files. As for the large amount of IDs this seems to be caused by
Broadcom using a separate ID for every bluetooth module using their
chips. E.g. BCM2EA6 seems to be specifically for the Raspberry Pi 3.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth/Kconfig')
0 files changed, 0 insertions, 0 deletions