Hi James/Anthony,

If an unsupported command is downloaded to FW, it results into command
response not supported - code 0x2.
It wouldnt result into command timeout.
According to our internal discussions, this issue is seen only on
Globalscale mirabox where SDIO controller is mvsdio.

"On Mirabox the SDIO controller is mvsdio. It polls for interrupts but
polling itself doesn’t seem to be the problem.
In the log, I got from another person it seems that there is no
SDIO_INT bit in controller “intr” register after scan command is sent.
Other commands are fine, only scan commands fail. I don’t why scan
(0x06 or 0x107) is special in this case."

Hi Anthony,

Could you please enable dynamic debug on mwifiex, mwifiex_sdio &
mvsdio driver; this will confirm if this is same issue.

Thanks,
Avinash.



On Thu, May 15, 2014 at 3:21 AM, James Cameron <quozl@laptop.org> wrote:
> On Wed, May 14, 2014 at 11:43:16AM +0200, WebAV wrote:
>> The FW is mwifiex 1.0 (14.66.9.p96) which I think is the last one.
>> [...]
>> mwifiex_sdio mmc0:0001:1: cmd: DNLD_CMD: (1397151023.654452): 0x107,
>> [...]
>> mwifiex_sdio mmc0:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id (1397151033.670677) = 0x107, act = 0x0
>
> My guess is that the driver has sent an extended scan command to
> firmware which does not support it, the result is a timeout.  If I'm
> right, what we're missing is a patch that uses the new fw_api_ver
> before scan.
>
> The inability to recover afterwards is a different problem.
>
> --
> James Cameron
> http://quozl.linux.org.au/