Hi Daniel, > Hi, > > we're trying to get a SD8787 to play which is connected via SDIO to an > OMAP hsmmc (AM33xx hardware). This fails with the following message: > > # modprobe mwifiex_sdio > [ 13.984779] [sched_delayed] sched: RT throttling activated > [ 22.401700] mwifiex_sdio mmc0:0001:1: FW failed to be active in time > > The firmware sd8787_uapsta.bin was taken from the linux-firmware.git and > apparently is transferred successfully, but then consequently fails to > do start up. When compiled with CONFIG_MMC_CONFIG=y, tons of successful > messages are logged like this: > > [ 2607.867660] mmc0: starting CMD52 arg 00000a00 flags 00000195 > [ 2607.867713] mmc0: req done (CMD52): 0: 00001000 00000000 00000000 > 00000000 > [ 2607.883273] mmc0: starting CMD52 arg 00000a00 flags 00000195 > [ 2607.883327] mmc0: req done (CMD52): 0: 00001000 00000000 00000000 > 00000000 > [ 2607.898905] mmc0: starting CMD52 arg 00000a00 flags 00000195 It keeps reading Int_Pending (CCCR register 0x05). Perhaps you have interrupt storm here? Could you please check if your controller clears interrupt properly? > > > The kernel we're based on is Linus' current merge tree (3.7-rc1), but > earlier version (3.6) have shown the same issue. > > Before we start digging into this, I want to ask whether there are any > common pitfalls we should be aware of and that could cause this? You may want to get a newer firmware release from here: http://git.marvell.com/?p=mwifiex-firmware.git;a=summary git://git.marvell.com/mwifiex-firmware.git > > Please let me know whether you need any further information. It might be helpful if you post messages before this line: [ 2607.867660] mmc0: starting CMD52 arg 00000a00 flags 00000195 Thanks, Bing > > > Many thanks, > Daniel ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
