On Tue, Mar 22, 2011 at 5:20 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > I think what we should do instead is this: > 1) Add suspend/resume ops instead of going through stop/start and all > the deconfiguration / reconfiguration (of course keep all the > previous logic for drivers that don't implement suspend.) > > 2) Implement more iterators / accessors to allow drivers to get access > to more information. Some of that might not be necessary since at > resume in some cases the device might just go and request a restart, > but in other cases this might be necessary to simplify/avoid book- > keeping in drivers. > > Adding such APIs would allow drivers to be more in control of what > happens at suspend, which given the complexity of how this might work, > with configuring the driver etc. > > Thoughts? > i agree. new suspend/resume ops sounds like the right thing to do. i'm not sure why i didn't add them in the first place. :) Eliad. -- 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
