From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Ondrej Jirman <megous@megous.com>
Subject: Re: Current mainline brcmfmac reports error on supposedly supported ap6256 chip
Date: Mon, 26 Jul 2021 09:54:07 +0200 [thread overview]
Message-ID: <3da7f271-0c5c-50de-375a-a8c67ca127f5@broadcom.com> (raw)
In-Reply-To: <53E7119F-D158-4EF0-940C-D0AA59C23CF6@gmail.com>
+ linux-wireless, + Ondrej (who added support for 4345 rev 9)
On 7/25/2021 12:16 AM, Piotr Oniszczuk wrote:
>
>
>> Wiadomość napisana przez Arend van Spriel <arend.vanspriel@broadcom.com> w dniu 24.07.2021, o godz. 23:20:
>>
>>
>> I am not so sure what is going on so maybe you can apply the patch below and see what comes out.
>>
>> Regards,
>> Arend
>>
>> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
>> index 4faab0170ffa..71fb34753528 100644
>> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
>> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
>> @@ -691,9 +691,11 @@ static u32 brcmf_chip_tcm_ramsize(struct brcmf_core_priv *cr4)
>> nbb = (corecap & ARMCR4_TCBBNB_MASK) >> ARMCR4_TCBBNB_SHIFT;
>> totb = nab + nbb;
>>
>> + brcmf_err("corecap %x nab %u nbb %u\n", corecap, nab, nbb);
>> for (idx = 0; idx < totb; idx++) {
>> brcmf_chip_core_write32(cr4, ARMCR4_BANKIDX, idx);
>> bxinfo = brcmf_chip_core_read32(cr4, ARMCR4_BANKINFO);
>> + brcmf_err("[%3u] %08x\n", idx, bxinfo);
>> memsize += ((bxinfo & ARMCR4_BSZ_MASK) + 1) * ARMCR4_BSZ_MULT;
>> }
>>
>>
>
> Arend
>
> Pls find dmesg output with patch:
>
> [ 121.226458] brcmfmac: brcmfmac_module_init No platform data available.
> [ 121.227955] brcmfmac: brcmf_sdio_probe Enter
> [ 121.232119] brcmfmac: F1 signature read @0x18000000=0x15294345
> [ 121.237659] brcmfmac: brcmf_chip_recognition found AXI chip: BCM4345/9
> [ 121.245832] brcmfmac: brcmf_chip_cores_check [1 ] core 0x800:51 base 0x18000000 wrap 0x18100000
> [ 121.252695] brcmfmac: brcmf_chip_cores_check [2 ] core 0x812:54 base 0x18001000 wrap 0x18101000
> [ 121.261363] brcmfmac: brcmf_chip_cores_check [3 ] core 0x83e:9 base 0x18002000 wrap 0x18102000
> [ 121.270071] brcmfmac: brcmf_chip_cores_check [4 ] core 0x83c:14 base 0x18003000 wrap 0x18103000
> [ 121.278783] brcmfmac: brcmf_chip_cores_check [5 ] core 0x829:21 base 0x18004000 wrap 0x18104000
> [ 121.287508] brcmfmac: brcmf_chip_cores_check [6 ] core 0x135:0 base 0x00000000 wrap 0x18107000
> [ 121.296206] brcmfmac: brcmf_chip_cores_check [7 ] core 0x240:0 base 0x00000000 wrap 0x00000000
> [ 121.304917] brcmfmac: brcmf_chip_set_passive Enter
> [ 121.312079] brcmfmac: brcmf_chip_tcm_ramsize: corecap 0 nab 0 nbb 0
Well. That explains the fact that RAM size ends up being zero. I want to
be sure the ARM CR4 core is up so can you retry using the patch below.
It is just getting bit more info, no fix.
Regards,
Arend
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
index 4faab0170ffa..b829ad2f3865 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c
@@ -691,9 +691,12 @@ static u32 brcmf_chip_tcm_ramsize(struct
brcmf_core_priv *cr4)
nbb = (corecap & ARMCR4_TCBBNB_MASK) >> ARMCR4_TCBBNB_SHIFT;
totb = nab + nbb;
+ brcmf_err("up %d corecap %x nab %u nbb %u\n",
+ brcmf_chip_iscoreup(&cr4->pub), corecap, nab, nbb);
for (idx = 0; idx < totb; idx++) {
brcmf_chip_core_write32(cr4, ARMCR4_BANKIDX, idx);
bxinfo = brcmf_chip_core_read32(cr4, ARMCR4_BANKINFO);
+ brcmf_err("[%3u] %08x\n", idx, bxinfo);
memsize += ((bxinfo & ARMCR4_BSZ_MASK) + 1) *
ARMCR4_BSZ_MULT;
}
next parent reply other threads:[~2021-07-26 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Arend van Spriel [this message]
[not found] ` <286E2774-FAA5-47E3-A1FC-FDB09EB37FDC@gmail.com>
2021-07-26 9:37 ` Current mainline brcmfmac reports error on supposedly supported ap6256 chip 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
2021-07-24 13:22 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=3da7f271-0c5c-50de-375a-a8c67ca127f5@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=megous@megous.com \
--cc=piotr.oniszczuk@gmail.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