From: Ping-Ke Shih <pkshih@realtek.com>
To: Damian Bronecki <bronecki.damian@gmail.com>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"Stable@vger.kernel.org" <Stable@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: fix 8852AE disconnection caused by RX full flags
Date: Tue, 8 Aug 2023 00:59:46 +0000 [thread overview]
Message-ID: <34fd2fef462c4f79812d8cbe02446bd5@realtek.com> (raw)
In-Reply-To: <CAEvXze=dbg9iR2Ym2YVKcph+6QG1rx+fcQeJSdqgPN6Jrqy=8g@mail.gmail.com>
> -----Original Message-----
> From: Damian Bronecki <bronecki.damian@gmail.com>
> Sent: Monday, August 7, 2023 2:46 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: kvalo@kernel.org; Stable@vger.kernel.org; linux-wireless@vger.kernel.org
> Subject: Re: [PATCH] wifi: rtw89: fix 8852AE disconnection caused by RX full flags
>
> > RX full flags are raised if certain types of RX FIFO are full, and then
> > drop all following MSDU of APMDU. In order to resume to receive MSDU
> > when RX FIFO becomes available, we clear the regitster bits by the
> > commit a0d99ebb3ecd ("wifi: rtw89: initialize DMA of CMAC"). But, 8852AE
> > needs more settings to support this. To quickly fix disconnection problem,
> > revert the behavior as before.
> >
> > Fixes: a0d99ebb3ecd ("wifi: rtw89: initialize DMA of CMAC")
> > Reported-by: Damian B <bronecki.damian@gmail.com>
> > Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217710
> > Cc: <Stable@vger.kernel.org>
> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
>
> This patch fixed connection drops for me. Thanks!
>
> Tested-by: Damian B <bronecki.damian@gmail.com>
>
Thanks for your test.
Due to typo of commit message, I sent v2 with the Tested-by.
Ping-Ke
prev parent reply other threads:[~2023-08-08 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 10:50 [PATCH] wifi: rtw89: fix 8852AE disconnection caused by RX full flags Ping-Ke Shih
2023-08-07 6:45 ` Damian Bronecki
2023-08-08 0:59 ` Ping-Ke Shih [this message]
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=34fd2fef462c4f79812d8cbe02446bd5@realtek.com \
--to=pkshih@realtek.com \
--cc=Stable@vger.kernel.org \
--cc=bronecki.damian@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox