linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: linux-sunxi <linux-sunxi@googlegroups.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Julian Calaby <julian.calaby@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Olliver Schinagl <oliver+list@schinagl.nl>, <benn@cubietech.com>
Subject: Re: [linux-sunxi] Firmware for Bluetooth (and wifi)
Date: Wed, 8 Jan 2014 10:33:06 +0100	[thread overview]
Message-ID: <52CD1B52.5000101@broadcom.com> (raw)
In-Reply-To: <CAGb2v64+5Rgs6JxD0iH3bcwXPOm-xyS_LSmWLfx0qiMQwreOeQ@mail.gmail.com>

On 01/08/2014 10:23 AM, Chen-Yu Tsai wrote:
> On Wed, Jan 8, 2014 at 4:56 PM, Arend van Spriel <arend@broadcom.com> wrote:
>> On 12/27/2013 01:36 PM, Chen-Yu Tsai wrote:
>>>>>>> Working tree:
>>>>>>>
>>>>>>>   https://github.com/wens/linux/tree/wip/sunxi-next-wifi
>>>>>>>
>>>>>>> Comments welcome :)
>>>>>
>>>>> No comment, but: Nice work!
>>> Thanks. BTW, who should submit the patch? :)
>>
>> Hi Chen-Yu
>>
>> I will submit the patch today.
> 
> Great!
> 
> I added device tree support for brcmfmac SDIO devices,
> to be able to specify external out-of-band interrupts.
> Unfortunately it's not working. I get the following output:
> 
> brcmfmac: brcmf_sdbrcm_bus_rxctl: resumed on timeout
> brcmfmac: brcmf_fil_cmd_data: Failed err=-110
> brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -110
> brcmfmac: brcmf_bus_start: failed: -110
> brcmfmac: brcmf_sdbrcm_probe: dongle is not responding

This is typeical behaviour when interrupt is not picked up.

> brcmfmac: brcmf_sdio_probe: device attach failed
> brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
> 
> Should we add device tree support for the brcmf platform driver,
> so we can enable power, clocks, etc. before the SDIO driver is probed?

How does the device-tree change for oob interrupt look like.

> Not sure if this is the right way. Maxime mentioned on IRC that some
> mmc host drivers take a vmmc regulator property.
> 
> Currently I am using rfkill-gpio to do this. But brcmfmac also
> registers an rfkill of its own.

Not sure what you mean here. The only thing I am aware of is that
cfg80211 registers brcmfmac as wifi transmitter in the rfkill framework,
which is unrelated to gpio's.

> Also, I have bluetooth working. Turns out it was a wrong pinctrl
> setting in my dt. For those who want to try:
> 
>   Get and compile brcm_patchram_plus from
>   http://code.google.com/p/broadcom-bluetooth/
> 
>   Run brcm_patchram_plus --patchram bcm20710a1.hcd --no2bytes /dev/ttyS1
>   and hciattach /dev/ttyS1
> 
>   If brcm_patchram_plus hangs, you may need to reset the controller
>   by blocking then unblocking the bluetooth rfkill switch.
> 
> I pushed all my work out already. Here's the link again:
> 
>   https://github.com/wens/linux/tree/wip/sunxi-next-wifi

I will take a look.

Gr. AvS


  reply	other threads:[~2014-01-08  9:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52A040CE.5040706@schinagl.nl>
     [not found] ` <CAFXj5xjJ0DTa0Qo1avLboQF-e3TFv3aEr_jjkuZjinwuTzXykQ@mail.gmail.com>
     [not found]   ` <52A09B5B.70800@schinagl.nl>
2013-12-05 21:46     ` [linux-sunxi] Firmware for Bluetooth (and wifi) Julian Calaby
2013-12-06  9:00       ` Arend van Spriel
2013-12-18 10:31       ` Arend van Spriel
2013-12-18 13:12         ` Hans de Goede
2013-12-18 16:16           ` Arend van Spriel
2013-12-18 16:39             ` Chen-Yu Tsai
2013-12-19 10:12               ` Chen-Yu Tsai
2013-12-26 16:13                 ` Chen-Yu Tsai
2013-12-26 20:29                   ` Hans de Goede
2013-12-27 11:47                   ` Arend van Spriel
2013-12-27 12:36                     ` Chen-Yu Tsai
2014-01-02 13:59                       ` Arend van Spriel
2014-01-02 17:09                         ` Chen-Yu Tsai
     [not found]                           ` <5ce9ab14-5794-4c0d-a859-7a158655f58e@googlegroups.com>
2014-01-02 19:26                             ` Michal Suchanek
2014-01-02 20:29                             ` Arend van Spriel
2014-01-02 21:03                           ` Arend van Spriel
2014-01-03  3:02                             ` Chen-Yu Tsai
2014-01-08  8:56                       ` Arend van Spriel
2014-01-08  9:23                         ` Chen-Yu Tsai
2014-01-08  9:33                           ` Arend van Spriel [this message]
2014-01-08 10:17                             ` Chen-Yu Tsai
2014-01-23 22:39                           ` Hans de Goede
2014-01-24 10:25                             ` Arend van Spriel
2014-01-24 16:34                               ` Hans de Goede
2014-01-26  8:53                                 ` Arend van Spriel
2014-01-26  8:56                                   ` Arend van Spriel
2014-01-26 10:23                                   ` Hans de Goede
2014-01-26 12:58                                     ` Arend van Spriel
2014-01-26 13:19                                       ` Hans de Goede
2014-01-26 12:07                                   ` Hans de Goede
2014-01-26 15:49                                   ` Hans de Goede
2014-01-26 11:04                                 ` Arend van Spriel
2014-01-26 12:09                                   ` Hans de Goede
2014-01-26 12:50                                     ` Arend van Spriel
2014-01-02 16:52                 ` Michal Suchanek
2014-01-02 17:11                   ` Chen-Yu Tsai

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=52CD1B52.5000101@broadcom.com \
    --to=arend@broadcom.com \
    --cc=benn@cubietech.com \
    --cc=hdegoede@redhat.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=oliver+list@schinagl.nl \
    --cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).