On Tuesday, August 23, 2011, Mark Brown wrote: > On Sun, Aug 21, 2011 at 08:05:53PM +0200, Rafael J. Wysocki wrote: > > On Sunday, August 21, 2011, Mark Brown wrote: > > > > I don't understand why the driver would need to know what situation it's > > > in. I'd been working on the basis that the idea was that the driver > > > said what the constraints it has are and then some code with a more > > > system wide view would make the actual decisions for things outside the > > > driver domian. > > > That's correct, but in order to figure out a "sensible default" > > the driver generally would need to know what the expectations with > > respect to it are. Otherwise it can very well generate a random > > number and use that. > > Right, but I'd expect that should be something that the driver can > generally do based on knowledge of what it needs to deliver to its > users. It doesn't need to be tunable to that - for example, input > devices will have a reasonable idea of the response time needed to > deliver interactive performance. If it's really got no idea then > hopefully not providng any constraints will do something sensible. Perhaps. Still, that requires some policy to be put into drivers, which I don't think is entirely correct. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
