The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Leonard Lausen <leonard@lausen.nl>, Ping-Ke Shih <pkshih@realtek.com>
Cc: leonard@lausen.nl, "David Härdeman" <david@hardeman.nu>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	linux-wireless@vger.kernel.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH rtw-next v3 2/2] wifi: rtw88: sdio: combine free TX page register reads
Date: Tue, 17 Nov 2026 06:43:47 +0100	[thread overview]
Message-ID: <4DA7AB91-A420-4C91-B57F-B39FD5DF6696@linux.dev> (raw)
In-Reply-To: <20261116205739.462458-6-leonard@lausen.nl>

On November 16, 2026 9:57:40 PM GMT+01:00, Leonard Lausen
<leonard@lausen.nl> wrote:
>TX capacity checks on non-8051 chips read three adjacent 32-bit registers
>in separate SDIO requests. Combine them into one 12-byte CMD53 read when
>the existing power/alignment check permits it, with the per-register
>fallback otherwise. Propagate read errors before checking queue capacity.
>
>Allocate a DMA-safe buffer at probe and copy its little-endian values
>into the caller's array before releasing the host. Holding the host
>through the read and copy serializes access to the shared buffer.
>
>Signed-off-by: Leonard Lausen <leonard@lausen.nl>
>---

Reviewed-by: Luka Gejak <luka.gejak@linux.dev>

Best regards,
Luka Gejak

  reply	other threads:[~2026-11-17  5:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 20:57 [PATCH rtw-next v3 0/2] wifi: rtw88: reduce RTL8822CS SDIO request overhead Leonard Lausen
2026-11-16 20:57 ` [PATCH rtw-next v3 1/2] wifi: rtw88: 8822c: filter hardware-handled control frames on SDIO Leonard Lausen
2026-11-17  5:43   ` Luka Gejak
2026-11-16 20:57 ` [PATCH rtw-next v3 2/2] wifi: rtw88: sdio: combine free TX page register reads Leonard Lausen
2026-11-17  5:43   ` Luka Gejak [this message]
2026-11-16 21:46 ` [PATCH rtw-next v3 0/2] wifi: rtw88: reduce RTL8822CS SDIO request overhead Luka Gejak
2026-11-17  0:54   ` Ping-Ke Shih

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=4DA7AB91-A420-4C91-B57F-B39FD5DF6696@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=david@hardeman.nu \
    --cc=heiko@sntech.de \
    --cc=leonard@lausen.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=shawn.lin@rock-chips.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