[PATCH 1/4] mfd: ab8500: add devicetree support for fuelgauge

2012-09-30 Thread Rajanikanth H . V
From: "Rajanikanth H.V" - This patch adds device tree support for fuelguage 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. Signed-off-by: Rajanikanth H.V --- Documentation/devicet

[PATCH 3/4] mfd: ab8500: add devicetree support for charger

2012-09-30 Thread Rajanikanth H . V
From: "Rajanikanth H.V" This patch adds device tree support for charger driver Signed-off-by: Rajanikanth H.V --- Documentation/devicetree/bindings/mfd/ab8500.txt | 14 + .../bindings/power_supply/ab8500/charger.txt | 44 ++ arch/arm/boot/dts/dbx5x0.dtsi

[PATCH 2/4] mfd: ab8500: add devicetree support for Btemp

2012-09-30 Thread Rajanikanth H . V
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 |7 ++- .../bindings/power_supply/ab8500/btemp.txt | 29 +++ arch/arm/boot/dts/dbx5x0.d

[PATCH 4/4] mfd: ab8500: add devicetree support for charging algorithm

2012-09-30 Thread Rajanikanth H . V
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 | 36 drivers/mfd/ab8500-core.c |1 + drivers/power/abx500_chargalg.c

[PATCH 0/4] Implement device tree support for ab8500 BM Devices

2012-09-30 Thread Rajanikanth H . V
From: "Rajanikanth H.V" This patch-set adds device tree support for ab8500 battery-managed devices. This removes the redundant platform structure maintained across bm devices and implements common DT probe routine across all the modules. Rajanikanth H.V (4): mfd: ab8500: add devicetree support

Re: [PATCH V2 3/3] workqueue: Schedule work on non-idle cpu instead of current one

2012-09-30 Thread Viresh Kumar
On 1 October 2012 06:02, Tejun Heo wrote: > It isn't about the CPU being actually idle? No. Being idle only from scheduler's perspective. :) > Also, if it's only about timers, shouldn't it be enough to implement > it for timer and delayed_work? What if we need a timer, which must re-arm itself

Re: [PATCH V2 3/3] workqueue: Schedule work on non-idle cpu instead of current one

2012-09-30 Thread Tejun Heo
Hello, On Sun, Sep 30, 2012 at 05:46:45PM +0530, Viresh Kumar wrote: > For the scheduler CPU is idle, if all below are true: > - current task is idle task > - nr_running == 0 > - wake_list is empty > > And during these conditions, there can be a timer running in background. > And when we reach it

RT patches and Linaro Linux

2012-09-30 Thread Einar Már Björgvinsson
Hi there I'm looking for the correct RT patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) for a Linaro Linux source. Just for a start I tried with linux-linaro-3.4-2012.05-1 with the RT patch patch-3.4-rc2-rt1.patch.bz2 and got some build errors due to undeclared methods/variables. I

Re: [PATCH 4/4] cpuidle - support multiple drivers

2012-09-30 Thread Daniel Lezcano
On 09/30/2012 12:07 AM, Rafael J. Wysocki wrote: > On Saturday, September 29, 2012, Daniel Lezcano wrote: >> On 09/29/2012 11:41 AM, Francesco Lavra wrote: >>> Hi, >> Hi Francesco, >> >> thanks for reviewing the patch. >> static ssize_t show_current_driver(struct device *dev,

Re: [PATCH V2 3/3] workqueue: Schedule work on non-idle cpu instead of current one

2012-09-30 Thread Viresh Kumar
On 30 September 2012 14:24, Tejun Heo wrote: > On Thu, Sep 27, 2012 at 02:34:05PM +0530, Viresh Kumar wrote: >> - A cpu has programmed a timer and is IDLE now. >> - CPU gets into interrupt handler due to timer and queues a work. As the CPU >> is >> currently IDLE, we can queue this work to some

Re: [PATCH V2 3/3] workqueue: Schedule work on non-idle cpu instead of current one

2012-09-30 Thread Tejun Heo
Hello, Viresh. On Thu, Sep 27, 2012 at 02:34:05PM +0530, Viresh Kumar wrote: > - A cpu has programmed a timer and is IDLE now. > - CPU gets into interrupt handler due to timer and queues a work. As the CPU > is > currently IDLE, we can queue this work to some other CPU. I'm still a bit confuse