limit gpu to 440mhz
input: touchscreen: revert mxt224_u1 changes
ksm: check and skip page, if it is already scanned

On system like Android where most of the process are forked
from parent w/o execve, KSM can scan same page multiple times
in one scan cycle. There is no advantage in scanning same page
multiple times for merging. During testing with Android, it was
observed around 60% pages are skipped for each scan cycle.

Change-Id: I0cf01802f0b4d61fcab92558beb9e1c660dc9a77
Link: http://lkml.kernel.org/r/CAMrOTPgBtANS_ryRjan0-dTL97U7eRvtf3dCsss=Kn+Uk89fuA@mail.gmail.com
Signed-off-by: Pradeep Sawlani <sawlani@amazon.com>

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

Conflicts:
	include/linux/page-flags.h
ARM: L1 cache optimization
ARM: Add optimised swahb32() byteswap helper
ARM-spinlock: use ticket algorithm for ARMv6+ locking implementation
ext4: prevent kernel panic in case of uninitialized jinode
update defconfig
ondemand: Add support to consider other cpu load when scaling frequen…
…cies

Currently only current cpu load is considered when frequency scaling.
As a side effect of this when scheduler migrates a thread to a slower
core, the execution time increases unexpectedly.

The new algorithm not only considers current cpu load for frequency
scaling, but also takes into account load of other online cpus. The
treshold for this can be controlled using up_threshold_any_cpu_load.
When the up_threshold_any_cpu_load is crossed in any cpu then the
current cpu is set to sync_freq.

Also, when more than one cpu is online a two step ramp-up mechanism
is used. When the up_threshold_multi_core is crossed the cpu is ramped
up to optimal_freq which is less than policy->max and set to a power
friendly value.

Change-Id: I469d6924743239e45c50255b9974c93bbea9d470
Signed-off-by: Narayanan Gopalakrishnan <nargop@codeaurora.org>
bcmdhd: update to 1.61.58 from google edition jf (4.3)
 Applied to smdk44x2 appears to help with dialing
 issues on wifi.  jf firmware is ideal also.

Change-Id: I299a0576c0a7c0c36dbdab492e85109daa9c9f01
mm: Don't use CMA pages for page cache
All layers of the page cache may take extra references to
pages to avoid migration. This is fine for general movable
pages but renders CMA pages useless as they cannot be
allocated for contiguous mode. Always omitting movable
pages completely has poor utilization of memory so attempt
with the given GFP flags first and if a CMA page is allocated,
free it and get a new non-movable page. This does have a minor
performance impact, but ultimately it's a tradeoff between
never using movable pages and taking the extra hit of a
free/realloc.

Change-Id: I4e9d7fc1c65306d6356492fd1a99935aa62ed2ec
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Revert "mm: Don't use CMA pages for page cache"
input: mxt224: tweak touchscreen when plugged to charger
pm-hotplug: add tegrak's secondcore support + pm-hotplug enable/disable depending on the selected cpu governor
build: update defconfig
+ undervolt busfreq and set a higher threshold, this aims battery saving