> -Original Message-
> From: hongbo.zhang [mailto:hongbo.zh...@linaro.org]
> Sent: Wednesday, October 31, 2012 12:49 AM
> To: linaro-dev@lists.linaro.org; linux-ker...@vger.kernel.org; linux-
> p...@vger.kernel.org; Zhang, Rui; amit.kach...@linaro.org
> Cc: patc...@linaro.org; linaro-ker.
Hey
(Cc:ing linaro-dev@ where we usually discuss technical stuff)
On Wed, Oct 31, 2012, sundar.subramani...@gmail.com wrote:
> This is great. Just tried the pre-compiled image and works like a charm.
> It took a little longer than two minutes though on my i3/4Gig machine.
> Haven't yet tr
With the tegra3 and the big.LITTLE [1] new architectures, several cpus
with different characteristics (latencies and states) can co-exists on the
system.
The cpuidle framework has the limitation of handling only identical cpus.
This patch removes this limitation by introducing the multiple driver
The code is racy and the check with cpuidle_curr_driver should be
done under the lock.
I don't find a path in the different drivers where that could happen
because the arch specific drivers are written in such way it is not
possible to register a driver while it is unregistered, except maybe
in a
We want to support different cpuidle drivers co-existing together.
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
Acked-by: Peter De Schrijver
---
drivers/cpuidle/driver.c | 13 -
include/
This patch is a preparation for the multiple drivers support.
As the next patch will introduce the multiple drivers with the Kconfig
option and we want to keep the code clean and understandable, this patch
defines a set of functions for encapsulating some common parts and split
what should be done
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 adds support for multiple cpuidl
From: "Rajanikanth H.V"
- This patch adds device tree support for fuelgauge driver
- optimize bm devices platform_data usage and of_probe(...)
Note: of_probe() routine for battery managed devices is made
common across all bm drivers.
- test status:
- interrupt numbers assigned differs betwe
From: "Rajanikanth H.V"
This patch adds device tree support for charging algorithm
driver
Signed-off-by: Rajanikanth H.V
---
.../bindings/power_supply/ab8500/chargalg.txt | 16 ++
arch/arm/boot/dts/dbx5x0.dtsi |5 ++
drivers/mfd/ab8500-core.c
From: "Rajanikanth H.V"
This patch adds device tree support for ab8500-charger
driver
Signed-off-by: Rajanikanth H.V
---
Documentation/devicetree/bindings/mfd/ab8500.txt | 14
.../bindings/power_supply/ab8500/charger.txt | 25 +++
arch/arm/boot/dts/dbx5x0.dtsi
From: "Rajanikanth H.V"
This patch adds device tree support for
battery-temperature-monitor driver
Signed-off-by: Rajanikanth H.V
---
Documentation/devicetree/bindings/mfd/ab8500.txt |6 ++
.../bindings/power_supply/ab8500/btemp.txt | 16 +
arch/arm/boot/dts/dbx5x0.dtsi
From: "Rajanikanth H.V"
This patch-set adds device tree binding for ab8500 battery-managed
devices. Removes the redundant platform structure maintained
across bm devices and implements common DT probe routine across all the
modules.
Test status:
a) Tested across 'legacy platform data' and DT bin
On 15 October 2012 10:08, Viresh Kumar wrote:
> I totally understand since last few weeks you guys were very busy as the
> merge window was around. So, didn't tried to disturb you then :)
>
> Can you please share your viewpoint on this patchset now? And also
> the running timer migration patch (wh
13 matches
Mail list logo
