On Thu, Sep 20, 2012 at 11:07 AM, Lei Wen wrote:
> Dave,
>
>
> On Thu, Sep 20, 2012 at 10:10 AM, Lei Wen wrote:
>
>> Hi Dave,
>>
>> On Thu, Sep 20, 2012 at 12:38 AM, Dave Martin wrote:
>>
>>> On Tue, Sep 18, 2012 at 04:58:21PM -0500, Andy Doan wrote:
>>> > On 09/17/2012 04:01 AM, Dave Pigott wro
On 20 September 2012 10:33, Lei Wen wrote:
> However, the A15x4_A7x4 model is running quit slow for launching the kernel,
> about 1minute to showing the kernel booting screen. Whereas A15x1 model is
> launching quite fast, just in several seconds.
This is in general not very surprising, since the
I forwarded this to the landing team and to the Igloo Community
as well. Another good place to check for
this type of info would be http://www.igloocommunity.org/, it is all
about Snowball.
Scott
On 12-09-19 11:46 AM, Amber Graner wrote:
Hi Christoph,
Thank you so much for contacting us.
The function __cpuidle_register_driver name is confusing because it
suggests, conforming to the coding style of the kernel, it registers
the driver without taking a lock. Actually, it just fill the different
power field states with a decresing value if the power has not been
specified.
Clarify the
In the next patch, we will support different cpuidle drivers
tied with a cpu. In this case we should move the refcount to
the cpuidle_driver structure to handle several drivers at a time.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/driver.c | 11 ++-
include/linux/cpuidle.h |
The discussion about having different cpus on the system with
different latencies bring us to a first attemp by adding a
pointer in the cpuidle_device to the states array.
But as Rafael suggested, it would make more sense to create a
driver per cpu [1].
This patch add support for multiple cpuidle
Hello,
I recently acquired a Gumstix Overo Water with a Tobi and decided to put
Node.js on it to turn it into a web server of sorts.
The build dies with an "Illegal instruction" error, and I am thoroughly
confused.
In order to set up the build, I did the following:
1. imaged a microSD card with
From: "hongbo.zhang"
A cooling device should be set to state zero when it is unbound.
Signed-off-by: hongbo.zhang
---
drivers/thermal/thermal_sys.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/thermal/thermal_sys.c b/drivers/thermal/thermal_sys.c
index 2c28c85..efc5c56 100644
From: "hongbo.zhang"
If the thermal zone mode is disabled, all the referenced cooling
devices should be put into state zero.
Without this patch the thermal driver cannot deactive all its
cooling devices in .set_mode callback, because the cooling device
list is maintained in the generic thermal la
From: "hongbo.zhang"
This patch set contains two patches.
[PATCH 1/2]
A new interface is introduced to deactive all the referenced cooling devices
when thermal zone is disabled. Because the cooling device list is maintained
in the generic thermal layer, the thermal driver cannot walk through the
10 matches
Mail list logo