From: Luciano Coelho <luciano.coelho@nokia.com>
To: "Oikarinen Juuso (Nokia-D/Tampere)" <juuso.oikarinen@nokia.com>
Cc: ext Johannes Berg <johannes@sipsolutions.net>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 21/31] wl1271: prevent power save entry while not associated
Date: Fri, 11 Dec 2009 15:15:54 +0200 [thread overview]
Message-ID: <4B22460A.9060804@nokia.com> (raw)
In-Reply-To: <1260533355.2689.45.camel@wimaxnb.ntc.nokia.com>
Oikarinen Juuso (Nokia-D/Tampere) wrote:
> Hi,
>
> Unfortunately I haven't had the time to investigate this further, but
> for me it did happen after getting de-authenticated from an AP and
> attempting to re-authenticate. While re-authenticating, mac80211
> appeared to request going into power save after transmitting the
> corresponding control messages, preventing the re-authentication from
> succeeding.
>
> My assumption is, that the dynamic power save mechanism is somehow
> getting triggered from the control message exchange - but, as I said, I
> cannot be sure at this point.
>
> -Juuso
>
> On Fri, 2009-12-11 at 12:53 +0100, ext Johannes Berg wrote:
>> On Fri, 2009-12-11 at 13:41 +0200, Luciano Coelho wrote:
>>> From: Juuso Oikarinen <juuso.oikarinen@nokia.com>
>>>
>>> The mac80211 sometimes requests power save entry while not associated - this
>>> will cause problems, so prevent it if not associated. Go to powersave once
>>> association is complete.
>> Does it? It's not supposed to, and I imagine that causing trouble with
>> other drivers too. Do you know how that happens?
I'll keep this patch for now. Later, if the issue with mac80211 is found and
fixed, we can remove the code if needed.
--
Cheers,
Luca.
next prev parent reply other threads:[~2009-12-11 13:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 11:40 [PATCH 00/31] wl1271: patches for wk50 Luciano Coelho
2009-12-11 11:40 ` [PATCH 01/31] wl1271: updated radio parameters structure for newer firmwares Luciano Coelho
2009-12-11 11:40 ` [PATCH 02/31] wl1271: updated general " Luciano Coelho
2009-12-11 11:40 ` [PATCH 03/31] wl1271: update radio and general parameters values Luciano Coelho
2009-12-11 11:40 ` [PATCH 04/31] wl1271: added radio parameters configuration values newer firmwares Luciano Coelho
2009-12-11 11:40 ` [PATCH 05/31] wl1271: use join command with dummy BSSID Luciano Coelho
2009-12-11 11:40 ` [PATCH 06/31] wl1271: remove workaround for disconnection Luciano Coelho
2009-12-11 11:40 ` [PATCH 07/31] wl1271: fix tx power setting function Luciano Coelho
2009-12-11 11:51 ` Johannes Berg
2009-12-11 12:16 ` Luciano Coelho
2009-12-11 11:40 ` [PATCH 08/31] wl1271: check result code from the join command Luciano Coelho
2009-12-11 11:41 ` [PATCH 09/31] wl1271: set null data template when BSSID is known Luciano Coelho
2009-12-11 11:41 ` [PATCH 10/31] wl1271: use the correct macro when setting the basic rates Luciano Coelho
2009-12-11 11:41 ` [PATCH 11/31] wl1271: implement dco itrim parameters setting Luciano Coelho
2009-12-11 11:41 ` [PATCH 12/31] wl1271: fix one typo in the rx_rssi_and_proc_compens values Luciano Coelho
2009-12-11 11:41 ` [PATCH 13/31] wl1271: add gpio_power file in debugfs to power the chip on and off Luciano Coelho
2009-12-11 11:41 ` [PATCH 14/31] wl1271: upload only the first 468 bytes from the NVS file Luciano Coelho
2009-12-11 11:41 ` [PATCH 15/31] wl1271: some new configuration values according to new reference Luciano Coelho
2009-12-11 11:41 ` [PATCH 16/31] wl1271: use channel 1 when configuring the data path Luciano Coelho
2009-12-11 11:41 ` [PATCH 17/31] wl1271: Configure smart-reflex paramter values Luciano Coelho
2009-12-11 11:41 ` [PATCH 18/31] wl1271: Remove smart reflex ACX Luciano Coelho
2009-12-11 11:41 ` [PATCH 19/31] wl1271: Use slow rates for association messages Luciano Coelho
2009-12-11 11:41 ` [PATCH 20/31] wl1271: Fix event acknowledging functionality Luciano Coelho
2009-12-11 11:41 ` [PATCH 21/31] wl1271: prevent power save entry while not associated Luciano Coelho
2009-12-11 11:53 ` Johannes Berg
2009-12-11 12:09 ` Juuso Oikarinen
2009-12-11 13:15 ` Luciano Coelho [this message]
2009-12-12 21:05 ` Kalle Valo
2009-12-11 11:41 ` [PATCH 22/31] wl1271: Implement chipset boot retry Luciano Coelho
2009-12-11 11:41 ` [PATCH 23/31] wl1271: Add pre-power-on sleep Luciano Coelho
2009-12-11 11:41 ` [PATCH 24/31] wl1271: Remove beacon-loss-ind from PSM entry failure handling Luciano Coelho
2009-12-11 11:41 ` [PATCH 25/31] wl1271: Add rudimentary ad-hoc support Luciano Coelho
2009-12-11 11:41 ` [PATCH 26/31] wl1271: Change rates configured for templates Luciano Coelho
2009-12-11 11:41 ` [PATCH 27/31] wl1271: Fix supported rate management Luciano Coelho
2009-12-11 11:41 ` [PATCH 28/31] wl1271: Change booleans in struct wl1271 into a flags bitmask Luciano Coelho
2009-12-11 11:41 ` [PATCH 29/31] wl1271: Add support for acx_pm_config Luciano Coelho
2009-12-11 11:41 ` [PATCH 30/31] wl1271: Check vif for NULL when indicating beacon-loss Luciano Coelho
2009-12-11 11:41 ` [PATCH 31/31] wl1271: Prevent performing "join" before association Luciano Coelho
2009-12-11 11:54 ` [PATCH 00/31] wl1271: patches for wk50 Johannes Berg
2009-12-11 13:22 ` Luciano Coelho
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=4B22460A.9060804@nokia.com \
--to=luciano.coelho@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=juuso.oikarinen@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).