mali: change alloc order from 6 to 11 for 4210

taken from samsung i9100 jb update

Change-Id: Ie67ffa8a72101fbe4460cdde1cb5c3435979ca66
i777, i9100, n7000: enable utf8 support for nls

Change-Id: Iefbeee4aa149eaf9a5aca1651cc39a592f0e4208
4412: builtin md4 and dnsresolver

Change-Id: Iab4e05f831e09d6cb2b40a2117accdb5b903a6b2
enable nfs support

Change-Id: I84dc53e949be90ca464cb80432105130d089dd90
Voodoo Sound added for i9300, n7100, n8000, m8013, t0lte and t0ltecdma - Used The Glitch Kernel i9300 as a refrence - https://github.com/GlitchKernel/Glitch-i9300
Makefile:  Add LDFLAGS_MODULE  = --strip-debug

shrink the modules down to a respectable size
Signed-off-by: Curtis Menard <curtis.menard@gmail.com>

Change-Id: I7ce7aa4d9a8e6315983b87aa211af5db27d457e6
mach-exynos: cpufreq: undervolting and overclocking support
cpufreq: undervolting interfaces
Allow CPU Based Alignment Handling
Expand OC to 1920 and 2000MHz

Tweak deadline scheduler.
Raise max readahead.
Tune Ondemand for those who want to use it.
Try to get pegasusq to online cores sooner, it seems a little sleepy.
Push GPU to 600MHz as test.
Scaling needs attention for UI response. Credit Morfic
cpufreq: fix sticking OC clocks

Conflicts:
	arch/arm/mach-exynos/cpufreq.c
performance: Turn CPUs online while active

Since we don't have separate active hotplugging logic aside the in-governor one in pegasusq, switching to performance governor will always just remain with whatever cores were online before the switch. This activates all available cores on governor start, and turns additional cores off when stopped.
t0ltecdma: custom config

Change-Id: I1c83df564b39d20cb6628ba9cbfd9e586c7e80f8
t0ltecdma: savedefconfig

Change-Id: Ie9e3ba1af4e63b3503cc0866fe372b58cdd20d0e
Cleanup

Change-Id: I82b68d2e1af7b9d70e2cfa011986378b49268ca3
cpufreq: interactive: Add boostpulse duration

Taken from stingray.

Credit - Daniel Bateman (tuna patch), Narayanan Gopalakrishnan and
Steve Kondik.

Change-Id: I7de5b15fa74a5c67437f514c20a0ad63f997f565
cpufreq: interactive: limit boostpulse duration to MAX

For boostpulse requests for a duration above MAX,
limit them to MAX instead of to DEFAULT.

Change-Id: I03ed20ee3b7a47122361ec890962d8c7ed0dad81
cpufreq: Update interactive governor

Originally for crespo (Iba70ed3580dd04704b0d7b4acde178df7a843b5f)

This is a squashed commit of the following:

cpufreq: interactive: add show_boost sysfs entry
  Signed-off-by: jt1134 <jt1134@gmail.com>

cpufreq: interactive: take idle notifications only when active
Register an idle notifier only when the governor is active.  Also
short-circuit work of idle end if the governor is not enabled.
  Signed-off-by: Sam Leffler <sleffler@chromium.org>

cpufreq: interactive: keep freezer happy when not current governor
Fix a problem where the hung task mechanism was deeming the interactive
clock boost thread as hung.  This was because the thread is created at
module init but never run/woken up until needed.  If the governor is not
being used this can be forever.  To workaround this explicitly wake up
the thread once all the necessary data structures are initialized.  The
latter required some minor code shuffle.
  Signed-off-by: Sam Leffler <sleffler@chromium.org>

cpufreq: interactive: handle speed up and down in the realtime task
Not useful to have a separate, non-realtime workqueue for speed down
events, avoid priority inversion for speed up events.
  Signed-off-by: Todd Poynor <toddpoynor@google.com>

cpufreq: interactive: remove input_boost handling
Now handled in userspace Power HAL instead.
  Signed-off-by: Todd Poynor <toddpoynor@google.com>

cpufreq: fix interactive bug during hotplug
When a new cpu is added and if does not enter idle
for long, the interactive timer is not started and hence
the cpu remains at lowest frequecny, despite the system
load. This impacts mainly benchmarks. Starting a timer
at governor start to handle low frequency.
  Signed-off-by: Narayanan Gopalakrishnan <nargop@codeaurora.org>

cpufreq: interactive: always limit initial speed bump to hispeed
First bump speed up to hispeed_freq whenever the current speed is below
hispeed_freq, instead of only when the current speed is the minimum speed.
The previous code made it too difficult to use hispeed_freq as a common
intermediate speed on systems that frequently run at speeds between
minimum and hispeed_freq.
  Signed-off-by: Todd Poynor <toddpoynor@google.com>

cpufreq: interactive: run at fraction of hispeed_freq when load is low
When load is below go_hispeed_load, apply the percentage of CPU load to
a max frequency of hispeed_freq instead of the max speed.  This avoids
jumping too quickly to hispeed_freq when it is a relatively low
percentage of max speed.  This also allows go_hispeed_load to be set to
a high percentage relative to hispeed_freq (as a percentage of max speed,
again useful when hispeed_freq is a low fraction of max speed), to cap
larger loads at hispeed_freq.  For example, a load of 60% will typically
move to 60% of hispeed_freq, not 60% of max speed.  This causes the
governor to apply two different speed caps, depending on whether load is
below or above go_hispeed_load.

Also fix the type of hispeed_freq, which was u64, to match other
speed data types (and avoid overhead and allow division).
  Signed-off-by: Todd Poynor <toddpoynor@google.com>

Change-Id: I11646ce80158bf198c0ced4e006f0f7f983904d3
Linux 3.0.65

Change-Id: I648fbd46a49e9242bf6da8348006882e61c73a48