* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 17:06 Pradeep Kumar Chitrapu 2018-09-06 17:06 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu 2018-09-06 19:58 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg 0 siblings, 2 replies; 10+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 17:06 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: linux-wireless, david.spinadel, Pradeep Kumar Chitrapu Currently ftm_responder parameter in hostapd.conf is only used for fine timing measurement (FTM) capability advertisement and actual control of the functionality is with low-level device/driver. This leads to confusion to the user when the capability advertisement is different from actual FTM responder functionality. For example, FTM responder capability advertisement is set to 'enabled', but the functionality is disabled or not supported by the driver. The patch set allows userspace to enable FTM responder functionality with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER with configurable lci/civic ocation parameters. Also extended feature flag is added for the drivers to advertise the support. Setting the flag to enable FTM responder would imply that AP responds to all FTM requests. Default is considered to be disabled. changes in V3: - fixed the ambiguous ftm responder disable case to be not supported changes in V2: - updated version number - rebased patches Johannes Berg, Pradeep Kumar Chitrapu (1): cfg80211: support FTM responder configuration/statistics David Spinadel, Johannes Berg, Pradeep Kumar Chitrapu (1): mac80211: support FTM responder configuration/statistics Pradeep Kumar Chitrapu (1): ath10k: Add support to configure ftm responder role drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/mac.c | 29 ++++++++ drivers/net/wireless/ath/ath10k/wmi.c | 4 ++ drivers/net/wireless/ath/ath10k/wmi.h | 10 +++ include/net/cfg80211.h | 66 ++++++++++++++++++ include/net/mac80211.h | 13 ++++ include/uapi/linux/nl80211.h | 81 +++++++++++++++++++++ net/mac80211/cfg.c | 84 ++++++++++++++++++++++ net/mac80211/driver-ops.h | 16 +++++ net/mac80211/trace.h | 23 ++++++ net/mac80211/util.c | 3 + net/wireless/nl80211.c | 124 +++++++++++++++++++++++++++++++-- net/wireless/rdev-ops.h | 15 ++++ net/wireless/trace.h | 44 ++++++++++++ 14 files changed, 508 insertions(+), 5 deletions(-) -- 1.9.1 ^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH v3 3/3] ath10k: Add support to configure ftm responder role 2018-09-06 17:06 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu @ 2018-09-06 17:06 ` Pradeep Kumar Chitrapu 2018-09-06 19:58 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg 1 sibling, 0 replies; 10+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 17:06 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: linux-wireless, david.spinadel, Pradeep Kumar Chitrapu Configure fine timing measurement (FTM) responder role from the ftm_responder bss param sent by mac80211. With FTM functionality offloaded to firmware, adding the interface allows userspace to enable FTM responder functionality. ath10k disables it at the time of interface creation. Supported FW: 10.4 Tested on QCA9984 with firmware: 10.4-3.6-00144 Signed-off-by: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> --- drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/mac.c | 29 +++++++++++++++++++++++++++++ drivers/net/wireless/ath/ath10k/wmi.c | 4 ++++ drivers/net/wireless/ath/ath10k/wmi.h | 10 ++++++++++ 4 files changed, 44 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wireless/ath/ath10k/core.h index 9feea02e7d37..db190230b292 100644 --- a/drivers/net/wireless/ath/ath10k/core.h +++ b/drivers/net/wireless/ath/ath10k/core.h @@ -544,6 +544,7 @@ struct ath10k_vif { bool nohwcrypt; int num_legacy_stations; int txpower; + bool ftm_responder; struct wmi_wmm_params_all_arg wmm_params; struct work_struct ap_csa_work; struct delayed_work connection_loss_work; diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c index 078058eef648..474df855342b 100644 --- a/drivers/net/wireless/ath/ath10k/mac.c +++ b/drivers/net/wireless/ath/ath10k/mac.c @@ -5260,6 +5260,17 @@ static int ath10k_add_interface(struct ieee80211_hw *hw, goto err_peer_delete; } + if (test_bit(WMI_SERVICE_RTT, ar->wmi.svc_map)) { + vdev_param = ar->wmi.vdev_param->rtt_responder_role; + ret = ath10k_wmi_vdev_set_param(ar, arvif->vdev_id, vdev_param, + arvif->ftm_responder); + + /* It is harmless to not set FTM role. Do not warn */ + if (ret && ret != -EOPNOTSUPP) + ath10k_warn(ar, "failed to set vdev %i FTM Responder: %d\n", + arvif->vdev_id, ret); + } + if (vif->type == NL80211_IFTYPE_MONITOR) { ar->monitor_arvif = arvif; ret = ath10k_monitor_recalc(ar); @@ -5533,6 +5544,20 @@ static void ath10k_bss_info_changed(struct ieee80211_hw *hw, if (changed & BSS_CHANGED_BSSID && !is_zero_ether_addr(info->bssid)) ether_addr_copy(arvif->bssid, info->bssid); + if (changed & BSS_CHANGED_FTM_RESPONDER && + arvif->ftm_responder != info->ftm_responder && + test_bit(WMI_SERVICE_RTT, ar->wmi.svc_map)) { + arvif->ftm_responder = info->ftm_responder; + + vdev_param = ar->wmi.vdev_param->rtt_responder_role; + ret = ath10k_wmi_vdev_set_param(ar, arvif->vdev_id, vdev_param, + arvif->ftm_responder); + + ath10k_dbg(ar, ATH10K_DBG_MAC, + "mac vdev %d ftm_responder %d:ret %d\n", + arvif->vdev_id, arvif->ftm_responder, ret); + } + if (changed & BSS_CHANGED_BEACON_ENABLED) ath10k_control_beaconing(arvif, info); @@ -8469,6 +8494,10 @@ int ath10k_mac_register(struct ath10k *ar) wiphy_ext_feature_set(ar->hw->wiphy, NL80211_EXT_FEATURE_SET_SCAN_DWELL); + if (test_bit(WMI_SERVICE_RTT, ar->wmi.svc_map)) + wiphy_ext_feature_set(ar->hw->wiphy, + NL80211_EXT_FEATURE_ENABLE_FTM_RESPONDER); + /* * on LL hardware queues are managed entirely by the FW * so we only advertise to mac we can do the queues thing diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c index 212005cd0646..8e7f3a444e4b 100644 --- a/drivers/net/wireless/ath/ath10k/wmi.c +++ b/drivers/net/wireless/ath/ath10k/wmi.c @@ -825,6 +825,7 @@ .meru_vc = WMI_VDEV_PARAM_UNSUPPORTED, .rx_decap_type = WMI_VDEV_PARAM_UNSUPPORTED, .bw_nss_ratemask = WMI_VDEV_PARAM_UNSUPPORTED, + .rtt_responder_role = WMI_VDEV_PARAM_UNSUPPORTED, }; /* 10.X WMI VDEV param map */ @@ -900,6 +901,7 @@ .meru_vc = WMI_VDEV_PARAM_UNSUPPORTED, .rx_decap_type = WMI_VDEV_PARAM_UNSUPPORTED, .bw_nss_ratemask = WMI_VDEV_PARAM_UNSUPPORTED, + .rtt_responder_role = WMI_VDEV_PARAM_UNSUPPORTED, }; static struct wmi_vdev_param_map wmi_10_2_4_vdev_param_map = { @@ -974,6 +976,7 @@ .meru_vc = WMI_VDEV_PARAM_UNSUPPORTED, .rx_decap_type = WMI_VDEV_PARAM_UNSUPPORTED, .bw_nss_ratemask = WMI_VDEV_PARAM_UNSUPPORTED, + .rtt_responder_role = WMI_VDEV_PARAM_UNSUPPORTED, }; static struct wmi_vdev_param_map wmi_10_4_vdev_param_map = { @@ -1051,6 +1054,7 @@ .bw_nss_ratemask = WMI_10_4_VDEV_PARAM_BW_NSS_RATEMASK, .inc_tsf = WMI_10_4_VDEV_PARAM_TSF_INCREMENT, .dec_tsf = WMI_10_4_VDEV_PARAM_TSF_DECREMENT, + .rtt_responder_role = WMI_10_4_VDEV_PARAM_ENABLE_DISABLE_RTT_RESPONDER_ROLE, }; static struct wmi_pdev_param_map wmi_pdev_param_map = { diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drivers/net/wireless/ath/ath10k/wmi.h index 36220258e3c7..fa94873fe46f 100644 --- a/drivers/net/wireless/ath/ath10k/wmi.h +++ b/drivers/net/wireless/ath/ath10k/wmi.h @@ -5035,6 +5035,7 @@ struct wmi_vdev_param_map { u32 bw_nss_ratemask; u32 inc_tsf; u32 dec_tsf; + u32 rtt_responder_role; }; #define WMI_VDEV_PARAM_UNSUPPORTED 0 @@ -5374,6 +5375,15 @@ enum wmi_10_4_vdev_param { WMI_10_4_VDEV_PARAM_ATF_SSID_SCHED_POLICY, WMI_10_4_VDEV_PARAM_DISABLE_DYN_BW_RTS, WMI_10_4_VDEV_PARAM_TSF_DECREMENT, + WMI_10_4_VDEV_PARAM_SELFGEN_FIXED_RATE, + WMI_10_4_VDEV_PARAM_AMPDU_SUBFRAME_SIZE_PER_AC, + WMI_10_4_VDEV_PARAM_NSS_VHT160, + WMI_10_4_VDEV_PARAM_NSS_VHT80_80, + WMI_10_4_VDEV_PARAM_AMSDU_SUBFRAME_SIZE_PER_AC, + WMI_10_4_VDEV_PARAM_DISABLE_CABQ, + WMI_10_4_VDEV_PARAM_SIFS_TRIGGER_RATE, + WMI_10_4_VDEV_PARAM_TX_POWER, + WMI_10_4_VDEV_PARAM_ENABLE_DISABLE_RTT_RESPONDER_ROLE, }; #define WMI_VDEV_PARAM_TXBF_SU_TX_BFEE BIT(0) -- 1.9.1 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 17:06 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu 2018-09-06 17:06 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu @ 2018-09-06 19:58 ` Johannes Berg 2018-09-07 9:23 ` Arend van Spriel 1 sibling, 1 reply; 10+ messages in thread From: Johannes Berg @ 2018-09-06 19:58 UTC (permalink / raw) To: Pradeep Kumar Chitrapu, ath10k; +Cc: linux-wireless, david.spinadel I'm not sure what you're doing, but this time only the cover letter made it to the list, afaict. maybe try to resend from somewhere else? johannes > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 19:58 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg @ 2018-09-07 9:23 ` Arend van Spriel 0 siblings, 0 replies; 10+ messages in thread From: Arend van Spriel @ 2018-09-07 9:23 UTC (permalink / raw) To: Pradeep Kumar Chitrapu, ath10k Cc: Johannes Berg, linux-wireless, david.spinadel On 9/6/2018 9:58 PM, Johannes Berg wrote: > I'm not sure what you're doing, but this time only the cover letter made > it to the list, afaict. > > maybe try to resend from somewhere else? I guess you are using 'git send-email' so you could use --dry-run and check if every message would be send to the linux-wireless list. If it is your MTA is probably misconfigured. Regards, Arend ^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 21:11 Pradeep Kumar Chitrapu 0 siblings, 0 replies; 10+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 21:11 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: linux-wireless, david.spinadel, Pradeep Kumar Chitrapu Currently ftm_responder parameter in hostapd.conf is only used for fine timing measurement (FTM) capability advertisement and actual control of the functionality is with low-level device/driver. This leads to confusion to the user when the capability advertisement is different from actual FTM responder functionality. For example, FTM responder capability advertisement is set to 'enabled', but the functionality is disabled or not supported by the driver. The patch set allows userspace to enable FTM responder functionality with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER with configurable lci/civic ocation parameters. Also extended feature flag is added for the drivers to advertise the support. Setting the flag to enable FTM responder would imply that AP responds to all FTM requests. Default is considered to be disabled. changes in V3: - fixed the ambiguous ftm responder disable case to be not supported changes in V2: - updated version number - rebased patches Johannes Berg, Pradeep Kumar Chitrapu (1): cfg80211: support FTM responder configuration/statistics David Spinadel, Johannes Berg, Pradeep Kumar Chitrapu (1): mac80211: support FTM responder configuration/statistics Pradeep Kumar Chitrapu (1): ath10k: Add support to configure ftm responder role drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/mac.c | 29 ++++++++ drivers/net/wireless/ath/ath10k/wmi.c | 4 ++ drivers/net/wireless/ath/ath10k/wmi.h | 10 +++ include/net/cfg80211.h | 66 ++++++++++++++++++ include/net/mac80211.h | 13 ++++ include/uapi/linux/nl80211.h | 81 +++++++++++++++++++++ net/mac80211/cfg.c | 84 ++++++++++++++++++++++ net/mac80211/driver-ops.h | 16 +++++ net/mac80211/trace.h | 23 ++++++ net/mac80211/util.c | 3 + net/wireless/nl80211.c | 124 +++++++++++++++++++++++++++++++-- net/wireless/rdev-ops.h | 15 ++++ net/wireless/trace.h | 44 ++++++++++++ 14 files changed, 508 insertions(+), 5 deletions(-) -- 1.9.1 ^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 1:01 Pradeep Kumar Chitrapu 2018-09-06 6:34 ` Johannes Berg 0 siblings, 1 reply; 10+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 1:01 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: linux-wireless, david.spinadel, Pradeep Kumar Chitrapu Currently ftm_responder parameter in hostapd.conf is only used for fine timing measurement (FTM) capability advertisement and actual control of the functionality is with low-level device/driver. This leads to confusion to the user when the capability advertisement is different from actual FTM responder functionality. For example, FTM responder capability advertisement is set to 'enabled', but the functionality is disabled or not supported by the driver. The patch set allows userspace to enable FTM responder functionality with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER with configurable lci/civic ocation parameters. Also extended feature flag is added for the drivers to advertise the support. Setting the flag to enable FTM responder would imply that AP responds to all FTM requests. Default is considered to be disabled. changes in V3: - fixed the ambiguous ftm responder disable case to be not supported changes in V2: - updated version number - rebased patches Johannes Berg, Pradeep Kumar Chitrapu (1): cfg80211: support FTM responder configuration/statistics David Spinadel, Johannes Berg, Pradeep Kumar Chitrapu (1): mac80211: support FTM responder configuration/statistics Pradeep Kumar Chitrapu (1): ath10k: Add support to configure ftm responder role drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/mac.c | 29 ++++++++ drivers/net/wireless/ath/ath10k/wmi.c | 4 ++ drivers/net/wireless/ath/ath10k/wmi.h | 10 +++ include/net/cfg80211.h | 66 ++++++++++++++++++ include/net/mac80211.h | 13 ++++ include/uapi/linux/nl80211.h | 81 +++++++++++++++++++++ net/mac80211/cfg.c | 84 ++++++++++++++++++++++ net/mac80211/driver-ops.h | 16 +++++ net/mac80211/trace.h | 23 ++++++ net/mac80211/util.c | 3 + net/wireless/nl80211.c | 124 +++++++++++++++++++++++++++++++-- net/wireless/rdev-ops.h | 15 ++++ net/wireless/trace.h | 44 ++++++++++++ 14 files changed, 508 insertions(+), 5 deletions(-) -- 1.9.1 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 1:01 Pradeep Kumar Chitrapu @ 2018-09-06 6:34 ` Johannes Berg 2018-09-06 15:15 ` Kalle Valo 0 siblings, 1 reply; 10+ messages in thread From: Johannes Berg @ 2018-09-06 6:34 UTC (permalink / raw) To: Pradeep Kumar Chitrapu, ath10k; +Cc: linux-wireless, david.spinadel On Wed, 2018-09-05 at 18:01 -0700, Pradeep Kumar Chitrapu wrote: > Currently ftm_responder parameter in hostapd.conf is only used for fine > timing measurement (FTM) capability advertisement and actual control of > the functionality is with low-level device/driver. This leads to confusion > to the user when the capability advertisement is different from actual FTM > responder functionality. > > For example, FTM responder capability advertisement is set to 'enabled', > but the functionality is disabled or not supported by the driver. > > The patch set allows userspace to enable FTM responder functionality > with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER > with configurable lci/civic ocation parameters. Also extended feature flag > is added for the drivers to advertise the support. Setting the flag to > enable FTM responder would imply that AP responds to all FTM requests. > Default is considered to be disabled. > > changes in V3: > - fixed the ambiguous ftm responder disable case to be not supported For reasons unknown to me, this patchset made it neither to the list nor, consequently, patchwork. Please resend. johannes ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 6:34 ` Johannes Berg @ 2018-09-06 15:15 ` Kalle Valo 2018-09-06 16:08 ` Johannes Berg 0 siblings, 1 reply; 10+ messages in thread From: Kalle Valo @ 2018-09-06 15:15 UTC (permalink / raw) To: Johannes Berg Cc: Pradeep Kumar Chitrapu, ath10k, linux-wireless, david.spinadel Johannes Berg <johannes@sipsolutions.net> writes: > On Wed, 2018-09-05 at 18:01 -0700, Pradeep Kumar Chitrapu wrote: >> Currently ftm_responder parameter in hostapd.conf is only used for fine >> timing measurement (FTM) capability advertisement and actual control of >> the functionality is with low-level device/driver. This leads to confusion >> to the user when the capability advertisement is different from actual FTM >> responder functionality. >> >> For example, FTM responder capability advertisement is set to 'enabled', >> but the functionality is disabled or not supported by the driver. >> >> The patch set allows userspace to enable FTM responder functionality >> with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER >> with configurable lci/civic ocation parameters. Also extended feature flag >> is added for the drivers to advertise the support. Setting the flag to >> enable FTM responder would imply that AP responds to all FTM requests. >> Default is considered to be disabled. >> >> changes in V3: >> - fixed the ambiguous ftm responder disable case to be not supported > > For reasons unknown to me, this patchset made it neither to the list > nor, consequently, patchwork. Please resend. Actually patch 3 made it: https://patchwork.kernel.org/patch/10590115/ But it didn't get the rest as it says "Untitled series #15763". Patchwork was timing out for me quite heavily so in that way I'm not surprised that patches are getting lost :( -- Kalle Valo ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 15:15 ` Kalle Valo @ 2018-09-06 16:08 ` Johannes Berg 2018-09-06 16:18 ` Kalle Valo 0 siblings, 1 reply; 10+ messages in thread From: Johannes Berg @ 2018-09-06 16:08 UTC (permalink / raw) To: Kalle Valo; +Cc: Pradeep Kumar Chitrapu, ath10k, linux-wireless, david.spinadel On Thu, 2018-09-06 at 18:15 +0300, Kalle Valo wrote: > > Actually patch 3 made it: > > https://patchwork.kernel.org/patch/10590115/ > > But it didn't get the rest as it says "Untitled series #15763". > Patchwork was timing out for me quite heavily so in that way I'm not > surprised that patches are getting lost :( No, it's not patchwork - I didn't get the patches (except for #3) via the list either. johannes ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 16:08 ` Johannes Berg @ 2018-09-06 16:18 ` Kalle Valo 0 siblings, 0 replies; 10+ messages in thread From: Kalle Valo @ 2018-09-06 16:18 UTC (permalink / raw) To: Johannes Berg Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel, ath10k Johannes Berg <johannes@sipsolutions.net> writes: > On Thu, 2018-09-06 at 18:15 +0300, Kalle Valo wrote: >> >> Actually patch 3 made it: >> >> https://patchwork.kernel.org/patch/10590115/ >> >> But it didn't get the rest as it says "Untitled series #15763". >> Patchwork was timing out for me quite heavily so in that way I'm not >> surprised that patches are getting lost :( > > No, it's not patchwork - I didn't get the patches (except for #3) via > the list either. Ah, missed that as the ath10k list did get all the patches. But very good that patchwork was not to blame here. -- Kalle Valo ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2018-09-07 17:30 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2018-09-06 17:06 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu 2018-09-06 17:06 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu 2018-09-06 19:58 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg 2018-09-07 9:23 ` Arend van Spriel -- strict thread matches above, loose matches on Subject: below -- 2018-09-06 21:11 Pradeep Kumar Chitrapu 2018-09-06 1:01 Pradeep Kumar Chitrapu 2018-09-06 6:34 ` Johannes Berg 2018-09-06 15:15 ` Kalle Valo 2018-09-06 16:08 ` Johannes Berg 2018-09-06 16:18 ` Kalle Valo
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).