ARM: dts: msm: change ambient light sensor maximum detection range

Increase default cm36283 ambient light sensor maximum detection range
to 6553.5 lux because there is no need for high resolution but require
high measurement range.

CRs-Fixed: 579407
Change-Id: Ib6e56271dab31dcbaa4764fb4e56ac1a94b79cea
Signed-off-by: Oliver Wang <mengmeng@codeaurora.org>
Signed-off-by: Bingzhe Cai <bingzhec@codeaurora.org>
sched: Fix clear NOHZ_BALANCE_KICK

I have faced a sequence where the Idle Load Balance was sometime not
triggered for a while on my platform, in the following scenario:

 CPU 0 and CPU 1 are running tasks and CPU 2 is idle

 CPU 1 kicks the Idle Load Balance
 CPU 1 selects CPU 2 as the new Idle Load Balancer
 CPU 2 sets NOHZ_BALANCE_KICK for CPU 2
 CPU 2 sends a reschedule IPI to CPU 2

 While CPU 3 wakes up, CPU 0 or CPU 1 migrates a waking up task A on CPU 2

 CPU 2 finally wakes up, runs task A and discards the Idle Load Balance
       task A quickly goes back to sleep (before a tick occurs on CPU 2)
 CPU 2 goes back to idle with NOHZ_BALANCE_KICK set

Whenever CPU 2 will be selected as the ILB, no reschedule IPI will be sent
because NOHZ_BALANCE_KICK is already set and no Idle Load Balance will be
performed.

We must wait for the sched softirq to be raised on CPU 2 thanks to another
part the kernel to come back to clear NOHZ_BALANCE_KICK.

The proposed solution clears NOHZ_BALANCE_KICK in schedule_ipi if
we can't raise the sched_softirq for the Idle Load Balance.

Change since V1:

- move the clear of NOHZ_BALANCE_KICK in got_nohz_idle_kick if the ILB
  can't run on this CPU (as suggested by Peter)

Change-Id: Ia206acc5e1109dcb6e7cd09d96c238721b4ad044
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1370419991-13870-1-git-send-email-vincent.guittot@linaro.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Git-commit: 873b4c65b519fd769940eb281f77848227d4e5c1
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
[smuckle@codeaurora.org: minor merge resolution for 3.4 in scheduler_ipi()]
CRs-Fixed: 583754
Signed-off-by: Steve Muckle <smuckle@codeaurora.org>
tracing/sched: add load balancer tracepoint

When doing performance analysis it can be useful to see exactly
what is going on with the load balancer - when it runs and why
exactly it may not be redistributing load.

This additional tracepoint will show the idle context of the
load balance operation (idle, not idle, newly idle), various
values from the load balancing operation, the final result,
and the new balance interval.

Change-Id: I9e5c97ae3878bea44e60d189ff3cec2275f2c75e
CRs-Fixed: 583754
Signed-off-by: Steve Muckle <smuckle@codeaurora.org>
Merge "sched: Fix clear NOHZ_BALANCE_KICK"
Merge "tracing/sched: add load balancer tracepoint"
Merge "ARM: dts: msm: change ambient light sensor maximum detection range"
Merge 719f9b695afe24f51bfd95f9c06dfbb92f6e6a8b on remote branch

Change-Id: I70fa4d6b72b883f8c67c59fc556895df36f80724
Merge "Merge 719f9b695afe24f51bfd95f9c06dfbb92f6e6a8b on remote branch"
Merge branch 'jb_3.2.1' of git://codeaurora.org/kernel/msm into jb_3.2.1