From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>,
"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>
Subject: RE: [PATCH v7 4/6] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS
Date: Tue, 25 Aug 2026 07:50:05 +0000 [thread overview]
Message-ID: <68a844f5ea2b4eea827da95080a9dbcb@realtek.com> (raw)
In-Reply-To: <E2ACBF1F-1C98-4091-A851-E2D8AF006911@linux.dev>
Luka Gejak <luka.gejak@linux.dev> wrote:
> On August 25, 2026 9:25:13 AM GMT+02:00, Ping-Ke Shih <pkshih@realtek.com> wrote:
> >Luka Gejak <luka.gejak@linux.dev> wrote:
> >> Hi Ping-Ke,
> >>
> >> On August 25, 2026 8:12:58 AM GMT+02:00, Ping-Ke Shih <pkshih@realtek.com> wrote:
> >> > guard(mutex)(&rtwsdio->tx_credit_lock);
> >>
> >> The lock is only taken for this chip, and guard() is unconditional, so I
> >> split the locked region into its own function instead of branching around
> >> the lock:
> >>
> >> if (!rtw_is_8723bs(rtwdev)) {
> >> txsize = sdio_align_size(rtwsdio->sdio_func, skb->len);
> >>
> >> ret = rtw_sdio_check_free_txpg(rtwdev, queue, txsize);
> >> if (ret)
> >> return ret;
> >>
> >> return rtw_sdio_write_to_port(rtwdev, skb, queue, txaddr,
> >> txsize);
> >> }
> >> ...
> >> guard(mutex)(&rtwsdio->tx_credit_lock);
> >>
> >> return rtw_sdio_8723bs_write_port(rtwdev, skb, queue, txaddr, txsize,
> >> write_size);
> >
> >I meant
> >
> > if (rtw_is_8723bs(rtwdev))
> > guard(mutex)(&rtwsdio->tx_credit_lock);
> >
> >Doesn't it work?
> >
> >
>
> I tried it, and no. guard() expands to a declaration, and a declaration
> cannot be the body of an if, so it does not build:
>
> sdio.c: In function 'rtw_sdio_write_port':
> include/linux/cleanup.h:302:9: error: expected expression before
> 'class_mutex_t'
> 302 | class_##_name##_t var __cleanup(...) =
>
> Adding braces builds cleanly, which is the more dangerous version, because
> the cleanup then runs at the closing brace and the mutex is released again
> before any of the code it is meant to protect runs.
>
> That is why I moved the locked part into its own function: the guard needs
> a scope that is exactly the critical section, and an if body is either too
> small or not allowed.
Okay. Got it.
next prev parent reply other threads:[~2026-08-25 7:50 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 [this message]
2026-08-25 8:07 ` Luka Gejak
2026-08-25 8:22 ` Ping-Ke Shih
2026-08-25 8:32 ` Luka Gejak
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=68a844f5ea2b4eea827da95080a9dbcb@realtek.com \
--to=pkshih@realtek.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=pbrobinson@gmail.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