On Sun, 03 Aug 2008, Tomas Winkler wrote: > > I think that handler was added by Dmitry, but I see no real reason for > > issuing the BLOCK event during suspend. However the handlers should > > be used to prevent state changes to drivers after they have been suspended. > > Sounds reasonable. Added to TODO list to remove the toggle_radio() calls on the suspend path. Note that rfkill will still call the toggle_radio() callback on the resume path with whatever state the radio was before suspend, because we want the state set by the user to be preserved across sleeps of any sort, and that's not the wireless driver's business to ensure, but rather, rfkill's. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
