aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm27xx/patches-5.4/950-0363-dwc_otg-checking-the-urb-transfer_buffer-too-early-3.patch
diff options
context:
space:
mode:
authorPetr Štetiar <ynezz@true.cz>2020-04-29 17:13:29 +0200
committerPetr Štetiar <ynezz@true.cz>2020-04-30 00:52:04 +0200
commit8036e7ebb53fc8125e985ef4e238970aeaaaed18 (patch)
tree8218b9b91ea9c2b975a1083f00927712ca4c33aa /target/linux/bcm27xx/patches-5.4/950-0363-dwc_otg-checking-the-urb-transfer_buffer-too-early-3.patch
parentb17a5a9bdb9f6f5ff73ceee0265b3f5de943d1bb (diff)
downloadupstream-8036e7ebb53fc8125e985ef4e238970aeaaaed18.tar.gz
upstream-8036e7ebb53fc8125e985ef4e238970aeaaaed18.tar.bz2
upstream-8036e7ebb53fc8125e985ef4e238970aeaaaed18.zip
ath10k-ct: update to version 2020-04-29
Pulls in workaround for TX rate code firmware bug which might as well help track it down via different printk()s and thus possibly provide more clue for proper fix. Firmware currently sends wrong (0xff) TX rate code which causes WARN_ONCE, so the workaround just changes this bogus value (0xff) into 0. For 5.4 it also pulls in tx-queue-wake throttling patch "ath10k: Restart xmit queues below low-water mark", which should improve performance with high number of concurrent TCP streams. Ref: https://github.com/greearb/ath10k-ct/pull/129 Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'target/linux/bcm27xx/patches-5.4/950-0363-dwc_otg-checking-the-urb-transfer_buffer-too-early-3.patch')
0 files changed, 0 insertions, 0 deletions