summaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/st
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javierm@redhat.com>2024-02-28 11:10:32 +0100
committerKalle Valo <kvalo@kernel.org>2024-03-05 20:53:46 +0200
commitf6e36d9e1c6353b74f1511ea18aa7c6fddd6e697 (patch)
tree84a15ef5c86c720e8d1206f36e5f8db097bdc28c /drivers/net/wireless/st
parent7979061313c81729b90accc8772635cfed9ba26d (diff)
downloadlinux-stable-f6e36d9e1c6353b74f1511ea18aa7c6fddd6e697.tar.gz
linux-stable-f6e36d9e1c6353b74f1511ea18aa7c6fddd6e697.tar.bz2
linux-stable-f6e36d9e1c6353b74f1511ea18aa7c6fddd6e697.zip
wifi: wlcore: sdio: Rate limit wl12xx_sdio_raw_{read,write}() failures warns
When these failures happen, the warning and call trace is printed which is excessive. Instead, just print the error but rate limited to prevent warns to unnecessarily pollute the kernel log buffer and make the serial console practically unusable. For example, on an AM625 BeaglePlay board where accessing a SDIO WiFi chip fails with an -110 (ETIMEDOUT) error: $ dmesg | grep "sdio write\|read failed (-110)" | wc -l 39 Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> Reviewed-by: Breno Leitao <leitao@debian.org> Signed-off-by: Kalle Valo <kvalo@kernel.org> Link: https://msgid.link/20240228101042.728881-1-javierm@redhat.com
Diffstat (limited to 'drivers/net/wireless/st')
0 files changed, 0 insertions, 0 deletions