| Message ID | 1393376982-28276-4-git-send-email-mcgrof@do-not-panic.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Wed, Feb 26, 2014 at 3:09 AM, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote: > This adds a trigger to review any pending regulatory > requests whenever an 802.11 device interface is brought > down or up. We use this as an opportunistic trigger > for checking the regulatory work queues as otherwise > they they're only checked upon an initial regulatory > request or when beacon hints are found. > > This opportunistic mechanism can be used to trigger > kicking the queues regulatory queues at any time from > userspace without having to change the regulatory state. > > A timer just waiting upon init is not that appropriate > as when it should be triggered will depend on systems, > a much better approach is to use and add opportunistic > triggers. The interface coming up is typically a good > indicator that filesystems have been mounted since > firmware is required for some devices. > > Reported-by: Sander Eikelenboom <linux@eikelenboom.it> > Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com> > --- > net/wireless/reg.h | 1 + > 1 file changed, 1 insertion(+) Seems the actual patch is missing? Arik -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Feb 27, 2014 at 5:21 AM, Arik Nemtsov <arik@wizery.com> wrote:
> Seems the actual patch is missing?
Yeah sorry I sent out a v3.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Feb 27, 2014 at 7:20 PM, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote: > On Thu, Feb 27, 2014 at 5:21 AM, Arik Nemtsov <arik@wizery.com> wrote: >> Seems the actual patch is missing? > > Yeah sorry I sent out a v3. Yea finally noticed. Thanks. Arik -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/net/wireless/reg.h b/net/wireless/reg.h index 37c180d..51912b3 100644 --- a/net/wireless/reg.h +++ b/net/wireless/reg.h @@ -37,6 +37,7 @@ unsigned int reg_get_max_bandwidth(const struct ieee80211_regdomain *rd, const struct ieee80211_reg_rule *rule); bool reg_last_request_cell_base(void); +void reg_process_pending_work(void); /** * regulatory_hint_found_beacon - hints a beacon was found on a channel
This adds a trigger to review any pending regulatory requests whenever an 802.11 device interface is brought down or up. We use this as an opportunistic trigger for checking the regulatory work queues as otherwise they they're only checked upon an initial regulatory request or when beacon hints are found. This opportunistic mechanism can be used to trigger kicking the queues regulatory queues at any time from userspace without having to change the regulatory state. A timer just waiting upon init is not that appropriate as when it should be triggered will depend on systems, a much better approach is to use and add opportunistic triggers. The interface coming up is typically a good indicator that filesystems have been mounted since firmware is required for some devices. Reported-by: Sander Eikelenboom <linux@eikelenboom.it> Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com> --- net/wireless/reg.h | 1 + 1 file changed, 1 insertion(+)