From: Paul Stewart <pstew@chromium.org>
To: linux-wireless@vger.kernel.org
Subject: [PATCH] nl80211: Provide TDLS link state
Date: Tue, 20 May 2014 13:27:16 -0700 [thread overview]
Message-ID: <20140520203657.2C281E0300@pstew.mtv.corp.google.com> (raw)
Provide a method to query TDLS state in drivers that use the
NL80211_CMD_TDLS_OPER method for link setup.
Signed-off-by: Paul Stewart <pstew@chromium.org>
---
include/uapi/linux/nl80211.h | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h
index 9922b9b..4f163f9 100644
--- a/include/uapi/linux/nl80211.h
+++ b/include/uapi/linux/nl80211.h
@@ -3866,6 +3866,7 @@ enum nl80211_pmksa_candidate_attr {
* @NL80211_TDLS_TEARDOWN: Teardown a TDLS link which is already established
* @NL80211_TDLS_ENABLE_LINK: Enable TDLS link
* @NL80211_TDLS_DISABLE_LINK: Disable TDLS link
+ * @NL80211_TDLS_QUERY_LINK: Query TDLS link status
*/
enum nl80211_tdls_operation {
NL80211_TDLS_DISCOVERY_REQ,
@@ -3873,6 +3874,19 @@ enum nl80211_tdls_operation {
NL80211_TDLS_TEARDOWN,
NL80211_TDLS_ENABLE_LINK,
NL80211_TDLS_DISABLE_LINK,
+ NL80211_TDLS_QUERY_LINK,
+};
+
+/**
+ * enum nl80211_tdls_link_state - values returned fo %NL80211_TDLS_QUERY_LINK
+ * @NL80211_TDLS_LINK_STATE_UNKNOWN: Nothing is known about this peer
+ * @NL80211_TDLS_LINK_STATE_UNCONNECTED: TDLS link is not setup to peer
+ * @NL80211_TDLS_LINK_STATE_CONNECTED: TDLS link is setup to peer
+ */
+enum nl80211_tdls_link_state {
+ NL80211_TDLS_LINK_STATE_UNKNOWN,
+ NL80211_TDLS_LINK_STATE_UNCONNECTED,
+ NL80211_TDLS_LINK_STATE_CONNECTED,
};
/*
--
1.9.1.423.g4596e3a
next reply other threads:[~2014-05-20 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 20:27 Paul Stewart [this message]
2014-05-20 21:54 ` [PATCH] nl80211: Provide TDLS link state Luca Coelho
2014-05-20 20:27 ` [PATCHv2] " Paul Stewart
2014-05-21 10:41 ` Johannes Berg
2014-05-21 16:17 ` Paul Stewart
2014-05-21 19:59 ` Johannes Berg
2014-05-21 20:19 ` Paul Stewart
2014-05-22 6:56 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140520203657.2C281E0300@pstew.mtv.corp.google.com \
--to=pstew@chromium.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox