linux-toradex.git/drivers/bluetooth, branch v4.17

Bluetooth: btusb: Add Dell XPS 13 9360 to btusb_needs_reset_resume_table

2018-04-30T08:56:04+00:00

The Dell XPS 13 9360 uses a QCA Rome chip which needs to be reset
(and have its firmware reloaded) for bluetooth to work after
suspend/resume.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Cc: stable@vger.kernel.org
Cc: Garrett LeSage 
Reported-and-tested-by: Garrett LeSage 
Signed-off-by: Hans de Goede 
Signed-off-by: Marcel Holtmann

Bluetooth: btusb: Only check needs_reset_resume DMI table for QCA rome chipsets

2018-04-30T08:50:45+00:00

Jeremy Cline correctly points out in rhbz#1514836 that a device where the
QCA rome chipset needs the USB_QUIRK_RESET_RESUME quirk, may also ship
with a different wifi/bt chipset in some configurations.

If that is the case then we are needlessly penalizing those other chipsets
with a reset-resume quirk, typically causing 0.4W extra power use because
this disables runtime-pm.

This commit moves the DMI table check to a btusb_check_needs_reset_resume()
helper (so that we can easily also call it for other chipsets) and calls
this new helper only for QCA_ROME chipsets for now.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Cc: stable@vger.kernel.org
Cc: Jeremy Cline 
Suggested-by: Jeremy Cline 
Signed-off-by: Hans de Goede 
Signed-off-by: Marcel Holtmann

Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174"

2018-04-30T08:49:05+00:00

Commit f44cb4b19ed4 ("Bluetooth: btusb: Fix quirk for Atheros
1525/QCA6174") is causing bluetooth to no longer work for several
people, see: https://bugzilla.redhat.com/show_bug.cgi?id=1568911

So lets revert it for now and try to find another solution for
devices which need the modified quirk.

Cc: stable@vger.kernel.org
Cc: Takashi Iwai 
Signed-off-by: Hans de Goede 
Signed-off-by: Marcel Holtmann

Bluetooth: Set HCI_QUIRK_SIMULTANEOUS_DISCOVERY for BTUSB_QCA_ROME

2018-04-01T18:43:02+00:00

QCA Rome controllers can do both LE scan and BR/EDR inquiry at once.

Signed-off-by: Vic Wei 
Signed-off-by: Marcel Holtmann

Bluetooth: btrsi: remove unused including

2018-04-01T18:43:02+00:00

Remove including  that don't need it.

Signed-off-by: Wei Yongjun 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_bcm: Remove DMI quirk for the MINIX Z83-4

2018-04-01T18:43:02+00:00

As Interrupt resource specified IRQs are now assumed to be always
active-low the DMI quirk for the MINIX Z83-4 is no longer required.

Signed-off-by: Ian W MORRISON 
Signed-off-by: Marcel Holtmann

Bluetooth: Remove unused btuart_cs driver

2018-04-01T12:25:32+00:00

With patch 279c936153199 the btuart_cs driver has been deprecated in
favor of serial_cs + hci_uart combination.

  static struct pcmcia_device_id btuart_ids[] = {
         /* don't use this driver. Use serial_cs + hci_uart instead */
         PCMCIA_DEVICE_NULL
  };

Intead of keeping it around, just remove it since it is not even
assigned to any PCMCIA identifiers anymore.

Signed-off-by: Marcel Holtmann 
Signed-off-by: Johan Hedberg

Bluetooth: bpa10x: Use separate h4_recv_buf helper

2018-04-01T12:25:32+00:00

When adding the alignment and padding support for H:4 packet processing
for the Nokia driver, it broke the h4_recv_buf usage within bpa10x
driver. To fix this use a separate helper function and placing it into a
dedicated h4_recv.h header file.

Signed-off-by: Marcel Holtmann 
Signed-off-by: Johan Hedberg

Bluetooth: hci_ll: Convert to use h4_recv_buf helper

2018-04-01T12:25:32+00:00

The HCILL or eHCILL protocol from TI is actually an H:4 protocol with a
few extra events and thus can also use the h4_recv_buf helper. Instead
of open coding the same funtionality add the extra events to the packet
description table and use h4_recv_buf.

Signed-off-by: Marcel Holtmann 
Tested-by: Tony Lindgren 
Signed-off-by: Johan Hedberg

Bluetooth: hci_bcm: Add ACPI HIDs found in Windows .inf files and DSTDs

2018-04-01T12:25:32+00:00

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 
Signed-off-by: Marcel Holtmann