On Saturday, December 18, 2010, Ohad Ben-Cohen wrote: > Hi Alan, > > Sorry for the belated response, > > On Sat, Dec 11, 2010 at 4:50 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > >> Think of a device which you have no way to reset other than powering > >> it down and up again. > >> > >> If that device is managed by runtime PM, the only way to do that is by > >> using put_sync() followed by a get_sync(). Sure, if someone else > >> increased the usage_count of that device this won't work, but then of > >> course it means that the driver is not using runtime PM correctly. > > > > Not so. Even if a driver uses runtime PM correctly, there will still > > be times when someone else has increased the usage_count. This happens > > during probing and during system resume, for example. > > I'm aware of these two examples; normally we're good with them since > during probing we're not toggling the power, and during suspend/resume > the SDIO core is responsible for manipulating the power (and it does > so directly). Are there (or do you think there will be) additional > examples where this can happen ? > > But this leads me to a real problem which we have encountered. > > During system suspend, our driver is asked (by mac80211's suspend > handler) to power off its device. When this happens, the driver has no > idea that the system is suspending - regular driver code (responsible > to remove the wlan interface and stop the device) is being called. That's where the problem is. If there's a difference, from the driver's point of view, between suspend and some other operation, there should be a way to tell the driver what case it actually is dealing with. BTW, what would you do in that case if the runtime PM of the device were disabled by user space by writing "on" to the device's /sys/devices/.../power/control file? Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
