Message ID | 1027342a-97dd-83cd-f363-43cff49967e2@lwfinger.net |
---|---|
State | New |
Headers | show |
Series | rtw88: Problem with sdio.c | expand |
Larry Finger <Larry.Finger@lwfinger.net> writes: > On 5/24/23 14:18, Jernej Škrabec wrote: >> >> This was fixed in: >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cb0ddaaa5db09d7d216fcbf0e68779be223a1128 > > That fix is in the kernel mainline source, but not in wireless-next, > where I got my source. I hope it gets resolved correctly. The fix should come to wireless-next after the next (no pun intended) net-next pull request. One way to avoid this problem of not having all the fixes is to use the wireless-testing tree: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git/ In that tree Bob Copeland periodically pulls both wireless and wireless-next to the latest -rc releases and that way you can easily get all the latest wireless code from one tree. For example I use wireless-testing as the baseline for all my ath1*k drivers testing. But do note that the tree is rebased so the history is not stable.
diff --git a/sdio.c b/sdio.c index 1647cdc..2051c30 100644 --- a/sdio.c +++ b/sdio.c @@ -87,7 +87,7 @@ static void rtw_sdio_writew(struct rtw_dev *rtwdev, u16 val, u32 addr, u8 buf[2]; int i; - if (rtw_sdio_use_memcpy_io(rtwdev, addr, 2)) { + if (rtw_sdio_use_memcpy_io(rtwdev, addr, 2) && !rtw_chip_wcpu_11n(rtwdev)) { sdio_writew(rtwsdio->sdio_func, val, addr, err_ret); return;