From: Ping-Ke Shih <pkshih@realtek.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony0620emma@gmail.com" <tony0620emma@gmail.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Rudi Heitbaum <rudi@heitbaum.com>
Subject: RE: [PATCH wireless v1] wifi: rtw88: sdio: Always use two consecutive bytes for word operations
Date: Mon, 15 May 2023 00:36:27 +0000 [thread overview]
Message-ID: <a0bf69fdb10b42a989a9b14e490e2f07@realtek.com> (raw)
In-Reply-To: <20230514200345.502807-1-martin.blumenstingl@googlemail.com>
> -----Original Message-----
> From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Sent: Monday, May 15, 2023 4:04 AM
> To: linux-wireless@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Ping-Ke Shih <pkshih@realtek.com>; tony0620emma@gmail.com;
> kvalo@kernel.org; Martin Blumenstingl <martin.blumenstingl@googlemail.com>; Larry Finger
> <Larry.Finger@lwfinger.net>; Rudi Heitbaum <rudi@heitbaum.com>
> Subject: [PATCH wireless v1] wifi: rtw88: sdio: Always use two consecutive bytes for word operations
>
> The Allwinner sunxi-mmc controller cannot handle word (16 bit)
> transfers. So and sdio_{read,write}w fails with messages like the
> following example using an RTL8822BS (but the same problems were also
> observed with RTL8822CS and RTL8723DS chips):
> rtw_8822bs mmc1:0001:1: Firmware version 27.2.0, H2C version 13
> sunxi-mmc 4021000.mmc: unaligned scatterlist: os f80 length 2
> sunxi-mmc 4021000.mmc: map DMA failed
> rtw_8822bs mmc1:0001:1: sdio read16 failed (0x10230): -22
>
> Use two consecutive single byte accesses for word operations instead. It
> turns out that upon closer inspection this is also what the vendor
> driver does, even though it does have support for sdio_{read,write}w. So
> we can conclude that the rtw88 chips do support word access but only on
> SDIO controllers that also support it. Since there's no way to detect if
> the controller supports word access or not the rtw88 sdio driver
> switches to the easiest approach: avoiding word access.
>
> Reported-by: Larry Finger <Larry.Finger@lwfinger.net>
> Closes: https://lore.kernel.org/linux-wireless/527585e5-9cdd-66ed-c3af-6da162f4b720@lwfinger.net/
"Closes:" seems not a regular tag. Use "Link: " instead.
> Reported-by: Rudi Heitbaum <rudi@heitbaum.com>
Followed by a "Link: " if you have another one.
> Fixes: 65371a3f14e7 ("wifi: rtw88: sdio: Add HCI implementation for SDIO based chipsets")
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> drivers/net/wireless/realtek/rtw88/sdio.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtw88/sdio.c b/drivers/net/wireless/realtek/rtw88/sdio.c
> index af0459a79899..06fce7c3adda 100644
> --- a/drivers/net/wireless/realtek/rtw88/sdio.c
> +++ b/drivers/net/wireless/realtek/rtw88/sdio.c
> @@ -87,11 +87,6 @@ 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)) {
> - sdio_writew(rtwsdio->sdio_func, val, addr, err_ret);
> - return;
> - }
> -
> *(__le16 *)buf = cpu_to_le16(val);
>
> for (i = 0; i < 2; i++) {
> @@ -125,9 +120,6 @@ static u16 rtw_sdio_readw(struct rtw_dev *rtwdev, u32 addr, int *err_ret)
> u8 buf[2];
> int i;
>
> - if (rtw_sdio_use_memcpy_io(rtwdev, addr, 2))
> - return sdio_readw(rtwsdio->sdio_func, addr, err_ret);
> -
> for (i = 0; i < 2; i++) {
> buf[i] = sdio_readb(rtwsdio->sdio_func, addr + i, err_ret);
> if (*err_ret)
> --
> 2.40.1
next prev parent reply other threads:[~2023-05-15 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 20:03 [PATCH wireless v1] wifi: rtw88: sdio: Always use two consecutive bytes for word operations Martin Blumenstingl
2023-05-15 0:36 ` Ping-Ke Shih [this message]
2023-05-15 10:59 ` Kalle Valo
2023-05-15 11:40 ` Ping-Ke Shih
2023-05-15 12:18 ` Julian Calaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0bf69fdb10b42a989a9b14e490e2f07@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=rudi@heitbaum.com \
--cc=tony0620emma@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.