Re: Support for QCA9377

[Kalle Valo <kvalo@codeaurora.org>]

Jay Foster <jayf0ster@roadrunner.com> writes:

>>> I did manage to get a successful Wi-Fi STA mode connection with this
>>> driver.  One issue that I don't understand is when the driver attempts
>>> to load a FW file that is not present, it fails with error -2 and then
>>> reports, "Falling back to user helper".  However, this 'user helper'
>>> does not exist/work either, but the driver waits quite a while waiting
>>> for it (about half a minute or so).  This causes a delay loading the
>>> driver (about half a minute for each missing file).  So, even though
>>> the cal files are optional, if they are not there, it significantly
>>> delays loading of the driver.  I need to eliminate this delay.  For
>>> now, I patched the driver to not attempt to load the
>>> pre-cal-usb-<bus>.bin or the cal-usb-<bus>.bin files (that do not
>>> exist for my adapter), but there must be a better way to avoid this
>>> delay.
>> Yeah, that delay is a common problem and not ath10k related. IIRC
>> there's a Kconfig option which you can disable to avoid the delay, maybe
>> it was CONFIG_FW_LOADER_USER_HELPER_FALLBACK? Not sure though, Google
>> should be able to help with that.
>>
> Thanks.  Selecting CONFIG_FW_LOADER_USER_HELPER_FALLBACK=n did the trick.

Good that you got it working.

> Other issues that I have observed (probably FW related):
> 1) In STA mode, I observe several messages from the driver "received
> tx completion for invalid msdu_id: 0".  A Google search led me to
> https://github.com/erstrom/linux-ath/issues/1, but I did not find a
> resolution.

Yeah, I think have seen the same while I was testing USB patches.

> 2) If I reboot, it appears that the USB Wi-Fi adapter is left in a
> broken state, so the device fails to enumerate and the driver won't
> load.  A power cycle is required.

That's not good. We should find a way to reset the USB device, does
anyone know how?

> 3) AP mode does not work.  The driver reports:
> usb 1-1.2: Failed to submit usb control message: -110
> usb 1-1.2: unable to send the bmi data to the device: -110
> usb 1-1.2: unable to write to the device (-110)
> usb 1-1.2: settings HTC version failed
> usb 1-1.2: Could not init core: -22
> At this point, the device is stuffed again, and requires a power cycle.

Ok, so we need to disable AP mode support for USB devices from ath10k,
at least temporarily before we find a solution for it.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k