Bug 73081 - Fail to setup Bluetooth on Dell Venue 11 Pro
Summary: Fail to setup Bluetooth on Dell Venue 11 Pro
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-28 06:19 UTC by Jin Yao
Modified: 2016-01-30 15:42 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.14-rc3
Tree: Mainline
Regression: No


Attachments

Description Jin Yao 2014-03-28 06:19:39 UTC
From windows, I can see the wireless chip used on Dell Venue 11 Pro is
"Dell Wireless 1538". I assume the Bluetooth chip is AR3002.

But Iā€™m failed to drive the Bluetooth working with Linux ath3k driver and
ath3k-1.fw firmware.

$hciattach /dev/ttyS1 ath3k 115200 flow
Initialization timed out

% hciattach /dev/ttyS1 any 115200 flow
Device setup complete

But dmesg shows:
Bluetooth: hci0 command 0x1001 tx timeout
Bluetooth: hci0 command 0x1009 tx timeout

% hcitool dev
Devices:

Looks the Bluetooth setup is not successful.

I have already added the ACPI-ID of this device ("DLAC3002") in my kernel.

--- a/drivers/acpi/acpi_platform.c
+++ b/drivers/acpi/acpi_platform.c
@@ -36,6 +36,7 @@ static const struct acpi_device_id acpi_platform_device_ids[] = {
        { "BCM2E1A" },
        { "BCM2E39" },
        { "BCM2E3D" },
+       { "DLAC3002" }

--- a/net/rfkill/rfkill-gpio.c
+++ b/net/rfkill/rfkill-gpio.c
@@ -161,6 +161,7 @@ static const struct acpi_device_id rfkill_acpi_match[] = {
        { "BCM2E1A", RFKILL_TYPE_BLUETOOTH },
        { "BCM2E39", RFKILL_TYPE_BLUETOOTH },
        { "BCM2E3D", RFKILL_TYPE_BLUETOOTH },
+       { "DLAC3002", RFKILL_TYPE_BLUETOOTH },
        { "BCM4752", RFKILL_TYPE_GPS },
        { "LNV4752", RFKILL_TYPE_GPS },
Comment 1 Dmitry Khromov 2015-08-03 20:06:03 UTC
Same here, on Venue 8 Pro.
Actually, the protocol Windows is using is H4, nevertheless, it doesn't work also.
This snippet from DSDT table (BTH0 entry, DLAC3002) specifies the UART settings that Windows (supposedly) uses:
UartSerialBus (0x0001C200, DataBitsEight, StopBitsOne, 0xC0, LittleEndian, ParityTypeNone, FlowControlHardware, 0x0020, 0x0020, "\\_SB.URT1", 0x00, ResourceConsumer, ,)
URT1 is /dev/ttyS4 in my config, the interesting thing is that there's no bytes inbound at all - looks like the BT module is simply unpowered, no matter if I attach an rfkill-gpio (like Jin above), or drive GPIOs manually (via /sys/bus/gpio).
So, it's unlikely a kernel bug (and may be closed as such).

Jin. had you ever succeed in getting this piece working?
Comment 2 Jianlong Liu 2016-01-30 15:41:20 UTC
Same here, not working on Venue 8 Pro. Adding the ACPI ID doesn't result in anything.
Comment 3 Jianlong Liu 2016-01-30 15:42:15 UTC
Forgot to mention, this was tested on kernel 4.4.

Note You need to log in before you can comment on or make changes to this bug.