All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Chuang <yhchuang@realtek.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
	"Larry.Finger\@lwfinger.net" <Larry.Finger@lwfinger.net>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>, Pkshih <pkshih@realtek.com>,
	Andy Huang <tehuang@realtek.com>
Subject: Re: [RFC 00/12] rtwlan: mac80211 driver for Realtek 802.11ac wireless network chips
Date: Sat, 06 Oct 2018 14:45:46 +0300	[thread overview]
Message-ID: <877eivguxh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <F7CD281DE3E379468C6D07993EA72F84D08D7F89@RTITMBSVM01.realtek.com.tw> (Tony Chuang's message of "Tue, 25 Sep 2018 11:09:06 +0000")

Tony Chuang <yhchuang@realtek.com> writes:

>> -----Original Message-----
>> From: Kalle Valo [mailto:kvalo@codeaurora.org]
>> Sent: Monday, September 24, 2018 7:05 PM
>> To: Stanislaw Gruszka
>> Cc: Tony Chuang; Larry.Finger@lwfinger.net; linux-wireless@vger.kernel.org;
>> Pkshih; Andy Huang
>> Subject: Re: [RFC 00/12] rtwlan: mac80211 driver for Realtek 802.11ac
>> wireless network chips
>> 
>> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>> 
>> > On Fri, Sep 21, 2018 at 02:03:55PM +0800, yhchuang@realtek.com wrote:
>> >> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>> >>
>> >> This is a new mac80211 driver for Realtek 802.11ac wireless network chips.
>> >> rtwlan supports 8822BE and 8822CE chips, and will be able to support
>> >> multi-vif combinations in run-time.
>> >>
>> >> For now, only PCI bus is supported, but rtwlan was originally designed
>> >> to optionally support three buses includes USB & SDIO. USB & SDIO
>> modules
>> >> will soon be supported by rtwlan, with configurable core module to fit
>> >> with different bus modules in the same time.
>> >>
>> >> For example, if we choose 8822BE and 8822CU, only PCI & USB modules
>> will
>> >> be selected, built, loaded into kernel. This is one of the major
>> >> difference from rtlwifi, which can only support specific combinations.
>> >>
>> >> Another difference from rtlwifi is that rtwlan is designed to support
>> >> the latest Realtek 802.11ac wireless network chips like 8822B and
>> >> 8822C series. Compared to the earlier chips supported by rtlwifi like
>> >> the 802.11n 8192EE chipset or 802.11ac 8821AE/8812AE chips, newer ICs
>> >> have different MAC & PHY settings, such as new multi-port feature for the
>> >> MAC layer design and Jaguar2/Jaguar3 PHY layer IPs.
>> >>
>> >> Multi-Port feature is also supported under rtwlan's software architecture.
>> >> rtlwifi can only support one vif in the same time, most because of the
>> >> hardware limitations for early chips, hence the original design of it
>> >> also restricts the usage of multi-vif support, so latest chipset seems not
>> >> take advantages from its new MAC engine.
>> >>
>> >> However, rtwlan can run multiple vifs concurrently by holding them on
>> >> hardware ports provided by MAC engine, so we can easily start different
>> >> roles on a single device.
>> >>
>> >> Based on the reasons mentioned before, we implemented rtwlan. It had
>> many
>> >> authors, they are listed here alphabetically:
>> >>
>> >> Ping-Ke Shih <pkshih@realtek.com>
>> >> Tzu-En Huang <tehuang@realtek.com>
>> >> Yan-Hsuan Chuang <yhchuang@realtek.com>
>> >
>> > I didn't do detailed review, but my general impression is very very
>> > positive. New driver looks great!
>> 
>> I also did a quick 10 min look at the driver and indeed in general it
>> looks good.
>> 
>> > Just 2 generic remarks:
>> > - please add MAINTAINERS file entry
>> > - please post a patch or request to remove staging/rtlwifi driver
>> >   since this one is replace for it (8822BE PCI-ID is the same)
>> 
>> Something I noticed:
>> 
>> o Magic numbers (BIT(1) etc) in quite a few places.
>> 
>> o Personally not really fond of "#ifdef LITTLE_ENDIAN" usage, but I
>>   guess we can live with that?
>> 
>> o To me the name "rtwlan" sounds confusing when one compares it with
>>   "rtlwifi". And how would the possible next generation 11ax driver be
>>   then called? As a good example I really like the driver name mt76,
>>   could this one have something similar to make it more descriptive?
>> 
>> I also pushed this to the pending branch on wireless-drivers-next so
>> that kbuild bot can extensively test it.
>
> Yes, we will add MAINTAINER files entry after this driver.
> got accepted into the kernel, or should we include the entry in this patch?

Please update the MAINTAINERS file in this patchset, just in a separate
patch. I can them apply it at the same time as the driver (once it's
ready).

-- 
Kalle Valo

  reply	other threads:[~2018-10-06 11:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21  6:03 [RFC 00/12] rtwlan: mac80211 driver for Realtek 802.11ac wireless network chips yhchuang
2018-09-21  6:03 ` [PATCH 01/12] rtwlan: main files yhchuang
2018-09-27 13:50   ` Stanislaw Gruszka
2018-09-27 15:40     ` Larry Finger
2018-09-28  9:08       ` Stanislaw Gruszka
2018-10-04 12:32         ` Kalle Valo
2018-09-28  3:20     ` Tony Chuang
2018-09-28  9:29       ` Stanislaw Gruszka
2018-09-28 11:32         ` Tony Chuang
2018-10-02 10:29           ` Stanislaw Gruszka
2018-10-02 15:23             ` Larry Finger
2018-10-03  2:57               ` Tony Chuang
2018-10-03  5:40                 ` Larry Finger
2018-10-04 12:39                   ` Kalle Valo
2018-10-04 13:42                     ` Stanislaw Gruszka
2018-10-04 16:19                       ` Larry Finger
2018-10-05  7:51                         ` Stanislaw Gruszka
2018-10-06 12:20                         ` Kalle Valo
2018-10-06 12:16                       ` Kalle Valo
2018-10-04 12:35               ` Kalle Valo
2018-10-02  9:35         ` Tony Chuang
2018-10-02 10:14           ` Stanislaw Gruszka
2018-10-03  3:25             ` Tony Chuang
2018-10-03  6:05               ` Stanislaw Gruszka
2018-10-04 12:30           ` Kalle Valo
2018-09-21  6:03 ` [PATCH 02/12] rtwlan: core files yhchuang
2018-09-21  6:03 ` [PATCH 03/12] rtwlan: hci files yhchuang
2018-09-21  6:03 ` [PATCH 04/12] rtwlan: trx files yhchuang
2018-09-21  6:04 ` [PATCH 05/12] rtwlan: mac files yhchuang
2018-09-21  6:04 ` [PATCH 06/12] rtwlan: fw and efuse files yhchuang
2018-09-21  6:04 ` [PATCH 07/12] rtwlan: phy files yhchuang
2018-09-21  6:04 ` [PATCH 08/12] rtwlan: debug files yhchuang
2018-09-21  6:04 ` [PATCH 09/12] rtwlan: chip files yhchuang
2018-09-21  6:04 ` [PATCH 10/12] rtwlan: 8822B init table yhchuang
2018-09-21  6:04 ` [PATCH 11/12] rtwlan: 8822C " yhchuang
2018-09-21  6:04 ` [PATCH 12/12] rtwlan: Kconfig & Makefile yhchuang
2018-09-22 23:39   ` kbuild test robot
2018-09-23  8:55   ` kbuild test robot
2018-09-21 13:12 ` [RFC 00/12] rtwlan: mac80211 driver for Realtek 802.11ac wireless network chips Stanislaw Gruszka
2018-09-24 11:05   ` Kalle Valo
2018-09-25 11:09     ` Tony Chuang
2018-10-06 11:45       ` Kalle Valo [this message]
     [not found]   ` <CAP71bdW0P8xFeLfGgNeENJf_9+S+DTnK4S=tXZi1FPY7U-AL3A@mail.gmail.com>
2018-09-24 11:08     ` Kalle Valo
2018-09-24 17:09 ` Larry Finger
2018-09-25 11:10   ` Tony Chuang

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=877eivguxh.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=sgruszka@redhat.com \
    --cc=tehuang@realtek.com \
    --cc=yhchuang@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.