linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Pedersen <thomas@adapt-ip.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Thomas Pedersen <thomas@adapt-ip.com>
Subject: [RFC 4/7] mac80211: add freq_offset to RX status
Date: Tue, 31 Mar 2020 23:21:47 -0700	[thread overview]
Message-ID: <20200401062150.3324-5-thomas@adapt-ip.com> (raw)
In-Reply-To: <20200401062150.3324-1-thomas@adapt-ip.com>

RX status needs a KHz component, so add freq_offset. We
can make ampdu_reference u16 since it is probably
sufficient to be able to distinguish 64k different
A-MPDUs.

Signed-off-by: Thomas Pedersen <thomas@adapt-ip.com>
---
 include/net/mac80211.h | 10 +++++++++-
 net/mac80211/mlme.c    |  6 ++++--
 net/mac80211/rx.c      |  1 +
 net/mac80211/scan.c    |  3 ++-
 4 files changed, 16 insertions(+), 4 deletions(-)

diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index b6b4de0e4b5e..459ec57248fc 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -1333,6 +1333,7 @@ enum mac80211_rx_encoding {
  * @freq: frequency the radio was tuned to when receiving this frame, in MHz
  *	This field must be set for management frames, but isn't strictly needed
  *	for data (other) frames - for those it only affects radiotap reporting.
+ * @freq_offset: positive KHz component of @freq.
  * @signal: signal strength when receiving this frame, either in dBm, in dB or
  *	unspecified depending on the hardware capabilities flags
  *	@IEEE80211_HW_SIGNAL_*
@@ -1361,9 +1362,10 @@ struct ieee80211_rx_status {
 	u64 mactime;
 	u64 boottime_ns;
 	u32 device_timestamp;
-	u32 ampdu_reference;
 	u32 flag;
+	u16 ampdu_reference;
 	u16 freq;
+	u16 freq_offset;
 	u8 enc_flags;
 	u8 encoding:2, bw:3, he_ru:3;
 	u8 he_gi:2, he_dcm:1;
@@ -1379,6 +1381,12 @@ struct ieee80211_rx_status {
 	u8 zero_length_psdu_type;
 };
 
+static inline u32
+ieee80211_rx_status_to_khz(struct ieee80211_rx_status *rx_status)
+{
+	return MHZ_TO_KHZ(rx_status->freq) + rx_status->freq_offset;
+}
+
 /**
  * struct ieee80211_vendor_radiotap - vendor radiotap data information
  * @present: presence bitmap for this vendor namespace
diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index 4eebee49bb7d..e5bcd786e333 100644
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -3669,7 +3669,8 @@ static void ieee80211_rx_bss_info(struct ieee80211_sub_if_data *sdata,
 
 	sdata_assert_lock(sdata);
 
-	channel = ieee80211_get_channel(local->hw.wiphy, rx_status->freq);
+	channel = ieee80211_get_channel_khz(local->hw.wiphy,
+				ieee80211_rx_status_to_khz(rx_status));
 	if (!channel)
 		return;
 
@@ -3885,7 +3886,8 @@ static void ieee80211_rx_mgmt_beacon(struct ieee80211_sub_if_data *sdata,
 		return;
 	}
 
-	if (rx_status->freq != chanctx_conf->def.chan->center_freq) {
+	if (rx_status->freq != chanctx_conf->def.chan->center_freq ||
+	    rx_status->freq_offset != chanctx_conf->def.chan->freq_offset) {
 		rcu_read_unlock();
 		return;
 	}
diff --git a/net/mac80211/rx.c b/net/mac80211/rx.c
index 91a13aee4378..0b6dca4c0c7d 100644
--- a/net/mac80211/rx.c
+++ b/net/mac80211/rx.c
@@ -412,6 +412,7 @@ ieee80211_add_rx_radiotap_header(struct ieee80211_local *local,
 	pos++;
 
 	/* IEEE80211_RADIOTAP_CHANNEL */
+	/* TODO: frequency offset in KHz */
 	put_unaligned_le16(status->freq, pos);
 	pos += 2;
 	if (status->bw == RATE_INFO_BW_10)
diff --git a/net/mac80211/scan.c b/net/mac80211/scan.c
index 4d14118dddca..5db15996524f 100644
--- a/net/mac80211/scan.c
+++ b/net/mac80211/scan.c
@@ -275,7 +275,8 @@ void ieee80211_scan_rx(struct ieee80211_local *local, struct sk_buff *skb)
 			return;
 	}
 
-	channel = ieee80211_get_channel(local->hw.wiphy, rx_status->freq);
+	channel = ieee80211_get_channel_khz(local->hw.wiphy,
+					ieee80211_rx_status_to_khz(rx_status));
 
 	if (!channel || channel->flags & IEEE80211_CHAN_DISABLED)
 		return;
-- 
2.20.1


  parent reply	other threads:[~2020-04-01  6:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  6:21 [RFC 0/7] add a KHz component to wireless channels Thomas Pedersen
2020-04-01  6:21 ` [RFC 1/7] ieee80211: share 802.11 unit conversion helpers Thomas Pedersen
2020-04-01  6:21 ` [RFC 2/7] cfg80211: express channels with a KHz component Thomas Pedersen
2020-04-01  6:54   ` Johannes Berg
2020-04-01 17:30     ` Thomas Pedersen
2020-04-01 17:53       ` Johannes Berg
2020-04-01 21:32         ` Thomas Pedersen
2020-04-01  6:21 ` [RFC 3/7] mac80211: handle channel frequency offset Thomas Pedersen
2020-04-01  6:59   ` Johannes Berg
2020-04-01 17:39     ` Thomas Pedersen
2020-04-01 17:53       ` Johannes Berg
2020-04-01  6:21 ` Thomas Pedersen [this message]
2020-04-01  7:08   ` [RFC 4/7] mac80211: add freq_offset to RX status Johannes Berg
2020-04-01 17:58     ` Thomas Pedersen
2020-04-01  6:21 ` [RFC 5/7] cfg80211: report frequency in KHz for management RX Thomas Pedersen
2020-04-01  6:21 ` [RFC 6/7] nl80211: add KHz frequency offset for most wifi commands Thomas Pedersen
2020-04-01  7:10   ` Johannes Berg
2020-04-01 18:15     ` Thomas Pedersen
2020-04-01  7:12   ` Johannes Berg
2020-04-01  6:21 ` [RFC 7/7] nl80211: accept scan frequencies in KHz Thomas Pedersen
2020-04-01  7:15 ` [RFC 0/7] add a KHz component to wireless channels Johannes Berg
2020-04-01 18:26   ` Thomas Pedersen

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=20200401062150.3324-5-thomas@adapt-ip.com \
    --to=thomas@adapt-ip.com \
    --cc=johannes@sipsolutions.net \
    --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).