linux-toradex.git/drivers/bluetooth/hci_bcm.c, branch v4.4.56

Bluetooth: hci_bcm: checking for ERR_PTR instead of NULL

2015-10-22T09:32:47+00:00

bt_skb_alloc() returns NULL on error, it never returns an ERR_PTR.

Signed-off-by: Dan Carpenter 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_uart: Provide initial manufacturer information

2015-10-21T04:20:44+00:00

Provide an early indication about the manufacturer information so that
it can be forwarded into monitor channel.

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

Bluetooth: hci_bcm: Enable support for set_diag driver callback

2015-10-08T06:59:16+00:00

The set_diag driver callback allows enabling and disabling the vendor
specific diagnostic information. Since Broadcom chips have support for
a dedicated LM_DIAG channel, hook it up accordingly.

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

Bluetooth: hci_bcm: Enable parsing of LM_DIAG messages

2015-10-08T06:53:16+00:00

The Broadcom UART based controllers can send LM_DIAG messages with the
identifier 0x07 inside the HCI stream. These messages are 63 octets in
size and have no variable payload or length indicator.

This patch adds correct parsing information for the h4_recv_buf handler
and in case these packets are received, they are forwarded to the
Bluetooth core via hci_recv_diag interface.

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

Bluetooth: hci_bcm: Do not test ACPI companion in bcm_acpi_probe()

2015-10-01T08:03:38+00:00

This device has always ACPI companion because driver supports only ACPI
enumeration. Therefore there is no need to test it in bcm_acpi_probe() and
we can pass it directly to acpi_dev_get_resources() (which will return
-EINVAL in case of NULL argument is passed).

Signed-off-by: Jarkko Nikula 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_bcm: Remove needless looking code

2015-10-01T08:03:37+00:00

Tree wide grep for "hci_bcm" doesn't reveal there is any code registering
this platform device and "struct acpi_device_id" use for passing the
platform data looks a debug/test code leftover to me.

I'm assuming this driver effectively supports only ACPI enumeration and
thus test for ACPI_HANDLE() and platform data can be removed.

Signed-off-by: Jarkko Nikula 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_bcm: Remove needless acpi_match_device() call

2015-10-01T08:03:37+00:00

There is no need to call acpi_match_device() in driver's probe path and
verify does it find a match to given ACPI _HIDs in .acpi_match_table as
driver/platform/acpi core code has found the match prior calling the probe.

Signed-off-by: Jarkko Nikula 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_bcm: Handle possible error from acpi_dev_get_resources()

2015-10-01T08:03:37+00:00

Driver doesn't handle possible error from acpi_dev_get_resources(). Test it
and return the error code in case of error.

Signed-off-by: Jarkko Nikula 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_bcm: Add missing acpi_dev_free_resource_list()

2015-10-01T08:03:37+00:00

Caller of acpi_dev_get_resources() should free the constructed resource
list by calling the acpi_dev_free_resource_list() in order to avoid memory
leak.

Signed-off-by: Jarkko Nikula 
Signed-off-by: Marcel Holtmann

Bluetooth: hci_bcm: Add suspend/resume runtime PM functions

2015-09-24T14:25:44+00:00

Adds autosuspend runtime functionality to BCM UART driver.
Autosuspend is enabled at end of bcm_setup.

bcm_device_lock is used for system sleep functions as they can be
called at any time.
bcm_device_lock is not held for runtime suspend functions as this
is only enabled as long as platform device is opened.

Signed-off-by: Frederic Danis 
Signed-off-by: Marcel Holtmann