From: Pkshih <pkshih@realtek.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>,
"quic_jjohnson@quicinc.com" <quic_jjohnson@quicinc.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Kevin Yang" <kevin_yang@realtek.com>
Subject: Re: [PATCH 5/6] rtw89: convert rtw89_band to nl80211_band precisely
Date: Mon, 16 May 2022 00:41:14 +0000 [thread overview]
Message-ID: <4dab18241944c2e262190500ecd9d524e69d711e.camel@realtek.com> (raw)
In-Reply-To: <548d2149-f47a-6afb-92e5-124abcecfe51@quicinc.com>
On Fri, 2022-05-13 at 09:34 -0700, Jeff Johnson wrote:
> On 5/12/2022 10:42 PM, Ping-Ke Shih wrote:
> > From: Zong-Zhe Yang <kevin_yang@realtek.com>
> >
> > Before 6G band was supported, i.e. only 2G and 5G, they were the same
> > from the numerical point of view. However, after 6G band support, we
> > need to do this conversion logically.
>
> In the ath drivers we've been trying to avoid using the terms 2G/5G/6G
> to describe frequencies since that usage conflicts with the cellular use
> of similar terms to describe generations of the technology, and further
> could cause confusion now that WFA is also defining generations of Wi-Fi
> by number instead of by IEEE 802.11 amendment.
>
> To that end it would be nice if we could universally adopt using proper
> SI terminology when referring to Wi-Fi frequencies:
> 2 GHz (or 2.4 GHz), 5 GHz, & 6 GHz
>
I will use SI terminology by v2, and share this information with my
members. Also, I will plan to rename the enum(s) of driver in separate
patch later.
--
Ping-Ke
next prev parent reply other threads:[~2022-05-16 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 5:42 [PATCH 0/6] rtw89: add missing functions and fix misbehavior found by verification Ping-Ke Shih
2022-05-13 5:42 ` [PATCH 1/6] rtw89: add ieee80211::sta_rc_update ops Ping-Ke Shih
2022-05-13 5:42 ` [PATCH 2/6] rtw89: 8852c: set TX antenna path Ping-Ke Shih
2022-05-13 5:42 ` [PATCH 3/6] rtw89: cfo: check mac_id to avoid out-of-bounds Ping-Ke Shih
2022-05-13 5:42 ` [PATCH 4/6] rtw89: 8852c: update txpwr tables to HALRF_027_00_052 Ping-Ke Shih
2022-05-13 5:42 ` [PATCH 5/6] rtw89: convert rtw89_band to nl80211_band precisely Ping-Ke Shih
2022-05-13 16:34 ` Jeff Johnson
2022-05-16 0:41 ` Pkshih [this message]
2022-05-13 5:42 ` [PATCH 6/6] rtw89: pci: only mask out INT indicator register for disable interrupt v1 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=4dab18241944c2e262190500ecd9d524e69d711e.camel@realtek.com \
--to=pkshih@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.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.