On Sat, 7 Mar 2015, Rafael J. Wysocki wrote: > > > Well right now it's using threaded irq, and I'd like to get rid of > > > I'll verify again, but I believe the issue was that without doing > > > mark_last_busy here the device falls back asleep right away. > > > That probably should be fixed in pm_runtime in general if that's > > > the case. > > > > It's up to the subsystem to handle this. For example, the USB > > subsystem's runtime-resume routine calls pm_runtime_mark_last_busy. > > I'm wondering, though, if there's any reason for us to avoid updating > power.last_busy in rpm_resume(). > > If I was a driver writer, I'd expect the core to do that for me quite frankly. In theory, you might want to wake up a device to perform some very limited operation (like reading an internal register) and then put it back into suspend very quickly, without waiting for the autosuspend delay to elapse. Apart from that, I can't think of any reason not to update last_busy in rpm_resume. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
