From: Ping-Ke Shih <pkshih@realtek.com>
To: <kvalo@kernel.org>
Cc: <johannes@sipsolutions.net>, <phhuang@realtek.com>,
<linux-wireless@vger.kernel.org>
Subject: [PATCH 1/3] wifi: ieee80211: add UL-bandwidth definition of trigger frame
Date: Mon, 25 Sep 2023 16:08:59 +0800 [thread overview]
Message-ID: <20230925080902.51449-2-pkshih@realtek.com> (raw)
In-Reply-To: <20230925080902.51449-1-pkshih@realtek.com>
From: Po-Hao Huang <phhuang@realtek.com>
Define UL-bandwidth values of trigger frame according to 802.11 std.
Signed-off-by: Po-Hao Huang <phhuang@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
include/linux/ieee80211.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/linux/ieee80211.h b/include/linux/ieee80211.h
index 340d7e0f6bf7..691e387c8056 100644
--- a/include/linux/ieee80211.h
+++ b/include/linux/ieee80211.h
@@ -307,6 +307,13 @@ static inline u16 ieee80211_sn_sub(u16 sn1, u16 sn2)
#define IEEE80211_TRIGGER_TYPE_BQRP 0x6
#define IEEE80211_TRIGGER_TYPE_NFRP 0x7
+/* UL-bandwidth within common_info of trigger frame */
+#define IEEE80211_TRIGGER_ULBW_MASK 0xc0000
+#define IEEE80211_TRIGGER_ULBW_20MHZ 0x0
+#define IEEE80211_TRIGGER_ULBW_40MHZ 0x1
+#define IEEE80211_TRIGGER_ULBW_80MHZ 0x2
+#define IEEE80211_TRIGGER_ULBW_160_80P80MHZ 0x3
+
struct ieee80211_hdr {
__le16 frame_control;
__le16 duration_id;
--
2.25.1
next prev parent reply other threads:[~2023-09-25 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 8:08 [PATCH 0/3] wifi: rtw89: consider UL-bandwidth of trigger frame as clue to improve OFDMA performance Ping-Ke Shih
2023-09-25 8:08 ` Ping-Ke Shih [this message]
2023-09-25 8:09 ` [PATCH 2/3] wifi: rtw89: refine uplink trigger based control mechanism Ping-Ke Shih
2023-09-28 16:20 ` Kalle Valo
2023-09-28 16:24 ` Kalle Valo
2023-09-29 0:42 ` Ping-Ke Shih
2023-09-25 8:09 ` [PATCH 3/3] wifi: rtw89: Refine bandwidth 160MHz uplink OFDMA performance Ping-Ke Shih
2023-09-25 8:09 ` [PATCH 3/3] wifi: rtw89: refine " 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=20230925080902.51449-2-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@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.