Linux wireless drivers development
 help / color / mirror / Atom feed
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: "straube.linux@gmail.com" <straube.linux@gmail.com>,
	"pbrobinson@gmail.com" <pbrobinson@gmail.com>
Subject: RE: [RFC PATCH v1 0/9] wifi: rtw88: add RTL8723B/RTL8723BS support
Date: Tue, 21 Jul 2026 08:57:26 +0000	[thread overview]
Message-ID: <cbaa891f94ce41c7a6a1d576db50b75c@realtek.com> (raw)
In-Reply-To: <3EA0A653-D15F-4DD4-8DA6-C9CFFFF38205@linux.dev>

Hi Luka,

Luka Gejak <luka.gejak@linux.dev> wrote:
> Hi Ping-Ke,
> 
> Thanks for the review, and for taking the time on a series this size.
> 
> Before I send v2 I want to report what changed, because the result of
> your comments is that the series gets noticeably smaller. I would
> rather tell you now than have you spend review time on patches I am
> about to delete.

I think you can send v2 as smaller patchset now if you have done it.

In short, I prefer first patchset is to add RTL8723BS with fewer special
cases as possible, and patches looks like
 - add hard required handling for RTL8723BS
 - add RTL8923B main body
 - add Kconfig & Makefile
 - add MAINTAINERS

If special cases are still needed, you can submit them after first
version gets merged. 

> 
> Answers to your questions from the cover letter first.
> 
> 1. The link. Michael Straube's original work is now referenced in the
>    chip patch:
> 
>      https://github.com/mistraube/rtw88/tree/rtl8723bs

Adding this to cover letter for reference will be good for reviewers. 

> 
>    The current state of my series is here, if it is easier to read than
>    mail:
> 
>      https://github.com/MocLG/rtw/tree/8723bs-upstream

I have not seen the detail, but good to have it.

> 
> 2. sparse and smatch. Both re-run on the new series, clean, no findings
>    in the 8723b/8723bs files.

Please keep running the checks afterward. As well as checkpatch.pl I forgot
to mention. 

> 
> 3. Bluetooth coexistence. Tested as you asked: WiFi download while an
>    A2DP sink plays music, shared antenna, 2.4 GHz HT40.
> 

[...]

> 
>    The reported BT coex version is 0x69, below the 0x6d the 1ant
>    parameters expect. Is the rtl8723bs BT firmware currently shipped in
>    linux-firmware older than the coex protocol these parameters were
>    written for, and should I be using a different blob? 

Sorry. I'm not sure. Perhaps, you can try rtlwifi/rtl8723befw.bin or
rtlwifi/rtl8723befw_36.bin (WiFi firmware) to see if it is better. 

(To prevent linux-firmware maintainer merge your submission right now, 
 you might need to drop your submission of rtw88/rtw8723b_fw.bin temporarily?)

> 
> Now the larger change.

Thanks for your follows.
 
> Two caveats I want to state plainly rather than have you find them.

As I mentioned at beginning, we can add special cases after first version
get merged. At that time, we can discuss each problem in detail by patch.

> I will hold v2 until you have had a chance to react to the removals, in
> case any of them should stay, and to pick up whatever else you find in
> the patches that remain.

I will stop reviewing v1 to avoid redundant works. You can send v2 now, but
please give me some time. 

Ping-Ke


  reply	other threads:[~2026-07-21  8:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 17:50 [RFC PATCH v1 0/9] wifi: rtw88: add RTL8723B/RTL8723BS support luka.gejak
2026-07-14 17:50 ` [RFC PATCH v1 1/9] wifi: rtw88: add RTL8723B chip support luka.gejak
2026-07-20  3:00   ` Ping-Ke Shih
2026-07-14 17:51 ` [RFC PATCH v1 2/9] wifi: rtw88: 8723bs: handle SDIO management and data TX luka.gejak
2026-07-20  6:30   ` Ping-Ke Shih
2026-07-14 17:51 ` [RFC PATCH v1 3/9] wifi: rtw88: 8723bs: add the firmware host-to-chip interface luka.gejak
2026-07-14 17:51 ` [RFC PATCH v1 4/9] wifi: rtw88: 8723bs: add WiFi/BT coexistence antenna handling luka.gejak
2026-07-14 17:51 ` [RFC PATCH v1 5/9] wifi: rtw88: 8723bs: keep the chip powered between scan and connect luka.gejak
2026-07-14 17:51 ` [RFC PATCH v1 6/9] wifi: rtw88: 8723bs: add scan, calibration and rate-adaptation handling luka.gejak
2026-07-14 17:51 ` [RFC PATCH v1 7/9] wifi: rtw88: 8723bs: implement the SDIO association sequence luka.gejak
2026-07-14 17:51 ` [RFC PATCH v1 8/9] wifi: rtw88: 8723bs: implement the SDIO transfer contract luka.gejak
2026-07-14 17:51 ` [RFC PATCH v1 9/9] MAINTAINERS: add entry for the RTL8723B rtw88 driver luka.gejak
2026-07-20  1:53 ` [RFC PATCH v1 0/9] wifi: rtw88: add RTL8723B/RTL8723BS support Ping-Ke Shih
2026-07-21  7:56   ` Luka Gejak
2026-07-21  8:57     ` Ping-Ke Shih [this message]
2026-07-21 10:55       ` Luka Gejak
2026-07-21 14:47         ` Bitterblue Smith
2026-07-21 16:01           ` Luka Gejak
2026-07-21 17:12             ` Bitterblue Smith
2026-07-21  9:49     ` Peter Robinson
  -- strict thread matches above, loose matches on Subject: below --
2026-07-18 17:38 Peter Robinson
2026-07-19 18:12 ` 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=cbaa891f94ce41c7a6a1d576db50b75c@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=pbrobinson@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