Revert "Set CONFIG_HZ=256"

This reverts commit 6bb9e87d18b7fa70a3c5458e87ef7359bde936db.
Revert "Increase DEFAULT_MMAP_MIN_ADDR value from 4096 to 8192"

This reverts commit c9339125ed1bd5f6655bfc6324930a0bd6b79d66.

Conflicts:

	arch/arm/configs/air_defconfig
acpuclock-8064.c: Disable some frequency
Signed-off-by: Seongmin Park <r_data@naver.com>
Use ccache so that it recompiles faster after a make clean.

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>

Conflicts:

	Makefile
Update #1 - 03122013
Signed-off-by: Seongmin Park <r_data@naver.com>
acpuclock-8064.c: Fix freq table
Signed-off-by: Seongmin Park <r_data@naver.com>
Update defconfig
Signed-off-by: Seongmin Park <r_data@naver.com>
sweep2wake: add lock up detection and re-init if detected

Signed-off-by: faux123 <reioux@gmail.com>
sweep2wake: force reinit upon detection of lock up

also added more debugging messages to narrow down exact cause

Signed-off-by: faux123 <reioux@gmail.com>
sweep2wake: add more debugging and re-organized reset code when lock up

Signed-off-by: faux123 <reioux@gmail.com>
sweep2wake: another attempt to re-init the touch driver

Signed-off-by: faux123 <reioux@gmail.com>
sweep2wake: release all touch events before enable irq in early suspend

per conversation with showp1984

Signed-off-by: faux123 <reioux@gmail.com>
Revert "final color config for pa 3.0"

This reverts commit 81c5fa82e2071ce13b5e6a6600e90a484b080fc1.
drivers: input: touch filter control enablement

1) Turn off accuracy filter by default and add a switch to turn it
on. Since it is off by default, users with issues should be fixed I
hope.  Good practice will be to turn off, set params, and turn on to
that the touchscreen is not disrupted if the user is interacting with
it.

To enable:
echo 1 > /sys/devices/virtual/input/lge_touch/accuracy_filter_enable

To disable:
echo 0 > /sys/devices/virtual/input/lge_touch/accuracy_filter_enable

2) Allow stock defaults to be set on init so when a user decides they
want to enable the filter, they will have reasonable defaults ready to
go.

3) TESTING ONLY - Allow Jitter filter control to be turned on in a
similar way and allow the adjust_margin parameter to be adjusted.  I
thought this might be useful for stylus control or users with big hands
etc, but after initial testing it doesn't seem to be useful at all and
makes the touch screen very hard to use. We will leave in for more
testing for now. Will likely pull unless it proves to be useful for some
purpose.

/sys/devices/virtual/input/lge_touch/adust_margin
/sys/devices/virtual/input/lge_touch/jitter_filter_enable

Notes: The stock kernel already allows all these parameters to be set in
one command as below. These recent changes initiated by Franco opens
each component up so that apps/scripts can more easily read the
variables. Since we add the ability to read by component, it makes sense
to also allow write by component and makes it easier to understand what
variables are being adjusted.

echo "accuracy_filter_enable ignore_pressure_gap delta_max
touch_max_count max_pressure direction_count time_to_max_pressure" >
/sys/devices/virtual/input/lge_touch/accuracy/sys/devices/virtual/input/lge_touch/accuracy

echo "jitter_filter_enable adjust_margin" >
/sys/devices/virtual/input/lge_touch/accuracy/sys/devices/virtual/input/lge_touch/jitter
Conflicts:

	drivers/input/touchscreen/lge_touch_core.c
Revert "+ "nohz/sched: delay going tickless when CPU is loaded" - http://lists.infradead.org/pipermail/linux-arm-kernel/2011-January/040165.html"

This reverts commit be7f1440c6b4a6466378c5bc639083b5b8640258.
Revert "Reduced Android Logger RAM usage. TNX to sakindia123@xda for point."

This reverts commit 33f96d3868709bd8fd823eda56e8f7c8b90dbba1.
Revert "LOAD_FREQ (4*HZ+61) avoids loadavg Moire"

This reverts commit 17b007221e72a029ade4f257ccc87ca22324cb71.
Makefile: Remove some flags
Signed-off-by: Seongmin Park <r_data@naver.com>
Makefile: Add mtune flag (Thanks to faux123)
Signed-off-by: Seongmin Park <r_data@naver.com>
rwsem: steal writing sem for better performance

Commit 5a50508 changes to rwsem from mutex, caused aim7 fork_test
performance to dropped 50%. Yuanhan liu did an analysis, found it was
caused by strict sequential writing. Ingo suggest stealing sem writing from
front task in wait queue. https://lkml.org/lkml/2013/1/29/84

So does this patch.
In this patch, I just allow write stealing to happen when the first waiter
is also writer. The performance fully is now fully recovered.

Reported-by: lkp@linux.intel.com
Cc: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Alex Shi <alex.shi@intel.com>