backlight: set minimum brightness to 1

minimum brightness is 10 by default, which can be pretty bright at night. allow it to be set below 10, with 1 being the default.

Change-Id: Ia8d90b257be95bae01c5f4b38c545f74b519f0ef
cpufreq: interactive: Honor changed minimum frequency

This saves a few cycles in the timer routine.

Change-Id: I732a20e96ed1d3aa64da82961f5cd95ea47576da
cpufreq: interactive: Use parts of native boost routine

Not all governors are created equal. Set boostpulse_endtime
and floor_freq to smoothen the timer routine.
cpufreq: interactive: Use frequency dependent per cpu timings

This allows in-depth testing of the timer routine.

Change-Id: Iee608ec2a816b2e5cf3fa02afcdd9d396e560871
cpufreq: interactive: Honor boosted state when entering idle

The old logic didn't take the boosted state in account. Just
leave the comment intact because our temporary min is not
the regular policy->min it refers to.
Revert "bcmdhd: Filter multicast packages when suspended"

This reverts commit 4580a4385bc9c79f3af421371a417060a9b4de98.

this causes wlan_rx_wake wakelocks on dynamic ips.
minor cleanup

Change-Id: I891e73f8fe0616b2a69657cfbd9ac034f96ab97a
cpufreq: interactive: simplify suspend hotplugging

Change-Id: I909e4103ff53a42f22d41680dccb073662b6e5bc
cpufreq: interactive: Move definition of cpufreq_gov_interactive downwards

This moves definition of cpufreq_gov_interactive towards the bottom of file, so
that we don't have to add prototype of cpufreq_governor_interactive() in the
beginning of file.

Change-Id: I04bd1004954eb36502c5cd7e35d3d7274cddaf95

[also tidied up abit]
lib/checksum.c: optimize do_csum a bit

Reduce the number of variables modified by the loop in do_csum() by 1,
which seems like a good idea.  On Nios II (a RISC CPU with 3-operand
instruction set) it reduces the loop from 7 to 6 instructions, including
the conditional branch.

Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
AIO: Don't plug the I/O queue in do_io_submit() Asynchronous I/O latency to a solid-state disk greatly increased between the 2.6.32 and 3.0 kernels. By removing the plug from do_io_submit(), we observed a 34% improvement in the I/O latency.

Unfortunately, at this level, we don't know if the request is to
a rotating disk or not.

Change-Id: I7101df956473ed9fd5dcff18e473dd93b688a5c1
Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: linux-aio@kvack.org
Cc: Chris Mason <chris.mason@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Revert "Added fsync_control [Cocafe]"

going to try out async fsync
This reverts commit ea9bdcc1921d882669301aa481de081c3a87864b.
fsync: adapt async fsync

Change-Id: Ib0626a2ee5fbe1a3ccad4b4d003ac8b216e00f4b
bln: allow separate configuration of blink on and off delays

also minor optimisation of bln_blink_mode check

devicesettings: need the appropriate modifications
Change-Id: I9930a42907ab3ef90a85dd065193f5b696b7c061
dt2w: decrease press timeout by 1/2
500ms timeout is pretty long, decrease to near instantaneous humane taps

devicesettings: need the appropriate modifications
Change-Id: I1920d8d7951c1353b1252e6ce90e3bca3bbac186
Disable Gentle Fair Sleepers
Hide more touchscreen spamming messages pt2
config: enable CONFIG_LIB80211 and CONFIG_MAC80211

CONFIG_IKCONFIG enabled too, to get current .config file just do "zcat /proc/config.gz > /sdcard/config"
Conflicts:
	arch/arm/configs/cyanogenmod_i8160_defconfig

Change-Id: I342b66121368e408c96a1486f5861fd59b47c26d
cpufreq: interactive: fix a few compiling warnings

Change-Id: Id884c79c6767ca0639e735a86526022e54b3d32b
warning: operation on 'ret' may be undefined [-Wsequence-point]
mutex: dynamically disable mutex spinning at high load
Date	Thu, 4 Apr 2013 10:54:18 -0400

The Linux mutex code has a MUTEX_SPIN_ON_OWNER configuration
option that was enabled by default in major distributions like Red
Hat. Allowing threads waiting on mutex to spin while the mutex owner
is running will theoretically reduce latency on the acquisition of
mutex at the expense of energy efficiency as the spinning threads
are doing no useful work.

This is not a problem on a lightly loaded system where the CPU may
be idle anyway. On a highly loaded system, the spinning tasks may be
blocking other tasks from running even if they have higher priority
because the spinning was done with preemption disabled.

This patch will disable mutex spinning if the current load is high
enough. The load is considered high if there are 2 or more active tasks
waiting to run on the current CPU. If there is only one task waiting,
it will check the average load at the past minute (calc_load_tasks).
If it is more than double the number of active CPUs, the load is
considered high too.  This is a rather simple metric that does not
incur that much additional overhead.

The AIM7 benchmarks were run on 3.7.10 derived kernels to show the
performance changes with this patch on a 8-socket 80-core system
with hyperthreading off.  The table below shows the mean % change
in performance over a range of users for some AIM7 workloads with
just the less atomic operation patch (patch 1) vs the less atomic
operation patch plus this one (patches 1+3).

+--------------+-----------------+-----------------+-----------------+
|   Workload   | mean % change   | mean % change   | mean % change   |
|              | 10-100 users    | 200-1000 users  | 1100-2000 users |
+--------------+-----------------+-----------------+-----------------+
| alltests     |      0.0%       |     -0.1%       |    +5.0%        |
| five_sec     |     +1.5%       |     +1.3%       |    +1.3%        |
| fserver      |     +1.5%       |    +25.4%       |    +9.6%        |
| high_systime |     +0.1%       |      0.0%       |    +0.8%        |
| new_fserver  |     +0.2%       |    +11.9%       |   +14.1%        |
| shared       |     -1.2%       |     +0.3%       |    +1.8%        |
| short        |     +6.4%       |     +2.5%       |    +3.0%        |
+--------------+-----------------+-----------------+-----------------+
It can be seen that this patch provides some big performance
improvement for the fserver and new_fserver workloads while is still
generally positive for the other AIM7 workloads.

Signed-off-by: Waiman Long <Waiman.Long@hp.com>
Reviewed-by: Davidlohr Bueso <davidlohr.bueso@hp.com>
modified for tuna kernel from LKML

Signed-off-by: Paul Reioux <reioux@gmail.com>