leanKernel v2.4.0

- Linux 3.0.22
- Linux 3.0.23
- lkflash: added the notrim option
- OPP table and smartreflex tweaks
- fast USB charging by chat0989, and ffc toggle script by me
- omap-serial fixes
- nfc wakelock reduced
- reverted c4 state patch due to instability
- fixed some opp/sr initialization bugs, a couple introduced with 2.0.0
ARM: OMAP4: cpuidle: prevent CPU1 from locking CPU0 in idle entry

We can have a lockup scenario when two cpu are spin waiting for each other:

CPU0:
	omap4_enter_idle()
		|---omap4_enter_idle_primary()
			|---------while (omap4_idle_requested_cx[1])
					cpu_relax();

CPU1:
	omap4_enter_idle()
		|----
		while ((omap4_idle_ready_count == 0) && omap4_all_cpus_idle()) {
			spin_unlock(&omap4_idle_lock);
			cpu_relax();
			spin_lock(&omap4_idle_lock);
		}

Depend on idle ready count to let CPU0 to progress forward.

Change-Id: Ida6b60f618e8078701fcad8d976c3f1620cc71e6
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Yuan Jiangli <jlyuan@motorola.com>
build script: still need to copy defconfig
defconfig: remove pvr debug stuff and tweak latency for stability.
checkt: show kernel version too, why not.
OMAP3+: PM: VP: fix integer truncation error

from Yuan Jiangli
leanKernel 2.4.1

- tweaked gpu latency for stability
- removed gpu debug for leaner kernel
- cpu1/cpu0 lockup fix from android-omap
ext4: optimize memmmove lengths in extent/index insertions

ext4_ext_insert_extent() (respectively ext4_ext_insert_index())
was using EXT_MAX_EXTENT() (resp. EXT_MAX_INDEX()) to determine
how many entries needed to be moved beyond the insertion point.
In practice this means that (320 - I) * 24 bytes were memmove()'d
when I is the insertion point, rather than (#entries - I) * 24 bytes.

This patch uses EXT_LAST_EXTENT() (resp. EXT_LAST_INDEX()) instead
to only move existing entries. The code flow is also simplified
slightly to highlight similarities and reduce code duplication in
the insertion logic.

This patch reduces system CPU consumption by over 25% on a 4kB
synchronous append DIO write workload when used with the
pre-2.6.39 x86_64 memmove() implementation. With the much faster
2.6.39 memmove() implementation we still see a decrease in
system CPU usage between 2% and 7%.

Note that the ext_debug() output changes with this patch, splitting
some log information between entries. Users of the ext_debug() output
should note that the "move %d" units changed from reporting the number
of bytes moved to reporting the number of entries moved.

Signed-off-by: Eric Gouriou <egouriou@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

Conflicts:

	fs/ext4/extents.c
ext4: optimize ext4_ext_convert_to_initialized()

This patch introduces a fast path in ext4_ext_convert_to_initialized()
for the case when the conversion can be performed by transferring
the newly initialized blocks from the uninitialized extent into
an adjacent initialized extent. Doing so removes the expensive
invocations of memmove() which occur during extent insertion and
the subsequent merge.

In practice this should be the common case for clients performing
append writes into files pre-allocated via
fallocate(FALLOC_FL_KEEP_SIZE). In such a workload performed via
direct IO and when using a suboptimal implementation of memmove()
(x86_64 prior to the 2.6.39 rewrite), this patch reduces kernel CPU
consumption by 32%.

Two new trace points are added to ext4_ext_convert_to_initialized()
to offer visibility into its operations. No exit trace point has
been added due to the multiplicity of return points. This can be
revisited once the upstream cleanup is backported.

Signed-off-by: Eric Gouriou <egouriou@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
defconfig: latency back to 100
tempcontrol: sysfs interface for temp sensor threshold control
usb: musb: Fix cold boot for a Dedicated charger

This patch adds the missing logic to detect a
dedicated charger connected at boot.

Change-Id: Id45236cb037b4386e1f6387f2064b2886661606d
Signed-off-by: Moiz Sonasath <m-sonasath@ti.com>
checkt: just fixing formatting
Added Color Control version 1.
Added note.
Added support for changing the color multipliers.
Prevent the color multipliers from being raised above the stock values.
Added support for disabling the safety feature which prevents the color
multipliers from being raised above the factory settings.
lkflash: remove the notrim option since all exps are notrim now
leanKernel 2.5.0

- Ezekeel's ColorControl
- TempControl: sysfs interface for temp sensor threshold control
- ext4 optimizations