* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ 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] 23+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 1:01 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH v3 1/3] cfg80211: support FTM responder configuration/statistics 2018-09-06 1:01 ` Pradeep Kumar Chitrapu (?) @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu -1 siblings, 0 replies; 23+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 1:01 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel, Johannes Berg Allow userspace to enable fine timing measurement responder functionality with configurable LCI/Civic parameters in AP mode. This can be done at AP start or changing beacon parameters. A new EXT_FEATURE flag is introduced for drivers to advertise the capability. Also nl80211 API support for retrieving statistics is added. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> --- v3: - fixed ftm responder disabled case to be not supported. - changed ftm_responder param from bool to s8. include/net/cfg80211.h | 66 +++++++++++++++++++++++ include/uapi/linux/nl80211.h | 81 ++++++++++++++++++++++++++++ net/wireless/nl80211.c | 124 +++++++++++++++++++++++++++++++++++++++++-- net/wireless/rdev-ops.h | 15 ++++++ net/wireless/trace.h | 44 +++++++++++++++ 5 files changed, 325 insertions(+), 5 deletions(-) diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h index 33c2a1d2a8d2..e54186d93c0c 100644 --- a/include/net/cfg80211.h +++ b/include/net/cfg80211.h @@ -775,6 +775,11 @@ struct cfg80211_crypto_settings { * @assocresp_ies_len: length of assocresp_ies in octets * @probe_resp_len: length of probe response template (@probe_resp) * @probe_resp: probe response template (AP mode only) + * @ftm_responder: enable FTM responder functionality + * @lci: LCI subelement content + * @civic: CIVIC subelement content + * @lci_len: LCI data length + * @civic_len: Civic data length */ struct cfg80211_beacon_data { const u8 *head, *tail; @@ -782,12 +787,17 @@ struct cfg80211_beacon_data { const u8 *proberesp_ies; const u8 *assocresp_ies; const u8 *probe_resp; + const u8 *lci; + const u8 *civic; + s8 ftm_responder; size_t head_len, tail_len; size_t beacon_ies_len; size_t proberesp_ies_len; size_t assocresp_ies_len; size_t probe_resp_len; + size_t lci_len; + size_t civic_len; }; struct mac_address { @@ -2795,6 +2805,55 @@ struct cfg80211_external_auth_params { }; /** + * cfg80211_ftm_responder_params - FTM responder parameters + * + * @lci: LCI subelement content + * @civic: CIVIC subelement content + * @lci_len: LCI data length + * @civic_len: Civic data length + */ +struct cfg80211_ftm_responder_params { + const u8 *lci; + const u8 *civic; + size_t lci_len; + size_t civic_len; +}; + +/** + * cfg80211_ftm_responder_stats - FTM responder statistics + * + * @filled: bitflag of flags using the bits of &enum nl80211_ftm_stats to + * indicate the relevant values in this struct for them + * @success_num: number of FTM sessions in which all frames were successfully + * answered + * @partial_num: number of FTM sessions in which part of frames were + * successfully answered + * @failed_num: number of failed FTM sessions + * @asap_num: number of ASAP FTM sessions + * @non_asap_num: number of non-ASAP FTM sessions + * @total_duration_ms: total sessions durations - gives an indication + * of how much time the responder was busy + * @unknown_triggers_num: number of unknown FTM triggers - triggers from + * initiators that didn't finish successfully the negotiation phase with + * the responder + * @reschedule_requests_num: number of FTM reschedule requests - initiator asks + * for a new scheduling although it already has scheduled FTM slot + * @out_of_window_triggers_num: total FTM triggers out of scheduled window + */ +struct cfg80211_ftm_responder_stats { + u32 filled; + u32 success_num; + u32 partial_num; + u32 failed_num; + u32 asap_num; + u32 non_asap_num; + u64 total_duration_ms; + u32 unknown_triggers_num; + u32 reschedule_requests_num; + u32 out_of_window_triggers_num; +}; + +/** * struct cfg80211_ops - backend description for wireless configuration * * This struct is registered by fullmac card drivers and/or wireless stacks @@ -3126,6 +3185,9 @@ struct cfg80211_external_auth_params { * * @tx_control_port: TX a control port frame (EAPoL). The noencrypt parameter * tells the driver that the frame should not be encrypted. + * + * @get_ftm_responder_stats: Retrieve FTM responder statistics, if available. + * Statistics should be cumulative, currently no way to reset is provided. */ struct cfg80211_ops { int (*suspend)(struct wiphy *wiphy, struct cfg80211_wowlan *wow); @@ -3431,6 +3493,10 @@ struct cfg80211_ops { const u8 *buf, size_t len, const u8 *dest, const __be16 proto, const bool noencrypt); + + int (*get_ftm_responder_stats)(struct wiphy *wiphy, + struct net_device *dev, + struct cfg80211_ftm_responder_stats *ftm_stats); }; /* diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h index 1766a12b231c..50c65e192414 100644 --- a/include/uapi/linux/nl80211.h +++ b/include/uapi/linux/nl80211.h @@ -1033,6 +1033,9 @@ * %NL80211_ATTR_CHANNEL_WIDTH,%NL80211_ATTR_NSS attributes with its * address(specified in %NL80211_ATTR_MAC). * + * @NL80211_CMD_GET_FTM_RESPONDER_STATS: Retrieve FTM responder statistics, in + * the %NL80211_ATTR_FTM_RESPONDER_STATS attribute. + * * @NL80211_CMD_MAX: highest used command number * @__NL80211_CMD_AFTER_LAST: internal use */ @@ -1245,6 +1248,8 @@ enum nl80211_commands { NL80211_CMD_CONTROL_PORT_FRAME, + NL80211_CMD_GET_FTM_RESPONDER_STATS, + /* add new commands above here */ /* used to define NL80211_CMD_MAX below */ @@ -2241,6 +2246,17 @@ enum nl80211_commands { * association request when used with NL80211_CMD_NEW_STATION). Can be set * only if %NL80211_STA_FLAG_WME is set. * + * @NL80211_ATTR_FTM_RESPONDER: attribute which user-space can include in + * %NL80211_CMD_START_AP or %NL80211_CMD_SET_BEACON to enable(1) + * fine timing measurement (FTM) responder functionality. + * @NL80211_ATTR_LCI: The content of Measurement Report Element (9.4.2.22 + * in 802.11-2016) with type 8 - LCI (9.4.2.22.10) + * @NL80211_ATTR_CIVIC: The content of Measurement Report Element (9.4.2.22 + * in 802.11-2016) with type 11 - Civic (Section 9.4.2.22.13) + * + * @NL80211_ATTR_FTM_RESPONDER_STATS: Nested attribute with FTM responder + * statistics, see &enum nl80211_ftm_responder_stats. + * * @NUM_NL80211_ATTR: total number of nl80211_attrs available * @NL80211_ATTR_MAX: highest attribute number currently defined * @__NL80211_ATTR_AFTER_LAST: internal use @@ -2682,6 +2698,12 @@ enum nl80211_attrs { NL80211_ATTR_HE_CAPABILITY, + NL80211_ATTR_FTM_RESPONDER, + NL80211_ATTR_LCI, + NL80211_ATTR_CIVIC, + + NL80211_ATTR_FTM_RESPONDER_STATS, + /* add attributes here, update the policy in nl80211.c */ __NL80211_ATTR_AFTER_LAST, @@ -5225,6 +5247,8 @@ enum nl80211_feature_flags { * @NL80211_EXT_FEATURE_SCAN_MIN_PREQ_CONTENT: Driver/device can omit all data * except for supported rates from the probe request content if requested * by the %NL80211_SCAN_FLAG_MIN_PREQ_CONTENT flag. + * @NL80211_EXT_FEATURE_ENABLE_FTM_RESPONDER: Driver supports enabling fine + * timing measurement responder role. * * @NUM_NL80211_EXT_FEATURES: number of extended features. * @MAX_NL80211_EXT_FEATURES: highest extended feature index. @@ -5263,6 +5287,7 @@ enum nl80211_ext_feature_index { NL80211_EXT_FEATURE_TXQS, NL80211_EXT_FEATURE_SCAN_RANDOM_SN, NL80211_EXT_FEATURE_SCAN_MIN_PREQ_CONTENT, + NL80211_EXT_FEATURE_ENABLE_FTM_RESPONDER, /* add new features before the definition below */ NUM_NL80211_EXT_FEATURES, @@ -5802,4 +5827,60 @@ enum nl80211_external_auth_action { NL80211_EXTERNAL_AUTH_ABORT, }; +/** + * enum nl80211_ftm_responder_state - fine timing measurement responder state + * @NL80211_FTM_RESP_DISABLED: FTM responder is disabled + * @NL80211_FTM_RESP_ENABLED: FTM responder is enabled + */ +enum nl80211_ftm_responder_state { + NL80211_FTM_RESP_DISABLED, + NL80211_FTM_RESP_ENABLED, +}; + +/* + * enum nl80211_ftm_responder_stats - FTM responder statistics + * + * These attribute types are used with %NL80211_ATTR_FTM_RESPONDER_STATS + * when getting FTM responder statistics. + * + * @__NL80211_FTM_STATS_INVALID: attribute number 0 is reserved + * @NL80211_FTM_STATS_SUCCESS_NUM: number of FTM sessions in which all frames + * were ssfully answered (u32) + * @NL80211_FTM_STATS_PARTIAL_NUM: number of FTM sessions in which part of the + * frames were successfully answered (u32) + * @NL80211_FTM_STATS_FAILED_NUM: number of failed FTM sessions (u32) + * @NL80211_FTM_STATS_ASAP_NUM: number of ASAP sessions (u32) + * @NL80211_FTM_STATS_NON_ASAP_NUM: number of non-ASAP sessions (u32) + * @NL80211_FTM_STATS_TOTAL_DURATION_MSEC: total sessions durations - gives an + * indication of how much time the responder was busy (u64, msec) + * @NL80211_FTM_STATS_UNKNOWN_TRIGGERS_NUM: number of unknown FTM triggers - + * triggers from initiators that didn't finish successfully the negotiation + * phase with the responder (u32) + * @NL80211_FTM_STATS_RESCHEDULE_REQUESTS_NUM: number of FTM reschedule requests + * - initiator asks for a new scheduling although it already has scheduled + * FTM slot (u32) + * @NL80211_FTM_STATS_OUT_OF_WINDOW_TRIGGERS_NUM: number of FTM triggers out of + * scheduled window (u32) + * @NL80211_FTM_STATS_PAD: used for padding, ignore + * @__NL80211_TXQ_ATTR_AFTER_LAST: Internal + * @NL80211_FTM_STATS_MAX: highest possible FTM responder stats attribute + */ +enum nl80211_ftm_responder_stats { + __NL80211_FTM_STATS_INVALID, + NL80211_FTM_STATS_SUCCESS_NUM, + NL80211_FTM_STATS_PARTIAL_NUM, + NL80211_FTM_STATS_FAILED_NUM, + NL80211_FTM_STATS_ASAP_NUM, + NL80211_FTM_STATS_NON_ASAP_NUM, + NL80211_FTM_STATS_TOTAL_DURATION_MSEC, + NL80211_FTM_STATS_UNKNOWN_TRIGGERS_NUM, + NL80211_FTM_STATS_RESCHEDULE_REQUESTS_NUM, + NL80211_FTM_STATS_OUT_OF_WINDOW_TRIGGERS_NUM, + NL80211_FTM_STATS_PAD, + + /* keep last */ + __NL80211_FTM_STATS_AFTER_LAST, + NL80211_FTM_STATS_MAX = __NL80211_FTM_STATS_AFTER_LAST - 1 +}; + #endif /* __LINUX_NL80211_H */ diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c index fbd0747a5a9d..62ed821c1f5e 100644 --- a/net/wireless/nl80211.c +++ b/net/wireless/nl80211.c @@ -430,6 +430,10 @@ enum nl80211_multicast_groups { [NL80211_ATTR_TXQ_QUANTUM] = { .type = NLA_U32 }, [NL80211_ATTR_HE_CAPABILITY] = { .type = NLA_BINARY, .len = NL80211_HE_MAX_CAPABILITY_LEN }, + + [NL80211_ATTR_FTM_RESPONDER] = { .type = NLA_U8 }, + [NL80211_ATTR_LCI] = { .type = NLA_BINARY }, + [NL80211_ATTR_CIVIC] = { .type = NLA_BINARY }, }; /* policy for the key attributes */ @@ -3997,7 +4001,8 @@ static int validate_beacon_tx_rate(struct cfg80211_registered_device *rdev, return 0; } -static int nl80211_parse_beacon(struct nlattr *attrs[], +static int nl80211_parse_beacon(struct cfg80211_registered_device *rdev, + struct nlattr *attrs[], struct cfg80211_beacon_data *bcn) { bool haveinfo = false; @@ -4051,6 +4056,38 @@ static int nl80211_parse_beacon(struct nlattr *attrs[], bcn->probe_resp_len = nla_len(attrs[NL80211_ATTR_PROBE_RESP]); } + if (attrs[NL80211_ATTR_FTM_RESPONDER]) { + bcn->ftm_responder = + nla_get_u8(attrs[NL80211_ATTR_FTM_RESPONDER]); + + if (bcn->ftm_responder != NL80211_FTM_RESP_DISABLED && + bcn->ftm_responder != NL80211_FTM_RESP_ENABLED) + return -EINVAL; + + if (bcn->ftm_responder == NL80211_FTM_RESP_DISABLED || + !wiphy_ext_feature_isset(&rdev->wiphy, + NL80211_EXT_FEATURE_ENABLE_FTM_RESPONDER)) + return -EOPNOTSUPP; + } else { + bcn->ftm_responder = -1; + } + + if (attrs[NL80211_ATTR_LCI]) { + if (nla_len(attrs[NL80211_ATTR_LCI]) > U8_MAX) + return -EINVAL; + + bcn->lci = nla_data(attrs[NL80211_ATTR_LCI]); + bcn->lci_len = nla_len(attrs[NL80211_ATTR_LCI]); + } + + if (attrs[NL80211_ATTR_CIVIC]) { + if (nla_len(attrs[NL80211_ATTR_CIVIC]) > U8_MAX) + return -EINVAL; + + bcn->civic = nla_data(attrs[NL80211_ATTR_CIVIC]); + bcn->civic_len = nla_len(attrs[NL80211_ATTR_CIVIC]); + } + return 0; } @@ -4194,7 +4231,7 @@ static int nl80211_start_ap(struct sk_buff *skb, struct genl_info *info) !info->attrs[NL80211_ATTR_BEACON_HEAD]) return -EINVAL; - err = nl80211_parse_beacon(info->attrs, ¶ms.beacon); + err = nl80211_parse_beacon(rdev, info->attrs, ¶ms.beacon); if (err) return err; @@ -4378,7 +4415,7 @@ static int nl80211_set_beacon(struct sk_buff *skb, struct genl_info *info) if (!wdev->beacon_interval) return -EINVAL; - err = nl80211_parse_beacon(info->attrs, ¶ms); + err = nl80211_parse_beacon(rdev, info->attrs, ¶ms); if (err) return err; @@ -7940,7 +7977,7 @@ static int nl80211_channel_switch(struct sk_buff *skb, struct genl_info *info) if (!need_new_beacon) goto skip_beacons; - err = nl80211_parse_beacon(info->attrs, ¶ms.beacon_after); + err = nl80211_parse_beacon(rdev, info->attrs, ¶ms.beacon_after); if (err) return err; @@ -7950,7 +7987,7 @@ static int nl80211_channel_switch(struct sk_buff *skb, struct genl_info *info) if (err) return err; - err = nl80211_parse_beacon(csa_attrs, ¶ms.beacon_csa); + err = nl80211_parse_beacon(rdev, csa_attrs, ¶ms.beacon_csa); if (err) return err; @@ -12990,6 +13027,76 @@ static int nl80211_tx_control_port(struct sk_buff *skb, struct genl_info *info) return err; } +static int nl80211_get_ftm_responder_stats(struct sk_buff *skb, + struct genl_info *info) +{ + struct cfg80211_registered_device *rdev = info->user_ptr[0]; + struct net_device *dev = info->user_ptr[1]; + struct wireless_dev *wdev = dev->ieee80211_ptr; + struct cfg80211_ftm_responder_stats ftm_stats = {}; + struct sk_buff *msg; + void *hdr; + struct nlattr *ftm_stats_attr; + int err; + + if (wdev->iftype != NL80211_IFTYPE_AP || !wdev->beacon_interval) + return -EOPNOTSUPP; + + err = rdev_get_ftm_responder_stats(rdev, dev, &ftm_stats); + if (err) + return err; + + if (!ftm_stats.filled) + return -ENODATA; + + msg = nlmsg_new(NLMSG_DEFAULT_SIZE, GFP_KERNEL); + if (!msg) + return -ENOMEM; + + hdr = nl80211hdr_put(msg, info->snd_portid, info->snd_seq, 0, + NL80211_CMD_GET_FTM_RESPONDER_STATS); + if (!hdr) + return -ENOBUFS; + + if (nla_put_u32(msg, NL80211_ATTR_IFINDEX, dev->ifindex)) + goto nla_put_failure; + + ftm_stats_attr = nla_nest_start(msg, NL80211_ATTR_FTM_RESPONDER_STATS); + if (!ftm_stats_attr) + goto nla_put_failure; + +#define SET_FTM(field, name, type) \ + do { if ((ftm_stats.filled & BIT(NL80211_FTM_STATS_ ## name)) && \ + nla_put_ ## type(msg, NL80211_FTM_STATS_ ## name, \ + ftm_stats.field)) \ + goto nla_put_failure; } while (0) +#define SET_FTM_U64(field, name) \ + do { if ((ftm_stats.filled & BIT(NL80211_FTM_STATS_ ## name)) && \ + nla_put_u64_64bit(msg, NL80211_FTM_STATS_ ## name, \ + ftm_stats.field, NL80211_FTM_STATS_PAD)) \ + goto nla_put_failure; } while (0) + + SET_FTM(success_num, SUCCESS_NUM, u32); + SET_FTM(partial_num, PARTIAL_NUM, u32); + SET_FTM(failed_num, FAILED_NUM, u32); + SET_FTM(asap_num, ASAP_NUM, u32); + SET_FTM(non_asap_num, NON_ASAP_NUM, u32); + SET_FTM_U64(total_duration_ms, TOTAL_DURATION_MSEC); + SET_FTM(unknown_triggers_num, UNKNOWN_TRIGGERS_NUM, u32); + SET_FTM(reschedule_requests_num, RESCHEDULE_REQUESTS_NUM, u32); + SET_FTM(out_of_window_triggers_num, OUT_OF_WINDOW_TRIGGERS_NUM, u32); +#undef SET_FTM + + nla_nest_end(msg, ftm_stats_attr); + + genlmsg_end(msg, hdr); + return genlmsg_reply(msg, info); + +nla_put_failure: + nlmsg_free(msg); + return -ENOBUFS; +} + #define NL80211_FLAG_NEED_WIPHY 0x01 #define NL80211_FLAG_NEED_NETDEV 0x02 #define NL80211_FLAG_NEED_RTNL 0x04 @@ -13901,6 +14008,13 @@ static void nl80211_post_doit(const struct genl_ops *ops, struct sk_buff *skb, .internal_flags = NL80211_FLAG_NEED_NETDEV_UP | NL80211_FLAG_NEED_RTNL, }, + { + .cmd = NL80211_CMD_GET_FTM_RESPONDER_STATS, + .doit = nl80211_get_ftm_responder_stats, + .policy = nl80211_policy, + .internal_flags = NL80211_FLAG_NEED_NETDEV | + NL80211_FLAG_NEED_RTNL, + }, }; static struct genl_family nl80211_fam __ro_after_init = { diff --git a/net/wireless/rdev-ops.h b/net/wireless/rdev-ops.h index 364f5d67f05b..51380b5c32f2 100644 --- a/net/wireless/rdev-ops.h +++ b/net/wireless/rdev-ops.h @@ -1232,4 +1232,19 @@ static inline int rdev_del_pmk(struct cfg80211_registered_device *rdev, return ret; } +static inline int +rdev_get_ftm_responder_stats(struct cfg80211_registered_device *rdev, + struct net_device *dev, + struct cfg80211_ftm_responder_stats *ftm_stats) +{ + int ret = -EOPNOTSUPP; + + trace_rdev_get_ftm_responder_stats(&rdev->wiphy, dev, ftm_stats); + if (rdev->ops->get_ftm_responder_stats) + ret = rdev->ops->get_ftm_responder_stats(&rdev->wiphy, dev, + ftm_stats); + trace_rdev_return_int(&rdev->wiphy, ret); + return ret; +} + #endif /* __CFG80211_RDEV_OPS */ diff --git a/net/wireless/trace.h b/net/wireless/trace.h index 5e7eec849200..89bd1f7aa7ed 100644 --- a/net/wireless/trace.h +++ b/net/wireless/trace.h @@ -3259,6 +3259,50 @@ ), TP_printk(WIPHY_PR_FMT ", " WDEV_PR_FMT, WIPHY_PR_ARG, WDEV_PR_ARG) ); + +TRACE_EVENT(rdev_get_ftm_responder_stats, + TP_PROTO(struct wiphy *wiphy, struct net_device *netdev, + struct cfg80211_ftm_responder_stats *ftm_stats), + + TP_ARGS(wiphy, netdev, ftm_stats), + + TP_STRUCT__entry( + WIPHY_ENTRY + NETDEV_ENTRY + __field(u64, timestamp) + __field(u32, success_num) + __field(u32, partial_num) + __field(u32, failed_num) + __field(u32, asap_num) + __field(u32, non_asap_num) + __field(u64, duration) + __field(u32, unknown_triggers) + __field(u32, reschedule) + __field(u32, out_of_window) + ), + + TP_fast_assign( + WIPHY_ASSIGN; + NETDEV_ASSIGN; + __entry->success_num = ftm_stats->success_num; + __entry->partial_num = ftm_stats->partial_num; + __entry->failed_num = ftm_stats->failed_num; + __entry->asap_num = ftm_stats->asap_num; + __entry->non_asap_num = ftm_stats->non_asap_num; + __entry->duration = ftm_stats->total_duration_ms; + __entry->unknown_triggers = ftm_stats->unknown_triggers_num; + __entry->reschedule = ftm_stats->reschedule_requests_num; + __entry->out_of_window = ftm_stats->out_of_window_triggers_num; + ), + + TP_printk(WIPHY_PR_FMT "Ftm responder stats: success %u, partial %u, " + "failed %u, asap %u, non asap %u, total duration %llu, unknown " + "triggers %u, rescheduled %u, out of window %u", WIPHY_PR_ARG, + __entry->success_num, __entry->partial_num, __entry->failed_num, + __entry->asap_num, __entry->non_asap_num, __entry->duration, + __entry->unknown_triggers, __entry->reschedule, + __entry->out_of_window) +); #endif /* !__RDEV_OPS_TRACE || TRACE_HEADER_MULTI_READ */ #undef TRACE_INCLUDE_PATH -- 1.9.1 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply related [flat|nested] 23+ messages in thread
* [PATCH v3 2/3] mac80211: support FTM responder configuration/statistics 2018-09-06 1:01 ` Pradeep Kumar Chitrapu @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu -1 siblings, 0 replies; 23+ 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, Johannes Berg New bss param ftm_responder is used to notify the driver to enable fine timing request (FTM) responder role in AP mode. Plumb the new cfg80211 API for FTM responder statistics through to the driver API in mac80211. Signed-off-by: David Spinadel <david.spinadel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> --- v3: - fixed ftm responder disabled case to be not supported. - changed ftm_responder param from bool to s8. include/net/mac80211.h | 13 ++++++++ net/mac80211/cfg.c | 84 +++++++++++++++++++++++++++++++++++++++++++++++ net/mac80211/driver-ops.h | 16 +++++++++ net/mac80211/trace.h | 23 +++++++++++++ net/mac80211/util.c | 3 ++ 5 files changed, 139 insertions(+) diff --git a/include/net/mac80211.h b/include/net/mac80211.h index e248f5fe5b19..d1589324d291 100644 --- a/include/net/mac80211.h +++ b/include/net/mac80211.h @@ -308,6 +308,8 @@ struct ieee80211_vif_chanctx_switch { * @BSS_CHANGED_KEEP_ALIVE: keep alive options (idle period or protected * keep alive) changed. * @BSS_CHANGED_MCAST_RATE: Multicast Rate setting changed for this interface + * @BSS_CHANGED_FTM_RESPONDER: fime timing reasurement request responder + * functionality changed for this BSS (AP mode). * */ enum ieee80211_bss_change { @@ -337,6 +339,7 @@ enum ieee80211_bss_change { BSS_CHANGED_MU_GROUPS = 1<<23, BSS_CHANGED_KEEP_ALIVE = 1<<24, BSS_CHANGED_MCAST_RATE = 1<<25, + BSS_CHANGED_FTM_RESPONDER = 1<<26, /* when adding here, make sure to change ieee80211_reconfig */ }; @@ -561,6 +564,9 @@ struct ieee80211_mu_group_data { * @protected_keep_alive: if set, indicates that the station should send an RSN * protected frame to the AP to reset the idle timer at the AP for the * station. + * @ftm_responder: whether to enable or disable fine timing measurement FTM + * responder functionality. + * @ftmr_params: configurable lci/civic parameter when enabling FTM responder. */ struct ieee80211_bss_conf { const u8 *bssid; @@ -611,6 +617,8 @@ struct ieee80211_bss_conf { bool allow_p2p_go_ps; u16 max_idle_period; bool protected_keep_alive; + s8 ftm_responder; + struct cfg80211_ftm_responder_params *ftmr_params; }; /** @@ -3546,6 +3554,8 @@ enum ieee80211_reconfig_type { * @del_nan_func: Remove a NAN function. The driver must call * ieee80211_nan_func_terminated() with * NL80211_NAN_FUNC_TERM_REASON_USER_REQUEST reason code upon removal. + * @get_ftm_responder_stats: Retrieve FTM responder statistics, if available. + * Statistics should be cumulative, currently no way to reset is provided. */ struct ieee80211_ops { void (*tx)(struct ieee80211_hw *hw, @@ -3828,6 +3838,9 @@ struct ieee80211_ops { void (*del_nan_func)(struct ieee80211_hw *hw, struct ieee80211_vif *vif, u8 instance_id); + int (*get_ftm_responder_stats)(struct ieee80211_hw *hw, + struct ieee80211_vif *vif, + struct cfg80211_ftm_responder_stats *ftm_stats); }; /** diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c index da1b85de7930..6f69e5bad17c 100644 --- a/net/mac80211/cfg.c +++ b/net/mac80211/cfg.c @@ -792,6 +792,48 @@ static int ieee80211_set_probe_resp(struct ieee80211_sub_if_data *sdata, return 0; } +static int ieee80211_set_ftm_responder_params( + struct ieee80211_sub_if_data *sdata, + const u8 *lci, size_t lci_len, + const u8 *civic, size_t civic_len) +{ + struct cfg80211_ftm_responder_params *new, *old; + struct ieee80211_bss_conf *bss_conf; + u8 *pos; + int len; + + if ((!lci || !lci_len) && (!civic || !civic_len)) + return 1; + + bss_conf = &sdata->vif.bss_conf; + old = bss_conf->ftmr_params; + len = lci_len + civic_len; + + new = kzalloc(sizeof(*new) + len, GFP_KERNEL); + if (!new) + return -ENOMEM; + + pos = (u8 *)(new + 1); + if (lci_len) { + new->lci_len = lci_len; + new->lci = pos; + memcpy(pos, lci, lci_len); + pos += lci_len; + } + + if (civic_len) { + new->civic_len = civic_len; + new->civic = pos; + memcpy(pos, civic, civic_len); + pos += civic_len; + } + + bss_conf->ftmr_params = new; + kfree(old); + + return 0; +} + static int ieee80211_assign_beacon(struct ieee80211_sub_if_data *sdata, struct cfg80211_beacon_data *params, const struct ieee80211_csa_settings *csa) @@ -865,6 +907,22 @@ static int ieee80211_assign_beacon(struct ieee80211_sub_if_data *sdata, if (err == 0) changed |= BSS_CHANGED_AP_PROBE_RESP; + if (params->ftm_responder != -1) { + sdata->vif.bss_conf.ftm_responder = params->ftm_responder; + err = ieee80211_set_ftm_responder_params(sdata, + params->lci, + params->lci_len, + params->civic, + params->civic_len); + + if (err < 0) + return err; + + changed |= BSS_CHANGED_FTM_RESPONDER; + } else { + sdata->vif.bss_conf.ftm_responder = -1; + } + rcu_assign_pointer(sdata->u.ap.beacon, new); if (old) @@ -2874,6 +2932,20 @@ static int ieee80211_start_radar_detection(struct wiphy *wiphy, memcpy(pos, beacon->probe_resp, beacon->probe_resp_len); pos += beacon->probe_resp_len; } + if (beacon->ftm_responder) + new_beacon->ftm_responder = beacon->ftm_responder; + if (beacon->lci) { + new_beacon->lci_len = beacon->lci_len; + new_beacon->lci = pos; + memcpy(pos, beacon->lci, beacon->lci_len); + pos += beacon->lci_len; + } + if (beacon->civic) { + new_beacon->civic_len = beacon->civic_len; + new_beacon->civic = pos; + memcpy(pos, beacon->civic, beacon->civic_len); + pos += beacon->civic_len; + } return new_beacon; } @@ -3764,6 +3836,17 @@ static int ieee80211_get_txq_stats(struct wiphy *wiphy, return ret; } +static int +ieee80211_get_ftm_responder_stats(struct wiphy *wiphy, + struct net_device *dev, + struct cfg80211_ftm_responder_stats *ftm_stats) +{ + struct ieee80211_local *local = wiphy_priv(wiphy); + struct ieee80211_sub_if_data *sdata = IEEE80211_DEV_TO_SUB_IF(dev); + + return drv_get_ftm_responder_stats(local, sdata, ftm_stats); +} + const struct cfg80211_ops mac80211_config_ops = { .add_virtual_intf = ieee80211_add_iface, .del_virtual_intf = ieee80211_del_iface, @@ -3858,4 +3941,5 @@ static int ieee80211_get_txq_stats(struct wiphy *wiphy, .set_multicast_to_unicast = ieee80211_set_multicast_to_unicast, .tx_control_port = ieee80211_tx_control_port, .get_txq_stats = ieee80211_get_txq_stats, + .get_ftm_responder_stats = ieee80211_get_ftm_responder_stats, }; diff --git a/net/mac80211/driver-ops.h b/net/mac80211/driver-ops.h index 8f6998091d26..16878f7310ab 100644 --- a/net/mac80211/driver-ops.h +++ b/net/mac80211/driver-ops.h @@ -1173,6 +1173,22 @@ static inline void drv_wake_tx_queue(struct ieee80211_local *local, local->ops->wake_tx_queue(&local->hw, &txq->txq); } +static inline int +drv_get_ftm_responder_stats(struct ieee80211_local *local, + struct ieee80211_sub_if_data *sdata, + struct cfg80211_ftm_responder_stats *ftm_stats) +{ + u32 ret = -EOPNOTSUPP; + + if (local->ops->get_ftm_responder_stats) + ret = local->ops->get_ftm_responder_stats(&local->hw, + &sdata->vif, + ftm_stats); + trace_drv_get_ftm_responder_stats(local, sdata, ftm_stats); + + return ret; +} + static inline int drv_start_nan(struct ieee80211_local *local, struct ieee80211_sub_if_data *sdata, struct cfg80211_nan_conf *conf) diff --git a/net/mac80211/trace.h b/net/mac80211/trace.h index 0ab69a1964f8..588c51a67c89 100644 --- a/net/mac80211/trace.h +++ b/net/mac80211/trace.h @@ -2600,6 +2600,29 @@ struct trace_switch_entry { ) ); +TRACE_EVENT(drv_get_ftm_responder_stats, + TP_PROTO(struct ieee80211_local *local, + struct ieee80211_sub_if_data *sdata, + struct cfg80211_ftm_responder_stats *ftm_stats), + + TP_ARGS(local, sdata, ftm_stats), + + TP_STRUCT__entry( + LOCAL_ENTRY + VIF_ENTRY + ), + + TP_fast_assign( + LOCAL_ASSIGN; + VIF_ASSIGN; + ), + + TP_printk( + LOCAL_PR_FMT VIF_PR_FMT, + LOCAL_PR_ARG, VIF_PR_ARG + ) +); + #endif /* !__MAC80211_DRIVER_TRACE || TRACE_HEADER_MULTI_READ */ #undef TRACE_INCLUDE_PATH diff --git a/net/mac80211/util.c b/net/mac80211/util.c index c195a0fdc0c0..26dd346ca006 100644 --- a/net/mac80211/util.c +++ b/net/mac80211/util.c @@ -2176,6 +2176,9 @@ int ieee80211_reconfig(struct ieee80211_local *local) case NL80211_IFTYPE_AP: changed |= BSS_CHANGED_SSID | BSS_CHANGED_P2P_PS; + if (sdata->vif.bss_conf.ftm_responder != -1) + changed |= BSS_CHANGED_FTM_RESPONDER; + if (sdata->vif.type == NL80211_IFTYPE_AP) { changed |= BSS_CHANGED_AP_PROBE_RESP; -- 1.9.1 ^ permalink raw reply related [flat|nested] 23+ messages in thread
* [PATCH v3 2/3] mac80211: support FTM responder configuration/statistics @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 1:01 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel, Johannes Berg New bss param ftm_responder is used to notify the driver to enable fine timing request (FTM) responder role in AP mode. Plumb the new cfg80211 API for FTM responder statistics through to the driver API in mac80211. Signed-off-by: David Spinadel <david.spinadel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org> --- v3: - fixed ftm responder disabled case to be not supported. - changed ftm_responder param from bool to s8. include/net/mac80211.h | 13 ++++++++ net/mac80211/cfg.c | 84 +++++++++++++++++++++++++++++++++++++++++++++++ net/mac80211/driver-ops.h | 16 +++++++++ net/mac80211/trace.h | 23 +++++++++++++ net/mac80211/util.c | 3 ++ 5 files changed, 139 insertions(+) diff --git a/include/net/mac80211.h b/include/net/mac80211.h index e248f5fe5b19..d1589324d291 100644 --- a/include/net/mac80211.h +++ b/include/net/mac80211.h @@ -308,6 +308,8 @@ struct ieee80211_vif_chanctx_switch { * @BSS_CHANGED_KEEP_ALIVE: keep alive options (idle period or protected * keep alive) changed. * @BSS_CHANGED_MCAST_RATE: Multicast Rate setting changed for this interface + * @BSS_CHANGED_FTM_RESPONDER: fime timing reasurement request responder + * functionality changed for this BSS (AP mode). * */ enum ieee80211_bss_change { @@ -337,6 +339,7 @@ enum ieee80211_bss_change { BSS_CHANGED_MU_GROUPS = 1<<23, BSS_CHANGED_KEEP_ALIVE = 1<<24, BSS_CHANGED_MCAST_RATE = 1<<25, + BSS_CHANGED_FTM_RESPONDER = 1<<26, /* when adding here, make sure to change ieee80211_reconfig */ }; @@ -561,6 +564,9 @@ struct ieee80211_mu_group_data { * @protected_keep_alive: if set, indicates that the station should send an RSN * protected frame to the AP to reset the idle timer at the AP for the * station. + * @ftm_responder: whether to enable or disable fine timing measurement FTM + * responder functionality. + * @ftmr_params: configurable lci/civic parameter when enabling FTM responder. */ struct ieee80211_bss_conf { const u8 *bssid; @@ -611,6 +617,8 @@ struct ieee80211_bss_conf { bool allow_p2p_go_ps; u16 max_idle_period; bool protected_keep_alive; + s8 ftm_responder; + struct cfg80211_ftm_responder_params *ftmr_params; }; /** @@ -3546,6 +3554,8 @@ enum ieee80211_reconfig_type { * @del_nan_func: Remove a NAN function. The driver must call * ieee80211_nan_func_terminated() with * NL80211_NAN_FUNC_TERM_REASON_USER_REQUEST reason code upon removal. + * @get_ftm_responder_stats: Retrieve FTM responder statistics, if available. + * Statistics should be cumulative, currently no way to reset is provided. */ struct ieee80211_ops { void (*tx)(struct ieee80211_hw *hw, @@ -3828,6 +3838,9 @@ struct ieee80211_ops { void (*del_nan_func)(struct ieee80211_hw *hw, struct ieee80211_vif *vif, u8 instance_id); + int (*get_ftm_responder_stats)(struct ieee80211_hw *hw, + struct ieee80211_vif *vif, + struct cfg80211_ftm_responder_stats *ftm_stats); }; /** diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c index da1b85de7930..6f69e5bad17c 100644 --- a/net/mac80211/cfg.c +++ b/net/mac80211/cfg.c @@ -792,6 +792,48 @@ static int ieee80211_set_probe_resp(struct ieee80211_sub_if_data *sdata, return 0; } +static int ieee80211_set_ftm_responder_params( + struct ieee80211_sub_if_data *sdata, + const u8 *lci, size_t lci_len, + const u8 *civic, size_t civic_len) +{ + struct cfg80211_ftm_responder_params *new, *old; + struct ieee80211_bss_conf *bss_conf; + u8 *pos; + int len; + + if ((!lci || !lci_len) && (!civic || !civic_len)) + return 1; + + bss_conf = &sdata->vif.bss_conf; + old = bss_conf->ftmr_params; + len = lci_len + civic_len; + + new = kzalloc(sizeof(*new) + len, GFP_KERNEL); + if (!new) + return -ENOMEM; + + pos = (u8 *)(new + 1); + if (lci_len) { + new->lci_len = lci_len; + new->lci = pos; + memcpy(pos, lci, lci_len); + pos += lci_len; + } + + if (civic_len) { + new->civic_len = civic_len; + new->civic = pos; + memcpy(pos, civic, civic_len); + pos += civic_len; + } + + bss_conf->ftmr_params = new; + kfree(old); + + return 0; +} + static int ieee80211_assign_beacon(struct ieee80211_sub_if_data *sdata, struct cfg80211_beacon_data *params, const struct ieee80211_csa_settings *csa) @@ -865,6 +907,22 @@ static int ieee80211_assign_beacon(struct ieee80211_sub_if_data *sdata, if (err == 0) changed |= BSS_CHANGED_AP_PROBE_RESP; + if (params->ftm_responder != -1) { + sdata->vif.bss_conf.ftm_responder = params->ftm_responder; + err = ieee80211_set_ftm_responder_params(sdata, + params->lci, + params->lci_len, + params->civic, + params->civic_len); + + if (err < 0) + return err; + + changed |= BSS_CHANGED_FTM_RESPONDER; + } else { + sdata->vif.bss_conf.ftm_responder = -1; + } + rcu_assign_pointer(sdata->u.ap.beacon, new); if (old) @@ -2874,6 +2932,20 @@ static int ieee80211_start_radar_detection(struct wiphy *wiphy, memcpy(pos, beacon->probe_resp, beacon->probe_resp_len); pos += beacon->probe_resp_len; } + if (beacon->ftm_responder) + new_beacon->ftm_responder = beacon->ftm_responder; + if (beacon->lci) { + new_beacon->lci_len = beacon->lci_len; + new_beacon->lci = pos; + memcpy(pos, beacon->lci, beacon->lci_len); + pos += beacon->lci_len; + } + if (beacon->civic) { + new_beacon->civic_len = beacon->civic_len; + new_beacon->civic = pos; + memcpy(pos, beacon->civic, beacon->civic_len); + pos += beacon->civic_len; + } return new_beacon; } @@ -3764,6 +3836,17 @@ static int ieee80211_get_txq_stats(struct wiphy *wiphy, return ret; } +static int +ieee80211_get_ftm_responder_stats(struct wiphy *wiphy, + struct net_device *dev, + struct cfg80211_ftm_responder_stats *ftm_stats) +{ + struct ieee80211_local *local = wiphy_priv(wiphy); + struct ieee80211_sub_if_data *sdata = IEEE80211_DEV_TO_SUB_IF(dev); + + return drv_get_ftm_responder_stats(local, sdata, ftm_stats); +} + const struct cfg80211_ops mac80211_config_ops = { .add_virtual_intf = ieee80211_add_iface, .del_virtual_intf = ieee80211_del_iface, @@ -3858,4 +3941,5 @@ static int ieee80211_get_txq_stats(struct wiphy *wiphy, .set_multicast_to_unicast = ieee80211_set_multicast_to_unicast, .tx_control_port = ieee80211_tx_control_port, .get_txq_stats = ieee80211_get_txq_stats, + .get_ftm_responder_stats = ieee80211_get_ftm_responder_stats, }; diff --git a/net/mac80211/driver-ops.h b/net/mac80211/driver-ops.h index 8f6998091d26..16878f7310ab 100644 --- a/net/mac80211/driver-ops.h +++ b/net/mac80211/driver-ops.h @@ -1173,6 +1173,22 @@ static inline void drv_wake_tx_queue(struct ieee80211_local *local, local->ops->wake_tx_queue(&local->hw, &txq->txq); } +static inline int +drv_get_ftm_responder_stats(struct ieee80211_local *local, + struct ieee80211_sub_if_data *sdata, + struct cfg80211_ftm_responder_stats *ftm_stats) +{ + u32 ret = -EOPNOTSUPP; + + if (local->ops->get_ftm_responder_stats) + ret = local->ops->get_ftm_responder_stats(&local->hw, + &sdata->vif, + ftm_stats); + trace_drv_get_ftm_responder_stats(local, sdata, ftm_stats); + + return ret; +} + static inline int drv_start_nan(struct ieee80211_local *local, struct ieee80211_sub_if_data *sdata, struct cfg80211_nan_conf *conf) diff --git a/net/mac80211/trace.h b/net/mac80211/trace.h index 0ab69a1964f8..588c51a67c89 100644 --- a/net/mac80211/trace.h +++ b/net/mac80211/trace.h @@ -2600,6 +2600,29 @@ struct trace_switch_entry { ) ); +TRACE_EVENT(drv_get_ftm_responder_stats, + TP_PROTO(struct ieee80211_local *local, + struct ieee80211_sub_if_data *sdata, + struct cfg80211_ftm_responder_stats *ftm_stats), + + TP_ARGS(local, sdata, ftm_stats), + + TP_STRUCT__entry( + LOCAL_ENTRY + VIF_ENTRY + ), + + TP_fast_assign( + LOCAL_ASSIGN; + VIF_ASSIGN; + ), + + TP_printk( + LOCAL_PR_FMT VIF_PR_FMT, + LOCAL_PR_ARG, VIF_PR_ARG + ) +); + #endif /* !__MAC80211_DRIVER_TRACE || TRACE_HEADER_MULTI_READ */ #undef TRACE_INCLUDE_PATH diff --git a/net/mac80211/util.c b/net/mac80211/util.c index c195a0fdc0c0..26dd346ca006 100644 --- a/net/mac80211/util.c +++ b/net/mac80211/util.c @@ -2176,6 +2176,9 @@ int ieee80211_reconfig(struct ieee80211_local *local) case NL80211_IFTYPE_AP: changed |= BSS_CHANGED_SSID | BSS_CHANGED_P2P_PS; + if (sdata->vif.bss_conf.ftm_responder != -1) + changed |= BSS_CHANGED_FTM_RESPONDER; + if (sdata->vif.type == NL80211_IFTYPE_AP) { changed |= BSS_CHANGED_AP_PROBE_RESP; -- 1.9.1 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply related [flat|nested] 23+ messages in thread
* [PATCH v3 3/3] ath10k: Add support to configure ftm responder role 2018-09-06 1:01 ` Pradeep Kumar Chitrapu @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu -1 siblings, 0 replies; 23+ 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 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] 23+ messages in thread
* [PATCH v3 3/3] ath10k: Add support to configure ftm responder role @ 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 1:01 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply related [flat|nested] 23+ 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 -1 siblings, 0 replies; 23+ 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] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 6:34 ` Johannes Berg 0 siblings, 0 replies; 23+ 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ 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 -1 siblings, 0 replies; 23+ 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] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 15:15 ` Kalle Valo 0 siblings, 0 replies; 23+ messages in thread From: Kalle Valo @ 2018-09-06 15:15 UTC (permalink / raw) To: Johannes Berg Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel, ath10k 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ 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 -1 siblings, 0 replies; 23+ 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] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 16:08 ` Johannes Berg 0 siblings, 0 replies; 23+ messages in thread From: Johannes Berg @ 2018-09-06 16:08 UTC (permalink / raw) To: Kalle Valo; +Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel, ath10k 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ 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 -1 siblings, 0 replies; 23+ 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] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 16:18 ` Kalle Valo 0 siblings, 0 replies; 23+ 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 17:06 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ 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] 23+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 17:06 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 17:06 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 17:06 ` Pradeep Kumar Chitrapu @ 2018-09-06 19:58 ` Johannes Berg -1 siblings, 0 replies; 23+ 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] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 19:58 ` Johannes Berg 0 siblings, 0 replies; 23+ 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 > _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics 2018-09-06 19:58 ` Johannes Berg @ 2018-09-07 9:23 ` Arend van Spriel -1 siblings, 0 replies; 23+ 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] 23+ messages in thread
* Re: [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-07 9:23 ` Arend van Spriel 0 siblings, 0 replies; 23+ 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 21:11 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ 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] 23+ messages in thread
* [PATCH v3 0/3] support ftm responder configuration/statistics @ 2018-09-06 21:11 ` Pradeep Kumar Chitrapu 0 siblings, 0 replies; 23+ messages in thread From: Pradeep Kumar Chitrapu @ 2018-09-06 21:11 UTC (permalink / raw) To: Johannes Berg, ath10k Cc: Pradeep Kumar Chitrapu, linux-wireless, david.spinadel 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 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2018-09-07 21:39 UTC | newest] Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-09-06 1:01 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 2018-09-06 1:01 ` [PATCH v3 1/3] cfg80211: support FTM " Pradeep Kumar Chitrapu 2018-09-06 1:01 ` [PATCH v3 2/3] mac80211: " Pradeep Kumar Chitrapu 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 2018-09-06 1:01 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu 2018-09-06 1:01 ` Pradeep Kumar Chitrapu 2018-09-06 6:34 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg 2018-09-06 6:34 ` Johannes Berg 2018-09-06 15:15 ` Kalle Valo 2018-09-06 15:15 ` Kalle Valo 2018-09-06 16:08 ` Johannes Berg 2018-09-06 16:08 ` Johannes Berg 2018-09-06 16:18 ` Kalle Valo 2018-09-06 16:18 ` Kalle Valo 2018-09-06 17:06 Pradeep Kumar Chitrapu 2018-09-06 17:06 ` Pradeep Kumar Chitrapu 2018-09-06 19:58 ` Johannes Berg 2018-09-06 19:58 ` Johannes Berg 2018-09-07 9:23 ` Arend van Spriel 2018-09-07 9:23 ` Arend van Spriel 2018-09-06 21:11 Pradeep Kumar Chitrapu 2018-09-06 21:11 ` Pradeep Kumar Chitrapu
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.