From: Dedy Lansky <dlansky@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dedy Lansky <dlansky@codeaurora.org>,
linux-wireless@vger.kernel.org,
Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Subject: [PATCH] nl80211: add new scan flag to indicate P2P search
Date: Sun, 25 Jan 2015 14:30:52 +0200 [thread overview]
Message-ID: <1422189052-25602-1-git-send-email-dlansky@codeaurora.org> (raw)
Scan request (NL80211_CMD_TRIGGER_SCAN) is used for triggering both scan
and P2P search.
At driver/firmware layer, scan and P2P search might be handled differently.
Add new scan flag to indicate P2P search. This flag can be used
by applications (e.g. wpa_supplicant) to explicitly request P2P search.
Signed-off-by: Dedy Lansky <dlansky@codeaurora.org>
---
include/uapi/linux/nl80211.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h
index f52797a..d7d07d6 100644
--- a/include/uapi/linux/nl80211.h
+++ b/include/uapi/linux/nl80211.h
@@ -4383,12 +4383,14 @@ enum nl80211_connect_failed_reason {
* locally administered 1, multicast 0) is assumed.
* This flag must not be requested when the feature isn't supported, check
* the nl80211 feature flags for the device.
+ * @NL80211_SCAN_FLAG_P2P: indicate this is a request for a P2P search
*/
enum nl80211_scan_flags {
NL80211_SCAN_FLAG_LOW_PRIORITY = 1<<0,
NL80211_SCAN_FLAG_FLUSH = 1<<1,
NL80211_SCAN_FLAG_AP = 1<<2,
NL80211_SCAN_FLAG_RANDOM_ADDR = 1<<3,
+ NL80211_SCAN_FLAG_P2P = 1<<4,
};
/**
--
1.9.1
next reply other threads:[~2015-01-25 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 12:30 Dedy Lansky [this message]
2015-01-26 8:27 ` [PATCH] nl80211: add new scan flag to indicate P2P search Johannes Berg
2015-01-26 9:58 ` Jouni Malinen
2015-01-29 7:01 ` Dedy Lansky
2015-02-23 16:07 ` 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=1422189052-25602-1-git-send-email-dlansky@codeaurora.org \
--to=dlansky@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=qca_vkondrat@qca.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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).