From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Franky Lin <franky.lin@broadcom.com>,
brcm80211-dev-list.pdl@broadcom.com,
linux-wireless@vger.kernel.org,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-rpi-kernel@lists.infradead.org,
Hante Meuleman <hante.meuleman@broadcom.com>,
Ian Molton <ian@mnementh.co.uk>
Subject: Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W
Date: Wed, 26 Jul 2017 10:50:30 +0200 [thread overview]
Message-ID: <597857D6.4010508@broadcom.com> (raw)
In-Reply-To: <314866679.136055.1501049965582@email.1und1.de>
On 7/26/2017 8:19 AM, Stefan Wahren wrote:
> Hi,
>
>> Stefan Wahren <stefan.wahren@i2se.com> hat am 17. Juli 2017 um 22:31 geschrieben:
>>
>>
>> Hi,
>>
>>> Franky Lin <franky.lin@broadcom.com> hat am 17. Juli 2017 um 21:50 geschrieben:
>>>
>>>
>>> On Mon, Jul 17, 2017 at 6:10 AM, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>>>> Hi,
>>>>
>>>>> Stefan Wahren <stefan.wahren@i2se.com> hat am 28. Juni 2017 um 21:33 geschrieben:
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> i'm currently working on Raspberry Pi Zero W for Mainline. Here is my first patch series [1].
>>>>>
>>>>> Unfortunately i didn't get brcmfmac (connected via SDIO) probed with this patch series against 4.12.0-rc5-next-20170616+
>>>>>
>>>>> [ 8.389167] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
>>>>> [ 8.735111] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
>>>>> [ 8.786016] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
>>>>> [ 11.288798] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
>>>>> [ 11.292822] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
>>>>> [ 13.848777] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
>>>>> [ 13.852974] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
>>>>> [ 16.408762] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
>>>>> [ 16.413004] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
>>>>> [ 18.968769] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
>>>>> [ 18.972965] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
>>>>> [ 21.528743] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
>>>>> [ 21.532924] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
>>>>> [ 24.088745] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
>>>>> [ 24.092948] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
>>>>> [ 26.648764] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
>>>>> [ 26.648789] brcmfmac: brcmf_cfg80211_attach: Failed to get D11 version (-110)
>>>>> [ 26.648831] brcmfmac: brcmf_bus_started: failed: -12
>>>>> [ 26.648842] brcmfmac: brcmf_sdio_firmware_callback: dongle is not responding
>>>>>
>>> ...
>>> Can you please try to comment out the following lines in
>>> brcmf_feat_attach? That's the only suspicious line that interact with
>>> firmware in the patch.
>>>
>>> + brcmf_feat_iovar_data_set(ifp, BRCMF_FEAT_GSCAN, "pfn_gscan_cfg",
>>> + &gscan_cfg, sizeof(gscan_cfg));
>>
>> after commenting out this line, the issue doesn't appear.
>>
>
> what are the plans to fix this regression?
I am a bit in doubt about this one. We can avoid the firmware config
above for bcm4343x devices as a short term fix. However, I would like to
root cause the issue. Received a Pi Zero over here so gearing it up.
Regards,
Arend
next prev parent reply other threads:[~2017-07-26 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 19:33 brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W Stefan Wahren
2017-07-17 13:10 ` Stefan Wahren
2017-07-17 19:50 ` Franky Lin
2017-07-17 20:31 ` Stefan Wahren
2017-07-26 6:19 ` Stefan Wahren
2017-07-26 8:50 ` Arend van Spriel [this message]
2017-08-11 5:55 ` Stefan Wahren
2017-08-11 8:24 ` Arend van Spriel
2017-07-18 8:59 ` James Hughes
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=597857D6.4010508@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian@mnementh.co.uk \
--cc=kvalo@codeaurora.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=stefan.wahren@i2se.com \
/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).