On Tue, Sep 8, 2015 at 9:35 AM, Oliver Neukum <oneukum@xxxxxxxx> wrote: > On Tue, 2015-09-08 at 01:10 +0000, Tirdea, Irina wrote: [cut] >> this would work except for adding a sysfs attribute that would trigger >> a runtime suspend while ignoring usage count. Would that be a >> better direction? > > No. If we want this at all, we need a new callback to notify drivers > that user space is temporarily uninterested in a device. And the reverse > of course. > The power model is good. We must not assume that devices can be > suspended at will. If we do this at all, we ought to see it as giving > strong hints to drivers when a device can be considered idle. This is a good summary in my view. The only thing we can add, realistically, is an interface for user space to "kick" drivers to check if the devices they handle may be suspended at this point (or to run their ->runtime_idle callbacks IOW). That would be quite similar to autosuspend except that the "kick" will come from user space rather than from a timer function in the kernel. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
