On Sat, Nov 05, 2011 at 03:13:14AM -0400, R, Durgadoss wrote: > Hi All, > > [Very Sorry for the big e-mail] > > As we all know, Linux is increasingly being used in handhelds. > The Hardware that supports the handhelds is also becoming > Performance-centric. With this, we need a way to efficiently > monitor the current consumption of the platform and take actions > when the platform draws more current, than it should. > > Where does this happen ? > ------------------------ > In a handheld, there are many components that demand high > Current. For example, Camera Flash, Video Streaming, 3G Voice > Call etc. Typically, two or more of these components are used > simultaneously in a real-time scenario. When this happens, the > current draw of the platform surges. If this surge lasts for > more than a specific time, it could crash the platform irrecoverably. > > How do we tackle this ? > ----------------------- > In Intel Medfield (Atom based) platform we had a driver that > Configures the current limits. When the platform current draws > more current than the programmed limit, the hardware generates > interrupt. The driver receives this interrupt and notifies the > user space to take appropriate actions. > The patch and the subsequent discussions can be found here: > http://comments.gmane.org/gmane.linux.drivers.platform.x86.devel/1197 > > To Generalize: > -------------- > With many more platforms to come, having a separate driver for each > results in heavy code duplication. Also, there arises a problem of > where to put these kind of drivers ? Hence I propose the idea of having > a Current Management subsystem. > > This will provide a generic ABI, API, so that the platform specific > drivers can register with this framework (and thus avail the basic > needs) and handle the events in their own way. > > In simple terms, this framework will offer something like this: > Current[1-N]_limit - set of current limits > Voltage[1-X]_limit - set of voltage limits > Controllers[1-Y]_enable - These are the components by throttling/ > disabling which the current consumption can be brought down. > hwmon already has power[1-*]_cap power[1-*]_crit with explicit mention of "the system is expected take drastic action to reduce power consumption, such as a system shutdown or a forced powerdown of some devices". We also have curr[1-*]_crit though with no explicit mention of any action to be taken. We also have a pending patch (waiting for someone to comment on it) to add notification and uevent support to sysfs ABI. It is at the tip of my staging tree: http://git.kernel.org/?p=linux/kernel/git/groeck/linux-staging.git;a=shortlog;h=refs/heads/hwmon-staging Using this would address reporting to userspace. Question is how to handle any actions. The regulator subsystem may be better suited to handle this, as already suggested. Another approach would be to have a kernel-internal notification mechanism, which was already suggested for the hwmon subsystem. Either case, I don't think a framework should be restricted to currents. Power may be an even more important factor to determine if the system needs to be throttled. In some cases, it may be necessary to reduce (or increase ?) voltage to reduce current. So I think this will need a more comprehensive approach. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
