On Saturday, August 20, 2011, Mark Brown wrote: > On Sat, Aug 20, 2011 at 06:34:34PM +0200, Rafael J. Wysocki wrote: > > On Saturday, August 20, 2011, Mark Brown wrote: > > > > Any sort of media streaming would be an obvious example - the > > > application picks the amount of data it buffers and how often it's > > > notified of progress depending on the usage which then controls how > > > quickly the system needs to handle things. > > > Well, what about other types of devices? > > Other than the input case (which is a latency issue - there's two > components, one is how much data is delivered for things like > touchscreens which stream and the other is how quickly the first data is > delivered) nothing immediately springs to mind but this may just be a > product of what I'm most familiar with. I don't really see this as a > problem, for a lot of devices it's probably the case that the device can > figure out something sensible to do without any help.
I guess you mean the driver here and I'm not really sure it can. For instance, the driver may not know what configuration it works in, e.g. is there a power domain or a hierarchy of those and how much time it takes to power them all down and up and what the power break even is. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
