[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200920132621.26468-1-afaerber@suse.de>
Date: Sun, 20 Sep 2020 15:26:19 +0200
From: Andreas Färber <afaerber@...e.de>
To: Yan-Hsuan Chuang <yhchuang@...ltek.com>,
Kalle Valo <kvalo@...eaurora.org>,
linux-wireless@...r.kernel.org
Cc: Chin-Yen Lee <timlee@...ltek.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-realtek-soc@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Andreas Färber <afaerber@...e.de>
Subject: [PATCH 0/2] net: wireless: rtw88: Fix oops on probe errors
Hello,
This mini-series fixes oopses in rtw88 device probe error handling,
resulting from asynchronous firmware loading.
Since there does not appear to be a public kernel API for canceling
scheduled or ongoing firmware loads, it seems we need to wait with
teardown until rtw88's callback was invoked and signals completion.
Found on RTD1296 arm64 SoC with experimental PCI host bridge driver
(https://github.com/afaerber/linux/commits/rtd1295-next) with a 4K
physical bar window, resulting in rtw_pci_setup_resource() failing,
or with non-implemented 4K remapping resulting in rtw_pci_read32()
returning 0xffffffff values and causing rtw_mac_power_on() to fail.
Cheers,
Andreas
Andreas Färber (2):
rtw88: Fix probe error handling race with firmware loading
rtw88: Fix potential probe error handling race with wow firmware
loading
drivers/net/wireless/realtek/rtw88/main.c | 5 +++++
1 file changed, 5 insertions(+)
--
2.28.0
Powered by blists - more mailing lists