Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Ping-Ke Shih <pkshih@realtek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Michael Straube <straube.linux@gmail.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Hans de Goede <johannes.goede@oss.qualcomm.com>,
	luka.gejak@linux.dev
Subject: RE: [PATCH v8 6/6] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation
Date: Fri, 28 Aug 2026 11:47:21 +0200	[thread overview]
Message-ID: <FCC54106-9CBC-4987-899B-4C7E0C997063@linux.dev> (raw)
In-Reply-To: <abbadda4537640eab1bce5620ade5f47@realtek.com>

Hi Ping-Ke,

On August 28, 2026 11:29:29 AM GMT+02:00, Ping-Ke Shih <pkshih@realtek.com> wrote:

> At the last review (I think v9), I will focus on the changes of this
> patchset doesn't affect existing chips.

That is the right thing to focus on and it is the part I cannot test, so
let me set out what the other parts actually run, and correct something
in the v8 cover letter while I am at it.

New code that is not behind rtw_is_8723bs(), all of it structural:

  sdio.h                   struct delayed_work work
  rtw_sdio_init_tx()       INIT_DELAYED_WORK(), mutex_init(), and
                           mutex_destroy() on its error path
  rtw_sdio_tx_kick_off()   mod_delayed_work(..., 0) in place of
                           queue_work()
  rtw_sdio_deinit_tx()     cancel_delayed_work_sync(), mutex_destroy()

Only this chip ever arms a delay, so on the other parts the work is
still queued immediately, and only this chip ever takes the mutex.

Two existing functions were also restructured and every chip runs
through them, so I should not describe the above as the whole story.
rtw_sdio_process_tx_queue() now returns a value instead of void, and
rtw_sdio_tx_handler() uses it. The behaviour is meant to be identical
for the other parts: on an empty queue the new "if (ret > 0) break"
takes the place of the old skb_queue_empty() break, and on a failed
write the frame is still requeued and the loop still retries, since
rtw_sdio_8723bs_reschedule_tx() returns false for anything that is not
this chip. That is the piece I would most like you to check.

Two things I verified against the base commit that I will spell out in
the v9 cover letter rather than leave implied:
rtw_sdio_check_free_txpg() differs by exactly one inserted branch ahead
of the existing 8051 test, which becomes an else if, everything else
unchanged; and the generic path through rtw_sdio_write_port() is step
for step what it was, same address from skb->len, same
sdio_align_size(), same check, same transfer, same failure message.

The correction: the v8 cover letter says patch 2 is "gated on the SDIO
interface rather than the chip id". That was true of an earlier version
and I did not update it. The code you have uses rtw_is_8723bs(), so it
is gated on the chip id as well, and the sentence understates how narrow
the check is. I will fix that section in v9.

One thing that would settle this better than any argument from me. rtw88
already supports five other SDIO parts that share sdio.c: RTL8723CS,
RTL8723DS, RTL8821CS, RTL8822BS and RTL8822CS. If anyone on the list has
any of them, a boot and some traffic with this series applied would
answer the question directly. I do not have that hardware. If nobody
does, I will say so in the cover letter rather than let it look tested.

Best regards,
Luka Gejak

  reply	other threads:[~2026-08-28  9:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 16:33 [PATCH v8 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-08-25 16:33 ` [PATCH v8 1/6] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-08-25 16:33 ` [PATCH v8 2/6] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-08-25 16:33 ` [PATCH v8 3/6] wifi: rtw88: tx: extend the TX report purge timeout to RTL8723BS luka.gejak
2026-08-25 16:33 ` [PATCH v8 4/6] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-08-28  9:23   ` Ping-Ke Shih
2026-08-28  9:40     ` Luka Gejak
2026-08-25 16:33 ` [PATCH v8 5/6] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-08-25 16:33 ` [PATCH v8 6/6] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
2026-08-28  9:29   ` Ping-Ke Shih
2026-08-28  9:47     ` Luka Gejak [this message]
2026-08-26 17:53 ` [PATCH v8 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS Luka Gejak

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=FCC54106-9CBC-4987-899B-4C7E0C997063@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pbrobinson@gmail.com \
    --cc=pkshih@realtek.com \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=straube.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox