The Linux Kernel Mailing List
 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 v7 4/6] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS
Date: Tue, 25 Aug 2026 10:32:06 +0200	[thread overview]
Message-ID: <2776B724-A5C6-4068-BFB5-3F0EC981F650@linux.dev> (raw)
In-Reply-To: <5c6d6a1826334966a4f0893ad306fba4@realtek.com>

On August 25, 2026 10:22:53 AM GMT+02:00, Ping-Ke Shih <pkshih@realtek.com> wrote:

> But I don't find rtw_sdio_write_to_port()?

My fault, it does not exist in v7. It is a function I added in v8 while
splitting the locked region out for guard(), and I asked you about it
without saying that. Sorry for the confusion. In v8 the transfer moved
into rtw_sdio_write_to_port(), called from both the generic path and the
8723BS one, and the warning had to go either inside it once or in both
callers. That was the whole of my question.

> Is this a normal case? Can current sdio.c handle this properly?
> If so, I'd change to debug level.

It should never happen. rtw_sdio_tx_skb_prepare() aligns the pointer
itself: it pushes the packet descriptor, and if the result is not aligned
to RTW_SDIO_DATA_PTR_ALIGN it pushes the difference as padding and tells
the firmware about the shifted offset. main.c reserves those 8 bytes in
hw->extra_tx_headroom for SDIO so the push always has room. So by the time
rtw_sdio_write_port() runs the pointer is aligned by construction, and the
check is really an assertion that the alignment step did its job.

It has never fired here, across all the testing on this chip.

So I would keep it at warn rather than debug. If it ever does fire it means
the alignment path above is broken, and the transfer would go out with a
misaligned pointer, which is worth being loud about. But it is your code
and your call.

Best regards,
Luka Gejak

  reply	other threads:[~2026-08-25  8:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  9:04 [PATCH v7 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-08-20  9:04 ` [PATCH v7 1/6] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-08-20  9:04 ` [PATCH v7 2/6] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-08-20  9:04 ` [PATCH v7 3/6] wifi: rtw88: tx: extend the TX report purge timeout to RTL8723BS luka.gejak
2026-08-20  9:04 ` [PATCH v7 4/6] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-08-25  6:12   ` Ping-Ke Shih
2026-08-25  7:20     ` Luka Gejak
2026-08-25  7:25       ` Ping-Ke Shih
2026-08-25  7:33         ` Luka Gejak
2026-08-25  7:50           ` Ping-Ke Shih
2026-08-25  8:07             ` Luka Gejak
2026-08-25  8:22               ` Ping-Ke Shih
2026-08-25  8:32                 ` Luka Gejak [this message]
2026-08-25  8:38                   ` Ping-Ke Shih
2026-08-25  8:42                     ` Luka Gejak
2026-08-25  8:49                       ` Ping-Ke Shih
2026-08-20  9:04 ` [PATCH v7 5/6] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-08-20  9:04 ` [PATCH v7 6/6] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
2026-08-25  6:36   ` Ping-Ke Shih
2026-08-25  7:22     ` Luka Gejak
2026-08-25  8:27       ` Ping-Ke Shih
2026-08-22 16:51 ` [PATCH v7 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS Luka Gejak
2026-08-23  6:00   ` Luka Gejak
2026-08-25  7:08     ` Ping-Ke Shih
2026-08-25  7:27       ` 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=2776B724-A5C6-4068-BFB5-3F0EC981F650@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