From: Pkshih <pkshih@realtek.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] rtw89: declare HE capabilities in 6G band
Date: Mon, 7 Mar 2022 01:33:09 +0000 [thread overview]
Message-ID: <70c84df91e244987a657948ef440edb1@realtek.com> (raw)
In-Reply-To: <050529f958bb628ee6e2819c944b42951b621893.camel@sipsolutions.net>
> -----Original Message-----
> From: Johannes Berg <johannes@sipsolutions.net>
> Sent: Friday, March 4, 2022 5:20 PM
> To: Pkshih <pkshih@realtek.com>; kvalo@kernel.org
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: [PATCH] rtw89: declare HE capabilities in 6G band
>
> On Fri, 2022-03-04 at 15:34 +0800, Ping-Ke Shih wrote:
> > To work properly in 6G band, declare HE 6G capabilities. Without this fix,
> > it can only TX/RX with OFDM rates.
> >
> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> > ---
> > drivers/net/wireless/realtek/rtw89/core.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/drivers/net/wireless/realtek/rtw89/core.c b/drivers/net/wireless/realtek/rtw89/core.c
> > index a0086b14550a8..81c1c28e6e92c 100644
> > --- a/drivers/net/wireless/realtek/rtw89/core.c
> > +++ b/drivers/net/wireless/realtek/rtw89/core.c
> > @@ -2383,6 +2383,15 @@ static void rtw89_init_he_cap(struct rtw89_dev *rtwdev,
> > he_cap->he_mcs_nss_supp.tx_mcs_160 = cpu_to_le16(mcs_map);
> > }
> >
> > + if (band == NL80211_BAND_6GHZ) {
> > + __le16 capa;
> > +
> > + capa = u16_encode_bits(0, IEEE80211_HE_6GHZ_CAP_MIN_MPDU_START) |
> >
>
> le16_encode_bits()? I guess sparse would tell.
>
> But it looks weird with the constants, I guess you mean
>
> le16_encode_bits(IEEE80211_HT_MPDU_DENSITY_NONE,
> IEEE80211_HE_6GHZ_CAP_MIN_MPDU_START) |
> le16_encode_bits(IEEE80211_VHT_MAX_AMPDU_1024K, ...) |
> ...
>
> (there's documentation in ieee80211.h which value enums should be used)
>
Thanks for pointing out these.
I have fixed them and sent v2.
--
Ping-Ke
prev parent reply other threads:[~2022-03-07 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 7:34 [PATCH] rtw89: declare HE capabilities in 6G band Ping-Ke Shih
2022-03-04 9:19 ` Johannes Berg
2022-03-07 1:33 ` Pkshih [this message]
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=70c84df91e244987a657948ef440edb1@realtek.com \
--to=pkshih@realtek.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.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 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.