From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] mac80211: inform the low level driver about events in mac80211
Date: Mon, 30 Mar 2015 10:17:44 +0200 [thread overview]
Message-ID: <1427703464.26117.2.camel@sipsolutions.net> (raw)
In-Reply-To: <1426541017-10516-1-git-send-email-emmanuel.grumbach@intel.com>
On Mon, 2015-03-16 at 23:23 +0200, Emmanuel Grumbach wrote:
> This can be useful to know what is happening in mac80211
> from the low level driver without guessing from mac80211's
> callbacks.
> This can be used for error detection (too many deauths)
> and trigger recovery / debug flows based on that
> information.
> Another possibility is to change parameters that are not
> controlled by mac80211 based on this. For example, after
> a few association failures, a device may change its BT
> Coexist scheme or modify the time sharing between its
> vifs.
>
> I use these patches in iwlwifi for debug only (currently).
> This allows me to collect firmware debug data upon
> authentication failure / deauth Rx etc...
Applied all four.
johannes
prev parent reply other threads:[~2015-03-30 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 21:23 [PATCH 0/4] mac80211: inform the low level driver about events in mac80211 Emmanuel Grumbach
2015-03-16 21:23 ` [PATCH 1/4] mac80211: convert rssi_callback() to event_callback() Emmanuel Grumbach
2015-03-16 21:23 ` [PATCH 2/4] mac80211: notify the driver about authentication status Emmanuel Grumbach
2015-03-16 21:23 ` [PATCH 3/4] mac80211: notify the driver about association status Emmanuel Grumbach
2015-03-16 21:23 ` [PATCH 4/4] mac80211: notify the driver about deauth Emmanuel Grumbach
2015-03-30 8:17 ` Johannes Berg [this message]
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=1427703464.26117.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.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 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.