2 Nov 2011 05:10
(unknown)
Abul Roihan <aroihan <at> aol.com>
2011-11-02 04:10:20 GMT
2011-11-02 04:10:20 GMT
http://parcs-fontaine.com/Herbal.php
http://parcs-fontaine.com/Herbal.php
Greetings, We are pleased to release the videos of the Embedded Linux Conference Europe that took place one week ago in Prague: http://free-electrons.com/blog/elce-2011-videos/ Happy downloads! Michael. -- -- Michael Opdenacker, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com +33 484 253 396
http://www.kaara.fi/pp.php
On Mon, Nov 07, 2011 at 08:14:06AM +0100, Michael Opdenacker wrote: > Greetings, > > We are pleased to release the videos of the Embedded Linux Conference > Europe that took place one week ago in Prague: > http://free-electrons.com/blog/elce-2011-videos/ Wow, that was _very_ fast! Congrats and thanks! Wolfram -- -- Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ |
Hi All, [Very Sorry for the Big Email] [I have posted this on lm-sensors and platform-drivers-x86 lists earlier. As per some recommendations there, posting it here] 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 this can 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.(Continue reading)
Hi, On Tue, Nov 08, 2011 at 04:39:17PM +0530, R, Durgadoss wrote: > [Very Sorry for the Big Email] > > [I have posted this on lm-sensors and platform-drivers-x86 > lists earlier. As per some recommendations there, posting it > here] > > 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 this can 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(Continue reading)
Hi, [snip.] > > > > I would like to see the opinion of the community on this entire > > stuff, before I start writing some code. > > looks like this should be done on hwmon ? We discussed it there. The link I sent in the previous mail, has all the discussions. Thanks, Durga
On 08/11/11 11:09, R, Durgadoss wrote: > Hi All, Hi Durga, > > [Very Sorry for the Big Email] > > [I have posted this on lm-sensors and platform-drivers-x86 > lists earlier. As per some recommendations there, posting it > here] > > 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 this can 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(Continue reading)
On Tue, Nov 08, 2011 at 04:39:17PM +0530, R, Durgadoss wrote: > [I have posted this on lm-sensors and platform-drivers-x86 > lists earlier. As per some recommendations there, posting it > here] lkml would probably be useful. It'd also help if you could publish code along with your mail, in general people are much more likely to review concrete code. > 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 What would the voltage limits be? Whatever is going on here there should be some integration with the regulator framework, modern regulators are often able to report when they go out of regulator and able to impose current limits.
RSS Feed2 | |
|---|---|
3 | |
3 | |
10 | |
2 | |
6 | |
2 | |
4 | |
8 | |
5 | |
9 | |
20 | |
8 | |
18 | |
22 | |
6 | |
31 | |
24 | |
10 | |
24 | |
21 | |
11 | |
31 | |
19 | |
26 | |
22 | |
82 | |
26 | |
16 | |
63 | |
82 | |
22 | |
21 | |
7 | |
7 | |
31 | |
31 | |
26 | |
26 | |
34 | |
107 | |
56 | |
25 | |
58 | |
127 | |
94 | |
263 | |
14 | |
92 | |
20 | |
6 | |
193 | |
51 | |
74 | |
238 | |
48 | |
338 | |
222 | |
433 | |
34 |