On Fri, Oct 09, 2009 at 07:10:12PM +0100, Mark Brown wrote: > On Fri, Oct 09, 2009 at 09:27:18AM -0700, Dmitry Torokhov wrote: > > On Fri, Oct 09, 2009 at 01:12:02PM +0100, Mark Brown wrote: > > > > It'd be really good to have this control exposed to user space in a > > > standard fashion. > > > I'll take the patches. > > Yes, I was planning on doing some - I've got a touchscreen driver to do > soon and was hoping to have time to look at this while working on that > driver. > > > > Other devices that generate constant data rates like > > > touchscreens could also benefit from it, changing their output rate > > > depending on the needs of user space to give a power saving. > > > Not sure if this belongs to the input core as such. It seems that what > > you want here is dynamic power-management which works on the level below > > input core (individual devices on particular buses). > > It definitely needs to be implemented in the drivers but they need to > present an interface to userspace which seems best placed in the core to > factor out code and help make sure that the interface is standardised. It seems to me that this kind of functionality belongs to PM core. Userspace probably does not really care about output rate and other details but rather wants to putsome devices into a low power mode in general. -- Dmitry -- 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
