From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Vanessa Maegima <vanessa.maegima@nxp.com>,
"van.ayumi@gmail.com" <van.ayumi@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"embed3d@gmail.com" <embed3d@gmail.com>
Subject: Re: AP6335 with mainline kernel
Date: Thu, 30 Nov 2017 13:31:19 +0100 [thread overview]
Message-ID: <5A1FFA17.6000703@broadcom.com> (raw)
In-Reply-To: <1511450638.9102.1.camel@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]
On 11/23/2017 4:24 PM, Vanessa Maegima wrote:
>>>>>> Buildroot:
>>>>>> # dmesg | grep brcmfmac
>>>>>> [ 5.343118] brcmfmac: brcmf_fw_map_chip_to_name: using
>>>>>> brcm/brcmfmac4339-sdio.bin for chip 0x00433
>>>>>> 9(17209) rev 0x000002
>>>>>> [ 6.420070] brcmfmac: brcmf_sdio_htclk: HT Avail timeout
>>>>>> (1000000):
>>>>>> clkctl 0x50
>>>>>> [ 6.427722] brcmfmac: brcmf_sdio_htclk: pmucontrol =
>>>>>> 01774381
>>>>>> [ 6.434865] brcmfmac: brcmf_sdio_htclk: pmustatus =
>>>>>> 0000002a
>>>>>> [ 6.441174] brcmfmac: brcmf_sdio_htclk: min_res_mask =
>>>>>> 0fcaff77
>>>>>> [ 6.447379] brcmfmac: brcmf_sdio_htclk: max_res_mask =
>>>>>> 0fceff77
It toook me a while to look into this. Unfortunately I do not have a
4339 to replicate your issue. The closest I have is a 4335. What looks
wrong here is the max_res_mask because the HT Avail resource is bit 29
which needs to be set in max_res_mask in order to make the request work.
On my 4335 the max_res_mask is 0x7fffffff before calling
brcmf_sdio_htclk(). So that is the cause of the failure in
brcmf_sdio_htclk(). However, now the question is why it is not properly set.
Between your device and mine there is once discrepancy in the pmucontrol
register, ie. bit 9 is set for your device. According the documentation
the power-on reset value for this bit is 0 and I don't seen any code in
our proprietary driver touching it.
> Sorry for the delayed answer, I had some trouble to copy the symlinks
> files corretly from /sys/class/devcoredump.
>
> I uploaded this folder to: https://drive.google.com/open?id=1fosahjLN1K
> I5NKS59_aPZdHLpENPFHtK
That worked nicely. So the firmware seems to crash very early. I have
rebuilt the firmware to provide me more info. Can you redo the
devcoredump trick with that firmware.
Regards,
Arend
[-- Attachment #2: 4339a0-sdio-ag-pool-autoabn-lpc.bin --]
[-- Type: application/octet-stream, Size: 493802 bytes --]
next prev parent reply other threads:[~2017-11-30 12:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 19:33 AP6335 with mainline kernel Vanessa Ayumi Maegima
2017-09-21 7:26 ` Arend van Spriel
2017-09-21 15:30 ` Vanessa Ayumi Maegima
2017-10-17 12:07 ` Vanessa Maegima
2017-11-10 12:43 ` Vanessa Maegima
2017-11-10 19:58 ` Arend van Spriel
2017-11-17 11:08 ` Vanessa Maegima
2017-11-17 12:55 ` Arend van Spriel
2017-11-17 15:24 ` Vanessa Maegima
2017-11-20 11:03 ` Arend van Spriel
2017-11-20 11:12 ` Arend van Spriel
2017-11-22 10:48 ` Vanessa Maegima
2017-11-22 10:58 ` Arend van Spriel
2017-11-23 15:24 ` Vanessa Maegima
2017-11-30 12:31 ` Arend van Spriel [this message]
2017-12-04 19:00 ` Vanessa Maegima
2017-12-05 9:06 ` Arend Van Spriel
2017-12-05 14:58 ` Vanessa Maegima
2018-01-15 20:08 ` Fabio Estevam
2018-01-16 20:21 ` Arend van Spriel
2018-01-18 11:47 ` Vanessa Maegima
2018-01-19 9:02 ` Arend van Spriel
2018-03-21 15:38 ` Vanessa Maegima
2018-03-23 9:28 ` Arend van Spriel
2018-03-23 13:15 ` Vanessa Maegima
2018-03-26 12:25 ` Vanessa Maegima
2018-03-26 13:34 ` Vanessa Maegima
2018-11-14 11:40 ` Arend van Spriel
2018-11-15 17:04 ` Vanessa Ayumi Maegima
[not found] ` <CAHWfWzm8Zwjc2tBQWVqpaa-cMYyEPWmUKYN7rspyb9W9spx2iQ@mail.gmail.com>
2018-11-17 19:10 ` Fabio Estevam
2018-11-28 15:59 ` Fabio Estevam
[not found] ` <CAF7Mx6p1DpRieCKy_1qOE5YT4_76UO8vhLMBFUD2B0FrQ9BJGw@mail.gmail.com>
2018-11-28 16:23 ` Fabio Estevam
2018-11-28 18:08 ` Fabio Estevam
2018-11-28 20:13 ` Arend van Spriel
2018-11-29 0:12 ` Fabio Estevam
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=5A1FFA17.6000703@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=embed3d@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=van.ayumi@gmail.com \
--cc=vanessa.maegima@nxp.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).