+ "git checkout exp" ...
New governor "Nightmare". Modified KEY_HOMEPAGE in mach-u1.c for JB-Sammy.
Finally Home button Fixed for all ROMS
Nightmare settings adjustment
Small correction to Home button Fix for JB SAMMY ROM.
mali: update gpu dvfs table voltages as soon as the driver is initialized

this commit is originally from AndreiLux's s3 kernel which also requires you to change the init sequence of the asv part.
However, in siyahkernel, gpu is initialized after the rom type is detected hence that commit is not applied.
+ updated build-script ...
+ "cpufreq: interactive: don't handle transition notification if not enabled" - https://github.com/android/kernel_common/commit/8e2dfe161140c53bb79a8b2a87a38ff6e2e8a8a9
nightmare and ZenX are HOT PLUG govs they have there ways. allow them.
Fixed some more missing HOTPLUG config for GOVS.
JB LEAK and JB Custom ROM HOME Button FIX! BIG TNX to @Alucard24

For helping to test and idea of implementation!
As TEMP solution to fix HOME button for Custom ICS and JB
Need to find better solution, this brakes JB LEAK home key!

Why Samsung did that, such waste of time trying to adapt it..
but will will beat them! as always. only matter of time!
Removed ZenX and nightmage GOVS from allowed hot plug control.

ZenX cant boot second CPU! one one active. if allowed to use hotplug
nightmare stuck kernel if allowed to use hotplug.

without hotplug control, all OK. and working good.
+ "Remove trace events from ZenX" - https://github.com/AndroidDeveloperAlliance/ZenKernel_TUNA/commit/7083f9f40a0dfc78967374ed0bc992601c12bf26
+ "Pegasusq tweaks primarily suggested by mnagy1987" - https://github.com/AndroidDeveloperAlliance/ZenKernel_TUNA/commit/47630c49926caf57d6ebcd32b0f90b93d8c4162b
+ sync with "cpufreq: ZenX: add ZenX governor v2.1" - https://github.com/AndroidDeveloperAlliance/ZenKernel_TUNA/commit/665cafe6952dc7c32050504f330c008d36a0048c#diff-3
cpufreq: ZenX: fix rearm_if_notmax calling, causing incidental timer stopping.
usb: gadget: accessory: Fix section mismatch (again)

create_bulk_endpoints should not be __init since it is called when
accessory is enabled.

Change-Id: Iac6e9f29d53c93760e926efd8e7603432632acb4
Signed-off-by: Todd Poynor <toddpoynor@google.com>
android: logger: enforce GID and CAP check on log flush

Restrict log flushing to those in the logs group, or
anyone with CAP_SYSLOG.

Change-Id: I5d6977d1c0d60ffe8487771cc195789e5db95454
Signed-off-by: Charndeep Grewal <csgrewa@tycho.ncsc.mil>
sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire

LOAD_FREQ is (5*HZ+1) to avoid high load average when idle:
http://kerneltrap.org/mailarchive/linux-kernel/2007/10/3/328568

I suggest (4*HZ+61) for a better distribution.

With some seconds based load (like SSL heartbeats)
and LOAD_FREQ at (5*HZ+1) I see Moire patterns like inverse sawtooth,
since 2 or 3 probes hit the jobs (load increases quickly),
followed by several probes missing it.

A 4.61 sec interval gives optimal distribution over when within a
second a probe is taken, as .61 is close to golden ratio phi 1.618...
(test in http://ripke.com/goldenratio.c).

12*4.61 = 55.32 secs is still close to a minute,
and 13*4.61=59.93 is even closer than the current 12*5.01=60.12
(with exponents EXP_x adjusted to a ratio of 13 instead of 12).
finish applying the LOAD_FREQ (4*HZ+61) avoids loadavg Moire patch from http://ripke.com/loadavg/moire

Conflicts:
	include/linux/sched.h