linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pkshih <pkshih@realtek.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH v7 00/24] rtw89: add Realtek 802.11ax driver
Date: Wed, 13 Oct 2021 08:55:29 +0000	[thread overview]
Message-ID: <adfb1ac4113c4ff08fd31596161a4146@realtek.com> (raw)
In-Reply-To: <87h7dlwj58.fsf@codeaurora.org>


> -----Original Message-----
> From: kvalo=codeaurora.org@mg.codeaurora.org <kvalo=codeaurora.org@mg.codeaurora.org> On
> Behalf Of Kalle Valo
> Sent: Wednesday, October 13, 2021 2:09 PM
> To: Pkshih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: [PATCH v7 00/24] rtw89: add Realtek 802.11ax driver
> 
> Pkshih <pkshih@realtek.com> writes:
> 
> >> -----Original Message-----
> >> From: kvalo=codeaurora.org@mg.codeaurora.org
> >> <kvalo=codeaurora.org@mg.codeaurora.org> On
> >> Behalf Of Kalle Valo
> >> Sent: Monday, October 11, 2021 8:07 PM
> >> To: Pkshih <pkshih@realtek.com>
> >> Cc: linux-wireless@vger.kernel.org
> >> Subject: Re: [PATCH v7 00/24] rtw89: add Realtek 802.11ax driver
> >>
> >> Kalle Valo <kvalo@codeaurora.org> writes:
> >>
> >> > Ping-Ke Shih <pkshih@realtek.com> writes:
> >> >
> >> >> This driver named rtw89, which is the next generation of rtw88, supports
> >> >> Realtek 8852AE 802.11ax 2x2 chip whose new features are OFDMA, DBCC,
> >> >> Spatial reuse, TWT and BSS coloring; now some of them aren't implemented
> >> >> though.
> >> >>
> >> >> The chip architecture is entirely different from the chips supported by
> >> >> rtw88 like RTL8822CE 802.11ac chip. First of all, register address ranges
> >> >> are totally redefined, so it's impossible to reuse register definition. To
> >> >> communicate with firmware, new H2C/C2H format is proposed. In order to have
> >> >> better utilization, TX DMA flow is changed to two stages DMA. To provide
> >> >> rich RX status information, additional RX PPDU packets are added.
> >> >>
> >> >> Since there are so many differences mentioned above, we decide to propose
> >> >> a new driver. It has many authors, they are listed in alphabetic order:
> >> >>
> >> >> Chin-Yen Lee <timlee@realtek.com>
> >> >> Ping-Ke Shih <pkshih@realtek.com>
> >> >> Po Hao Huang <phhuang@realtek.com>
> >> >> Tzu-En Huang <tehuang@realtek.com>
> >> >> Vincent Fann <vincent_fann@realtek.com>
> >> >> Yan-Hsuan Chuang <tony0620emma@gmail.com>
> >> >> Zong-Zhe Yang <kevin_yang@realtek.com>
> >> >>
> >> >> Tested-by: Brian Norris <briannorris@chromium.org>
> >> >> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> >> >>
> >> >> v7:
> >> >>   - use consistent license of Kconfig
> >> >>   - remove #ifdef and dummy functions from coex.c
> >> >>   - C2H handler of coex uses meaningful naming insetad, and use le32_to_cpu()
> >> >>     to convert the value.
> >> >>   - add icmp packet notify to coex
> >> >>   - use function call instead of a work to notify coex about traffic changed
> >> >>   - fix dereference security CAM NULL pointer while disconnecting occasionally
> >> >>   - fill tx descriptor once a 32 bits word (Suggested by Arnd. Thanks!)
> >> >>   - use static pci PS, so remove pci link_ps
> >> >>   - make many mac tables constant
> >> >>   - add early_h2c debugfs entry to notify firmware early
> >> >>   - support new RA report format
> >> >>   - configure retry_lowest_rate by band
> >> >>   - avoid to use of whil(1) to parse power sequence
> >> >>   - notify rfk before/after scanning to reset status
> >> >>   - firmware: rtw89: 8852a: update fw to v0.13.30.0
> >> >>     https://github.com/pkshih/linux-firmware.git
> >> >>     pick the commit 6595133a7cde82be932067afde834dcd036167f8
> >> >
> >> > I have not reviewed this version yet, but I pushed it to the pending
> >> > branch for build testing:
> >> >
> >> >
> >>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git/commit/?h=
> >> pending&id=c321740f93af1a31d9e149ce5077e28bd4e859f7
> >> >
> >> > For the final commit my plan is to squash all patches into one big
> >> > patch. I will do that after reviewing v7, if everything is ok of course.
> >> >
> >> > Are there more Tested-by or Reviewed-by tags?
> >
> > Sorry for the late reply. Because our National Day is Oct. 10th, and
> > additional holiday on Oct. 11th.
> >
> > Aaron have tested v5 and a tag is given [1].
> >
> > Tested-by: Aaron Ma <aaron.ma@canonical.com>
> 
> I added Aaron to the commit log and pushed the driver to the master
> branch:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git/commit/?id
> =e3ec7017f6a20d12ddd9fe23d345ebb7b8c104dd
> 
> So the driver is now officially accepted, a big thank you to everyone
> who participated with the review and testing! Now let's see what kind of
> reports we get from linux-next.
> 

Thank you!

Should I add myself to the file MAINTAINERS?

--
Ping-Ke


  reply	other threads:[~2021-10-13  8:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  3:56 [PATCH v7 00/24] rtw89: add Realtek 802.11ax driver Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 01/24] rtw89: add CAM files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 02/24] rtw89: add BT coexistence files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 03/24] rtw89: add core and trx files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 04/24] rtw89: add debug files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 05/24] rtw89: add efuse files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 06/24] rtw89: add files to download and communicate with firmware Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 07/24] rtw89: add MAC files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 08/24] rtw89: implement mac80211 ops Ping-Ke Shih
2021-10-08 17:45   ` Toke Høiland-Jørgensen
2021-10-12  8:39     ` Pkshih
2021-10-08  3:56 ` [PATCH v7 09/24] rtw89: add pci files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 10/24] rtw89: add phy files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 11/24] rtw89: define register names Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 12/24] rtw89: add regulatory support Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 13/24] rtw89: 8852a: add 8852a specific files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 14/24] rtw89: 8852a: add 8852a RFK files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 15/24] rtw89: 8852a: add 8852a RFK tables Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 16/24] rtw89: 8852a: add 8852a tables (1 of 5) Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 17/24] rtw89: 8852a: add 8852a tables (2 " Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 18/24] rtw89: 8852a: add 8852a tables (3 " Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 19/24] rtw89: 8852a: add 8852a tables (4 " Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 20/24] rtw89: 8852a: add 8852a tables (5 " Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 21/24] rtw89: add ser to recover error reported by firmware Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 22/24] rtw89: add PS files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 23/24] rtw89: add SAR files Ping-Ke Shih
2021-10-08  3:56 ` [PATCH v7 24/24] rtw89: add Kconfig and Makefile Ping-Ke Shih
2021-10-09  8:21 ` [PATCH v7 00/24] rtw89: add Realtek 802.11ax driver Kalle Valo
2021-10-11 12:06   ` Kalle Valo
2021-10-12  1:32     ` Pkshih
2021-10-13  6:09       ` Kalle Valo
2021-10-13  8:55         ` Pkshih [this message]
2021-10-13  9:06           ` Kalle Valo

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=adfb1ac4113c4ff08fd31596161a4146@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).