From: Ping-Ke Shih <pkshih@realtek.com>
To: Ping-Ke Shih <pkshih@realtek.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: rtw89: pci: correct TX resource checking for PCI DMA channel of firmware command
Date: Thu, 18 Apr 2024 09:06:01 +0800 [thread overview]
Message-ID: <e40848a0-7b9c-4faf-9cd6-7c003c0fbf81@RTEXMBS04.realtek.com.tw> (raw)
In-Reply-To: <20240410011316.9906-1-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> The DMA channel of firmware command doesn't use TX WD (WiFi descriptor), so
> don't need to consider number of TX WD as factor of TX resource. Otherwise,
> during pause state (a transient state to switch to/from low power mode)
> firmware commands could be dropped and driver throws warnings suddenly:
>
> rtw89_8852ce 0000:04:00.0: no tx fwcmd resource
> rtw89_8852ce 0000:04:00.0: failed to send h2c
>
> The case we met is that driver sends RSSI strength of firmware command at
> RX path that could be running concurrently with switching low power mode.
> The missing of this firmware command doesn't affect user experiences,
> because the RSSI strength will be updated again after a while.
>
> The DMA descriptors of normal packets has three layers like:
>
1 patch(es) applied to rtw-next branch of rtw.git, thanks.
c6330b129786 wifi: rtw89: pci: correct TX resource checking for PCI DMA channel of firmware command
---
https://github.com/pkshih/rtw.git
prev parent reply other threads:[~2024-04-18 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 1:13 [PATCH] wifi: rtw89: pci: correct TX resource checking for PCI DMA channel of firmware command Ping-Ke Shih
2024-04-18 1:06 ` 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=e40848a0-7b9c-4faf-9cd6-7c003c0fbf81@RTEXMBS04.realtek.com.tw \
--to=pkshih@realtek.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).