diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2018-04-20 14:44:02 +0200 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2018-05-18 06:37:51 +0200 |
| commit | 1b2525c05bf9c661f6631e598b3bef5ce810085a (patch) | |
| tree | 7ac4ffbfc707825d0377a555b126968894645747 /drivers/acpi/acpi_processor.c | |
| parent | 05ba533c5c1155839cf1538085b67488f1d3d308 (diff) | |
| download | blackbird-op-linux-1b2525c05bf9c661f6631e598b3bef5ce810085a.tar.gz blackbird-op-linux-1b2525c05bf9c661f6631e598b3bef5ce810085a.zip | |
Bluetooth: btbcm: Stop using upper nibble of rev to chose between uart/USB paths
btbcm_setup_patchram() was using the upper nibble of the revision code to
determine if we are dealing with an uart or USB connected bcm-bt device,
but just as btbcm_initialize() has started accepting 1 and 2 as uart
connected devices, I've now encountered an USB connected device (0a5c:216c)
which has 0 in the upper nibble. So it seems that the upper nibble is not
really a reliable indicator of the bus type.
Instead check hdev->bus which does give us a reliable indication. This
fixes the patchram code trying to load the patchram by the fallback BCM.hcd
filename, now it correctly requests BCM43142A0-0a5c-216c.hcd.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/acpi/acpi_processor.c')
0 files changed, 0 insertions, 0 deletions
