From: Neil Armstrong <neil.armstrong@linaro.org>
To: Franky Lin <franky.lin@broadcom.com>,
Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Arend van Spriel <aspriel@gmail.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Kalle Valo <kvalo@kernel.org>, Eric Dumazet <edumazet@google.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Alexander Prutskov <alep@cypress.com>,
Joseph chuang <jiac@cypress.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Angus Ainslie <angus@akkea.ca>,
linux-wireless@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [RFC PATCH] brcmfmac: add 43751 SDIO ids and initialization
Date: Wed, 8 Mar 2023 18:37:48 +0100 [thread overview]
Message-ID: <629435a5-fb47-2cb5-78b6-e42c943aa397@linaro.org> (raw)
In-Reply-To: <CA+8PC_dFTvv9VtY9jBWLLwSoQzGxQd57zWMsnN6amddop4Yw-g@mail.gmail.com>
On 08/03/2023 18:21, Franky Lin wrote:
> On Wed, Mar 8, 2023 at 4:48 AM Marc Gonzalez <marc.w.gonzalez@free.fr> wrote:
>>
>> On 08/03/2023 00:15, Franky Lin wrote:
>>
>>> On Tue, Mar 7, 2023 at 6:40 AM Marc Gonzalez wrote:
>>>
>>>> Through the SDIO bus, the WiFi chip reports 0xaae7 (i.e. 43751)
>>>> hence the /sys/bus/sdio/devices output above.
>>>>
>>>> sdio_read_func_cis() -> sdio_read_cis() which sets
>>>> func->vendor/func->device to 2d0/aae7
>>>>
>>>>
>>>> But when brcmf_chip_recognition() calls ci->ops->read32()
>>>> i.e. brcmf_sdio_buscore_read32()
>>>> [ vs brcmf_sdiod_readl() in brcmf_sdio_probe_attach() ]
>>>>
>>>> [ 1.177283] brcmfmac: F1 signature read @0x18000000=0x1042aae8
>>>> [ 1.182912] found AXI chip: BCM43752/2
>>>> [ 1.186384] BCM43752/2: chip=aae8 rev=2 type=1
>>>>
>>>> Here it reports 0xaae8 (i.e. 43752)
>>>>
>>>> Why the discrepancy?
>>>> Can it cause issues?
>>>> (Sometimes, the whole SDIO bus doesn't probe at boot.
>>>> I am still investigating these intermittent problems.)
>>>>
>>>> Should I use 43751 or 43752 firmware...?
>>>
>>> This question should be answered by the Cypress/Infineon folks but
>>> unfortunately they have been quiet for a long time. In general we use
>>> the id read from 0x18000000 to decide which firmware to load. But be
>>> aware that the rev also matters. There are some examples in
>>> brcmf_sdio_fwnames table that the different firmware name can be
>>> derived from the same chip common id but different rev.
>>>
>>> However sdio device enumeration happens before firmware download so
>>> the intermittent problem you are facing probably is not related to
>>> firmware version.
>>
>> Disclosure: My knowledge of SDIO device enumeration is 0.
>>
>> When the host sends the equivalent of an "identify yourself" message
>> on the SDIO bus, doesn't the reply come from the WiFi device?
>> Why would the device reply 0xaae7 instead of 0xaae8?
>>
>> In other words, who is replying 0xaae7?
>
> The enumeration response is done by the HW sdio core on the chip. No
> software involved.
Mark,
This would be the:
BRCMF_SDIO_DEVICE(SDIO_DEVICE_ID_BROADCOM_CYPRESS_43751, CYW),
which is returned by the SDIO bus and associated the SDIO device with the brcmf driver.
All the other IDs are returned by reading registers/send commands to the SDIO device.
Neil
>
> Regards,
> - Franky
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-03-08 17:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 18:19 Unsupported WiFi adapter on S905X2 board Marc Gonzalez
2023-03-06 9:17 ` Neil Armstrong
2023-03-06 10:24 ` [RFC PATCH] brcmfmac: add 43751 SDIO ids and initialization Marc Gonzalez
2023-03-06 10:41 ` Marc Gonzalez
2023-03-07 14:40 ` Marc Gonzalez
2023-03-07 23:15 ` Franky Lin
2023-03-08 12:47 ` Marc Gonzalez
2023-03-08 17:21 ` Franky Lin
2023-03-08 17:37 ` Neil Armstrong [this message]
2023-03-22 17:40 ` Marc Gonzalez
2023-04-04 15:59 ` Marc Gonzalez
2023-03-09 10:16 ` Marc Gonzalez
2023-03-09 12:13 ` Marc Gonzalez
2023-03-09 14:29 ` Ulf Hansson
2023-03-09 16:45 ` Marc Gonzalez
2023-03-09 17:51 ` Marc Gonzalez
2023-03-13 13:55 ` Marc Gonzalez
2023-03-13 14:41 ` Marc Gonzalez
2023-03-13 14:53 ` Marc Gonzalez
2023-03-13 17:09 ` Marc Gonzalez
2023-03-13 20:04 ` Martin Blumenstingl
2023-03-13 21:42 ` Marc Gonzalez
2023-03-14 7:27 ` Ulf Hansson
[not found] ` <c7e48c6f-530b-7198-b8bb-fc927a2fdc66@free.fr>
2023-03-14 11:08 ` Ulf Hansson
2023-03-14 16:37 ` Marc Gonzalez
2023-03-15 20:55 ` Ulf Hansson
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=629435a5-fb47-2cb5-78b6-e42c943aa397@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=alep@cypress.com \
--cc=angus@akkea.ca \
--cc=aspriel@gmail.com \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=jbrunet@baylibre.com \
--cc=jiac@cypress.com \
--cc=khilman@baylibre.com \
--cc=kvalo@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=martin.blumenstingl@googlemail.com \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=ulf.hansson@linaro.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