From: Michael Garofalo <officialtechflashyt@gmail.com>
To: adrian.hunter@intel.com
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
officialtechflashyt@gmail.com, ulf.hansson@linaro.org
Subject: Re: [PATCH 0/2] mmc: sdhci: add quirk to disable bounce buffer
Date: Tue, 7 Oct 2025 18:10:41 -0700 [thread overview]
Message-ID: <20251008011041.3298938-1-officialTechflashYT@gmail.com> (raw)
In-Reply-To: <6294fb07-31b4-4c0e-9023-7c5ab604bbf1@intel.com>
> On 06/10/2025 12:28, Michael Garofalo wrote:
>>> On 06/10/2025 10:35, Adrian Hunter wrote:
>>>> On 06/10/2025 04:36, Michael Garofalo wrote:
>>>>> This patch series adds a new bit to quirks2 for disabling the bounce
>>>>> buffer. On some hardware, this is required for proper operation. An
>>>>> example of such hardware is the SDHCI controller of the Nintendo Wii's
>>>>> "Hollywood" chipset. Without this patch, the onboard Broadcom 4318
>>>>> Wi-Fi fails to connect to any networks.
>>>>
>>>> The bounce buffer should not make any difference, so it is likely
>>>> a different problem that gets hidden when the bounce buffer is not
>>>> used.
>>>>
>>>>> Could you enable dynamic debug messages and show the messages
>>>>> for the failing case?
>>>>
>>>> Actually will also need to see the messages in the "fixed" case
>>>> to compare.
>> I'm afraid I won't be able to provide those easily, at least not with the
>> commands you've provided. Since the rootfs is _also_ running from SD,
>> turning on full MMC logs like this produces an obscene amount of noise
>> from the storage, unrelated to the SDIO wireless. It gets even worse with
>> my original intention, which was to save the logs to SD Card, (since my USB
>> Gecko serial console is rather flakey, and introduces corruption now and then),
>> since it's now logging the writes of it's own logs in a permanent loop.
>> If there's a way to narrow down the logs to specifically whatever portions
>> you're interested in, and filter out the noise, I would happily provide it.
>
> Are there any error messages?
If I drop the debug logs you mentioned so that I can actually see what's
going on (they produce hundreds of lines / sec), here's what the Wi-Fi card
actually reports with, vs without, MMC bounce buffers. With bounce buffers on,
it takes several tries to load the firmware, and it can't authenticate to any
network. I've tested and confirmed this effect on multiple consoles, across
multiple reboots, on multiple Wi-Fi networks. Meanwhile with MMC bounce buffers
off, it's much more functional.
Logs with MMC bounce buffers *on* (without my patches):
[ 168.492687] b43-sdio mmc1:0001:1: Chip ID 14e4:4318
[ 168.493516] ssb: Found chip with id 0x4710, rev 0x00 an package 0x00
[ 168.508519] ssb: WARNING: Multiple ChipCommon found
[ 168.510597] b43-sdio mmc1:0001:1: Sonics Silicon Backplane found on SDIO device mmc1:0001:1
[ 168.510886] b43-phy0: Broadcom 4710 WLAN found (core revision 9)
[ 168.530151] b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
[ 168.538447] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2050, Revision 8, Version 0
[ 168.719257] Broadcom 43xx driver loaded [ Features: S ]
[ 168.722231] b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2
[ 168.724613] b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2
[ 168.740666] b43 ssb0:0: Direct firmware load for b43-open/pcm5.fw failed with error -2
[ 168.762630] ieee80211 phy0: Slected rate control algorithm 'minstrel_ht'
[ 176.156693] b43-phy0: Loading OpenSource firmware version 410.31754
[ 176.157159] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 179.993008] b43-phy0: Loading OpenSource firmware version 410.31754
[ 179.994373] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 186.940346] b43-phy0: Loading OpenSource firmware version 410.31754
[ 186.942559] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 216.368668] b43-phy0: Loading OpenSource firmware version 410.31754
[ 216.369135] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 221.750016] b43-phy0: Loading OpenSource firmware version 410.31754
[ 221.757700] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 223.437731] wlan0: authenticate with da:b3:70:18:7c:14 (local address=00:1c:be:ab:73:27)
[ 223.437764] wlan0: send auth to da:b3:70:18:7c:14 (try 1/3)
[ 223.648472] wlan0: send auth to da:b3:70:18:7c:14 (try 2/3)
[ 223.859770] wlan0: send auth to da:b3:70:18:7c:14 (try 3/3)
[ 224.064469] wlan0: authentication with da:b3:70:18:7c:14 timed out
[ 226.045361] wlan0: authenticate with da:b3:70:18:7c:14 (local address=00:1c:be:ab:73:27)
[ 226.045393] wlan0: send auth to da:b3:70:18:7c:14 (try 1/3)
[ 226.248488] wlan0: send auth to da:b3:70:18:7c:14 (try 2/3)
[ 226.462378] wlan0: send auth to da:b3:70:18:7c:14 (try 3/3)
[ 226.664487] wlan0: authentication with da:b3:70:18:7c:14 timed out
[ 250.424168] b43-phy0: Loading OpenSource firmware version 410.31754
[ 250.425629] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 255.806790] b43-phy0: Loading OpenSource firmware version 410.31754
[ 255.807256] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 257.467380] wlan0: authenticate with da:b3:70:18:7c:14 (local address=00:1c:be:ab:73:27)
[ 257.467414] wlan0: send auth to da:b3:70:18:7c:14 (try 1/3)
[ 257.672475] wlan0: send auth to da:b3:70:18:7c:14 (try 2/3)
[ 257.880474] wlan0: send auth to da:b3:70:18:7c:14 (try 3/3)
[ 258.093974] wlan0: authentication with da:b3:70:18:7c:14 timed out
[ 284.326415] b43-phy0: Loading OpenSource firmware version 410.31754
[ 284.326922] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 289.836233] b43-phy0: Loading OpenSource firmware version 410.31754
[ 289.837612] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 291.528250] wlan0: authenticate with da:b3:70:18:7c:14 (local address=00:1c:be:ab:73:27)
[ 291.528283] wlan0: send auth to da:b3:70:18:7c:14 (try 1/3)
[ 291.736473] wlan0: send auth to da:b3:70:18:7c:14 (try 2/3)
[ 291.944482] wlan0: send auth to da:b3:70:18:7c:14 (try 3/3)
[ 292.152470] wlan0: authentication with da:b3:70:18:7c:14 timed out
<keeps trying and failing forever....>
Logs with MMC bounce buffers *off* (with my patches):
[ 383.974268] b43-sdio mmc1:0001:1: Chip ID 14e4:4318
[ 383.975824] ssb: Found chip with id 0x4710, rev 0x00 and package 0x00
[ 383.986645] ssb: WARNING: Multiple ChipCommon found
[ 383.987414] b43-sdio mmc1:0001:1: Sonics Silicon Backplane found on SDIO device mmc1:0001:1
[ 383.987744] b43-phy0: Broadcom 4710 WLAN found (core revision 9)
[ 383.995898] b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
[ 383.996249] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2050, Revision 8, Version 0
[ 384.077562] b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2
[ 384.077687] b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2
[ 384.086571] Broadcom 43xx driver loaded [ Features: S ]
[ 384.144620] b43 ssb0:0: Direct firmware load for b43-open/pcm5.fw failed with error -2
[ 384.190831] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 395.097838] b43-phy0: Loading OpenSource firmware version 410.31754
[ 395.098158] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 397.667851] b43-phy0: Loading OpenSource firmware version 410.31754
[ 397.668171] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 403.940787] b43-phy0: Loading OpenSource firmware version 410.31754
[ 403.941110] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 405.366065] wlan0: authenticate with da:b3:70:18:7c:14 (local address=00:1c:be:ab:73:27)
[ 405.366095] wlan0: send auth to da:b3:70:18:7c:14 (try 1/3)
[ 405.389013] wlan0: authenticated
[ 405.392814] wlan0: associate with da:b3:70:18:7c:14 (try 1/3)
[ 405.600498] wlan0: associate with da:b3:70:18:7c:14 (try 2/3)
[ 405.808479] wlan0: associate with da:b3:70:18:7c:14 (try 3/3)
[ 406.016481] wlan0: association with da:b3:70:18:7c:14 timed out
[ 414.301216] wlan0: authenticate with da:b3:70:18:7c:14 (local address=00:1c:be:ab:73:27)
[ 414.301245] wlan0: send auth to da:b3:70:18:7c:14 (try 1/3)
[ 414.351544] wlan0: authenticated
[ 414.403769] wlan0: associate with da:b3:70:18:7c:14 (try 1/3)
[ 414.422775] wlan0: RX AssocResp from da:b3:70:18:7c:14 (capab=0x1411 status=0 aid=25)
[ 414.431879] wlan0: associated
[ 415.272393] wlan0: Limiting TX power to 36 (36 - 0) dBm as advertised by da:b3:70:18:7c:14
If there's anything further that would be useful here, let me know and I'd be happy to provide them.
next prev parent reply other threads:[~2025-10-08 1:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 1:36 [PATCH 0/2] mmc: sdhci: add quirk to disable bounce buffer Michael Garofalo
2025-10-06 1:36 ` [PATCH 1/2] mmc: sdhci: add quirk to disable the " Michael Garofalo
2025-10-06 1:37 ` [PATCH 2/2] mmc: sdhci-of-hlwd: disable bounce buffer usage Michael Garofalo
2025-10-06 7:35 ` [PATCH 0/2] mmc: sdhci: add quirk to disable bounce buffer Adrian Hunter
2025-10-06 7:38 ` Adrian Hunter
2025-10-06 9:15 ` Michael Garofalo
2025-10-06 9:28 ` Michael Garofalo
2025-10-06 10:46 ` Adrian Hunter
2025-10-08 1:10 ` Michael Garofalo [this message]
2025-10-08 11:30 ` Adrian Hunter
2025-10-10 21:16 ` Michael Garofalo
2025-10-13 6:40 ` Adrian Hunter
2025-10-20 7:53 ` Michael Garofalo
2025-10-24 5:36 ` Adrian Hunter
2025-10-24 8:32 ` Linus Walleij
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=20251008011041.3298938-1-officialTechflashYT@gmail.com \
--to=officialtechflashyt@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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