On 2019-09-26 14:54, Kalle Valo wrote:
+ Miaoqing
Federico Cuello <fedux@xxxxxxxxxxxx> writes:
On 2019-09-25 18:24, Brian Norris wrote:
On Wed, Sep 25, 2019 at 2:16 AM Federico Cuello <fedux@xxxxxxxxxxxx>
wrote:
When upgrading to 5.3 my AP started to work really slow. I tracked
the problem to 4504f0e5b5714d9d26b1a80bf1fc133c95830588 and fixed
the issue.
For the record, that's:
4504f0e5b571 ath10k: sdio: workaround firmware UART pin
configuration bug
The attached patch fixes the issue when uart_print is false and
uart_pin_workaround also false.
-ENOPATCH
Sorry, I sent it in a different email "attached to the thread", but in
any case, there was the same fix already applied to kvalo's tree.
Here is the patch and link to already applied fix:
https://patchwork.kernel.org/patch/11160267/
It would be great if we can get this to stable, in my case, my WiFi
speed went from 150 Mbit/s to 1-5 Mbit/s without this fix.
I didn't know that the bug was severe and I applied the patch to
ath-next, which means it will go to v5.5 which is bad. (This is why I
always ask people to clearly describe the bug in the commit log!)
In theory I could also push it to v5.4 but I just don't want to deal
with the possible conflicts coming from duplicate commits.
I don't know how this is affecting others. Miaoqing? How did this affect
you?
Also, would it be possible maybe to revert the patch and re-apply it
with stable CCed to avoid any possible conflicts and get it to stable? I
can still just patch my kernels if this is not big deal for others.
