All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Jürgen Bausa" <juergen.Bausa@online.de>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: Broadcom 43340 BT support
Date: Wed, 25 Mar 2015 11:44:43 +0100	[thread overview]
Message-ID: <5512919B.9000707@broadcom.com> (raw)
In-Reply-To: <F2171E58-C919-4EEB-9305-6BC3858A7242@holtmann.org>

On 03/25/15 00:42, Marcel Holtmann wrote:
> Hi Juergen,
>
>> I have a laptop (asus x205ta / intel-baytrail) with the broadcom 43340
>> chipset. However, while wireless is working now, bluetooth is not. I am
>> running debian jessie 32 bit with kernel 4.0rc4:
>>
>> root@lina:/home/jba# hciconfig --all
>> hci0:   Type: BR/EDR  Bus: SDIO
>>         BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
>>         DOWN
>>         RX bytes:0 acl:0 sco:0 events:0 errors:0
>>         TX bytes:0 acl:0 sco:0 commands:0 errors:0
>>         Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>>         Packet type: DM1 DH1 HV1
>>         Link policy:
>>         Link mode: SLAVE ACCEPT
>
> can you figure out which driver is claiming that it is SDIO based? I assumed the Baytrail Bluetooth controllers are all attached via UARTs. I didn't know that Broadcom had Bluetooth on SDIO. The WiFi part yes, but the Bluetooth part should be on an UART.

According to documentation SDIO function #3 is providing access to BT 
over SDIO. However, I did not (yet) come across any device that uses 
that. I did find some devices where function #3 cis says BT and btsdio 
claims it, but the BT part is not hooked up to it. So it is either usb 
or uart. For uart our BT group plans to upstream a new driver (something 
they never did before), but have not heard much on that recently.

> Please also check with "rfkill list" if the device might be blocked.
>
> Arend might know more, but you would need to dig into the list of SDIO devices. Sadly I think Linux does not yet have a lssdio tool. So maybe lshw can get us some info on what the kernel thinks about this device. Alternatively you need to dig you sysfs and look at ACPI. Maybe dmesg reveals something useful.

You can confirm it is function #3 of the same mmc device as wifi, but 
chances are BT requires the UART driver.

Regards,
Arend

> Regards
>
> Marcel
>

  reply	other threads:[~2015-03-25 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 21:37 Broadcom 43340 BT support Jürgen Bausa
2015-03-24 23:42 ` Marcel Holtmann
2015-03-25 10:44   ` Arend van Spriel [this message]
2015-03-25 22:31   ` Jürgen Bausa
2015-03-25  2:10 ` fugang.duan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5512919B.9000707@broadcom.com \
    --to=arend@broadcom.com \
    --cc=juergen.Bausa@online.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.