Linux wireless drivers development
 help / color / mirror / Atom feed
From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: brcm80211-dev-list.pdl@broadcom.com, linux-wireless@vger.kernel.org
Subject: Current mainline brcmfmac reports error on supposedly supported ap6256 chip
Date: Sat, 24 Jul 2021 15:22:38 +0200	[thread overview]
Message-ID: <DAA2C28E-0CF2-4A1C-9110-BDEB85ADC09B@gmail.com> (raw)

Dears,

I working on adding support in mainline kernel for radxa-zero SBC.
https://www.cnx-software.com/2021/06/16/radxa-zero-sbc-quad-core-raspberry-pi-zero-w-alternative/  

So far all seems to be working well on mainline 5.13.4 kernel except WiFi.

radxa-zero SBC uses SDIO attached AP6256 WiFi/BT module.
Chip seems to be communicating with brcmfmac driver - but kernel dmesg reports error like below.

(output is after kernel compile with:

CONFIG_BRCM_TRACING=y
CONFIG_BRCMDBG=y

and

echo 8 > /proc/sys/kernel/printk
modprobe brcmfmac debug=0x6)


5.13.4 dmesg from brcmfmac probing:

[  138.188502] brcmfmac: brcmfmac_module_init No platform data available.
[  138.189917] brcmfmac: brcmf_sdio_probe Enter
[  138.194049] brcmfmac: F1 signature read @0x18000000=0x15294345
[  138.199709] brcmfmac: brcmf_chip_recognition found AXI chip: BCM4345/9
[  138.207838] brcmfmac: brcmf_chip_cores_check  [1 ] core 0x800:51 base 0x18000000 wrap 0x18100000
[  138.214720] brcmfmac: brcmf_chip_cores_check  [2 ] core 0x812:54 base 0x18001000 wrap 0x18101000
[  138.223405] brcmfmac: brcmf_chip_cores_check  [3 ] core 0x83e:9  base 0x18002000 wrap 0x18102000
[  138.232112] brcmfmac: brcmf_chip_cores_check  [4 ] core 0x83c:14 base 0x18003000 wrap 0x18103000
[  138.240834] brcmfmac: brcmf_chip_cores_check  [5 ] core 0x829:21 base 0x18004000 wrap 0x18104000
[  138.249534] brcmfmac: brcmf_chip_cores_check  [6 ] core 0x135:0  base 0x00000000 wrap 0x18107000
[  138.258248] brcmfmac: brcmf_chip_cores_check  [7 ] core 0x240:0  base 0x00000000 wrap 0x00000000
[  138.266957] brcmfmac: brcmf_chip_set_passive Enter
[  138.274227] brcmfmac: brcmf_chip_get_raminfo RAM: base=0x198000 size=0 (0x0) sr=0 (0x0)
[  138.279634] brcmfmac: brcmf_chip_get_raminfo: RAM size is undetermined
[  138.286085] brcmfmac: brcmf_sdio_probe_attach: brcmf_chip_attach failed!
[  138.292725] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed
[  138.299190] brcmfmac: brcmf_sdio_remove Enter
[  138.303476] brcmfmac: brcmf_detach Enter
[  138.307444] brcmfmac: brcmf_sdio_remove Disconnected
[  138.312361] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
[  138.319198] usbcore: registered new interface driver brcmfmac

i tested fw ver 7.45.96.61 and also a bit newer ver. (7.45.96.68). both are giving the same error. removing firmware changes nothing - so i think issue is in frcmfmac kernel code which is not ready yet for chip variant used in radxa-zero ap6256 wifi module.

Full kernel dmesg: https://pastebin.com/VT1tQUJY 

May you pls advise me how to move forward with this issue?


             reply	other threads:[~2021-07-24 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 13:22 Piotr Oniszczuk [this message]
     [not found] <CB0AA0D2-A8F3-4217-A3C1-E14D7E9FF11E@gmail.com>
     [not found] ` <17ad94781a0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
     [not found]   ` <6F6333F3-0BDB-48AF-B445-723958ABA8C9@gmail.com>
     [not found]     ` <be6c2b7f-2c85-59fb-3013-d0590c487c51@broadcom.com>
     [not found]       ` <53E7119F-D158-4EF0-940C-D0AA59C23CF6@gmail.com>
2021-07-26  7:54         ` Current mainline brcmfmac reports error on supposedly supported ap6256 chip Arend van Spriel
     [not found]           ` <286E2774-FAA5-47E3-A1FC-FDB09EB37FDC@gmail.com>
2021-07-26  9:37             ` Arend van Spriel
2021-07-26  9:39               ` Arend van Spriel
2021-07-26 12:21                 ` Piotr Oniszczuk
2021-07-26 12:31                   ` Arend van Spriel
2021-07-26  9:53           ` Piotr Oniszczuk

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=DAA2C28E-0CF2-4A1C-9110-BDEB85ADC09B@gmail.com \
    --to=piotr.oniszczuk@gmail.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=linux-wireless@vger.kernel.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