Hi, On Friday, September 30, 2011, Jean Pihet wrote: > Hi, > > Here is a patch which adds a PM_QOS_MEMORY_THROUGHPUT class to the PM > QoS framework. The idea is to provide a memory or SDMA throughput > constraints class, which can be applied to the low level platform code > using the callback notification mechanism and also a MISC /dev entry > for the constraints from user space. > > The first user of this class of constraints is the OMAP platform. The > aggregated constraint is fed to the DVFS layer in order to control the > main interconnect (L3) frequency and so the memory bandwidth. This > comes as a subsequent patch. > > This patch is RFC since more throughput constraints could be added in > the future, in order to control more clocks in the system. Is it worth > adding a class for every new subsystem to control? > > What do you think? > > The patch follows asap as a reply to this message. It applies on > Rafael' latest linux-pm tree, cf. > https://github.com/rjwysocki/linux-pm/commits/pm-qos. Quite frankly, I'm not very fond of creating more special device files for PM QoS at this point. It would be nice if you could give an example of how you intend to use it, especially from the user space's viewpoint. 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
