On Thu, 2010-12-16 at 04:27 -0800, Paul Stewart wrote: > > How so? After resume, mac80211 will invoke start(), add interfaces and > > stations back, and then invoke drv_config with all flags in "changed" > > set. Therefore, at this point, the device should be reset. Where's this > > not working? > > I haven't dug deep into it, but I can guess at a reason -- ath9k stores idle > state in two different places -- one is meant to mirror mac80211's state, > and the other one is internal, periodically computed from the state of all > wiphys. The ath9k version of the fix modified the > internal state without the mac80211 mirror. But at this point mac80211 doesn't care what the state is any more. > The ath9k config() routine > probably does nothing when called with "all changed" on resume because > in fact, if we suspend and resume when non-idle, nothing _has_ changed > from that perspective. Hmm, I still don't get it. The "idle just changed" flag is set -- and idle will actually be what it was at suspend time. If ath9k was simply setting its own idle state on stop(), and returning to what mac80211 says when it first configures the device after start(), what would the problem be? > I fear that unless ath9k gets changed more > substantially, it really does need to be informed of IDLE changes. I'd rather have ath9k change more than try to enforce this perfectly in mac80211. I still think that's brittle, and every little bug in a corner case will cause severe problems since it causes suspend/resume to fail. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
