Hello,
On Fri, 17 Aug 2012 11:18:36 +0800
YongQin Liu yongqin@linaro.org wrote:
Hi,
Just found that I can't view the lava result on android-build page for
some build.
but not all of them, I still can view some the information of some
builds before.
say the builds of
On 17 August 2012 00:37, Michael Hope michael.h...@linaro.org wrote:
Hi there. I'm seeing a huge improvement in the SPEC floating point
benchmarks between a hacked Ubuntu Precise 3.2.14 kernel and Linus
3.5. Does anyone know why off the top of their head?
Hacked how? How big a change? What
This patchset updates devfreq core to add support for devices
which can idle. When device idleness is detected perhaps
through runtime-pm, need some mechanism to suspend devfreq
load monitoring and resume when device is back online.
patch 1 adds core design changes mainly moving monitoring
logic
This patch adds suspend and resume apis needed
for devices which can idle. Suspend/resume apis
are called from driver to suspend/resume devfreq
load monitoring of that device.
Signed-off-by: Rajagopal Venkat rajagopal.ven...@linaro.org
---
drivers/devfreq/devfreq.c | 30
Devfreq returns governor predicted frequency as current
frequency via sysfs interface. But device may not support
all frequencies that governor predicts. As per the design
its driver responsibility to maintain current frequency
at which device is operating. So add a callback in device
profile to
Prepare devfreq core framework to support devices which
can idle. When device idleness is detected perhaps through
runtime-pm, need some mechanism to suspend devfreq load
monitoring and resume when device is back online. Present
code continues monitoring unless device is removed from
devfreq core.
