From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V7 1/3] cfg80211: introduce critical protocol indication from user-space
Date: Mon, 22 Apr 2013 15:49:48 +0200 [thread overview]
Message-ID: <1366638588.8637.15.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1366292942-21038-1-git-send-email-arend@broadcom.com>
On Thu, 2013-04-18 at 15:49 +0200, Arend van Spriel wrote:
> Some protocols need a more reliable connection to complete
> successful in reasonable time. This patch adds a user-space
> API to indicate the wireless driver that a critical protocol
> is about to commence and when it is done, using nl80211 primitives
> NL80211_CMD_CRIT_PROTOCOL_START and NL80211_CRIT_PROTOCOL_STOP.
>
> There can be only on critical protocol session started per
> registered cfg80211 device.
>
> The driver can support this by implementing the cfg80211 callbacks
> .crit_proto_start() and .crit_proto_stop(). Examples of protocols
> that can benefit from this are DHCP, EAPOL, APIPA. Exactly how the
> link can/should be made more reliable is up to the driver. Things
> to consider are avoid scanning, no multi-channel operations, and
> alter coexistence schemes.
Applied.
johannes
next prev parent reply other threads:[~2013-04-22 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 13:49 [PATCH V7 1/3] cfg80211: introduce critical protocol indication from user-space Arend van Spriel
2013-04-18 13:49 ` [PATCH 2/3] brcmfmac: allow scanning to be suppressed in the driver Arend van Spriel
2013-04-18 13:49 ` [PATCH 3/3] brcmfmac: support critical protocol API for DHCP Arend van Spriel
2013-04-22 13:49 ` Johannes Berg [this message]
2013-04-23 7:31 ` [PATCH V7 1/3] cfg80211: introduce critical protocol indication from user-space Arend van Spriel
2013-04-23 7:48 ` Johannes Berg
2013-05-23 18:30 ` Dan Williams
2013-05-24 16:43 ` Arend van Spriel
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=1366638588.8637.15.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).