Hi, On Mon, Jan 25, 2016 at 12:07 PM, Arend van Spriel <arend@xxxxxxxxxxxx> wrote: >> In any case, in my experience the Broadcom firmware is fairly >> complicated and has numerous cases where it stretches SDIO more than >> the other SDIO WiFi chip I've worked with. It wouldn't terribly >> surprise me if there was a period of time during bootup where it was >> non-responsive for 2 seconds. As unrelated "evidence" showing some of >> the Broadcom SDIO limitations, you can see >> <https://chromium-review.googlesource.com/#/c/250228/> and also the >> fact that Broadcom often holds the SDIO "busy" signal whereas the >> other SDIO WiFi chip I've worked never did that. Also, even with all >> fixes the Broadcom WiFi module will still show periodic SDIO errors >> that the higher level driver just knows to ignore. > > The busy signal is in accordance with the SDIO spec. Sorry, didn't mean to imply that it wasn't. That particular instance is definitely legal, but it was also just showing a case where the Broadcom WiFi needed something that wasn't needed elsewhere. AKA: it's kinda like saying that other modules work on a UART without flow control lines and the Broadcom needs the flow control lines. UARTs are designed with flow control lines and it's totally legal to need them. ...but if you saw that one serial device didn't need them then you would presume that maybe the device on the other end had very low interrupt latency or had some other hardware help (large FIFOs, DMA, fast processor, hard real time OS, etc). A device with low interrupt latency, large FIFOs, DMA, fast processor, etc would presumably be less likely to have other pauses in communication. > It would be good to > know if that is what is happening. Unfortunately I do have an SDIO > analyzer, but not reproduced it. May retry on veyron device. You might just be able to put a trace to see if it hits the busy signal. Depending on your Linux version you might just be able to put a trace in __mmc_start_request(). If not and if you're on dw_mmc you can put a trace in dw_mci_wait_while_busy(). >> My old debugging from the (sorry, private) bug >> http://crosbug.com/p/36975 showed this periodically even with all >> known fixes: >> >> [21310.271635] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000104 >> [21550.583598] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000104 >> [21550.616035] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -110 >> [21550.648460] brcmfmac: brcmf_sdio_rxfail: abort command, terminate >> frame, send NAK >> [21550.683502] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000104 >> [21550.691214] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000100 >> [22671.121329] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000104 >> [22671.153167] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x01000104 >> [22671.184581] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -110 >> [22671.192600] brcmfmac: brcmf_sdio_rxfail: abort command, terminate >> frame, send NAK >> [22671.201929] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000114 >> [22671.209536] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000100 >> [28463.941736] dwmmc_rockchip ff0d0000.dwmmc: CMD ERR: 0x00000104 >> >> At the time dekim@ responded: >> >>> There are several sleep/wake control at different level. The one we're talking >>> about here is controlled by brcmf_sdio_bus_sleep() in the host driver to turn >>> on/off bus core on the chip. There can be a period of time when chip is not >>> paying attention to the host command (cmd52 to the >>> SBSDIO_FUNC1_SLEEPCSR). >> >> ...and we decided that the periodic SDIO errors weren't causing any >> huge problems (since they were retried). As far as I know, they still >> happen today. > > Were these true periodic errors or random at interval. I believe they were random, and I believe that I needed "power save" mode turned on for WiFi. I believe errors were made worse if I had a TCP/IP ping running (AKA bring out of power save and go back in constantly). -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
