Move data to OneNAND

same change made to kernel-samsung-aries by pawitp, matching the change

Change-Id: Ic43955cf0ef0a5d7f229faf1e9636143c9b90351
Revert "Move data to OneNAND"

This reverts commit fd74c34e5bb9e688d4092b5ebce3a21904aa31b3.
Re-enable data usage tracking

Change-Id: I1384d11d2bf212637d1d2219ac3c994155a19236
Enable RNDIS in kernel for USB tethering support

Change-Id: If4981d43f709a4192f0b24a11129315206a17ec5
Replace VSYNC uevent thread with a custom IOCTL.

* The uevents were causing high CPU usage in android
  system_server for really no good reason since it
  doesn't need to watch for them

  8e68584758ea2502118ff481ff6e804ad8df46a3

Change-Id: Ia5dd0b5f33e10cc63f96117e94c08dfc40cf5824
s3cfb: Don't lock for vsync poll

Ioctl vsync polling runs in its own thread and will always hold
a lock on the framebuffer, only releasing on a vsync event, causing
microlags. Do not lock to prevent the issue from happening.

Not locking should not have any negative effect because the original
uevent code does not lock anyway.

Change-Id: I27f34170d1ec3a3d150aa54816f9166365b8da16
Revert "Enable RNDIS in kernel for USB tethering support"

Needs more testing.. with this and the device patch, adb/usb transfer doesn't work for me.

This reverts commit 359e2f3f649fc1919c3cb2e28406d1eddcd94c47.
samsung_infuse4g: Take 30mb from cache and make system 380mb
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>

Change-Id: Ib581e1ae6aa206c770b4b3a14e7420c0f3f7543a
cpufreq: Add a boostpulse interface to ondemand

For applications that require a one-shot increase in frequency,
the boostpulse interface would help to scale to max for the time
specified in boostime. This helps applications that currently
increases scaling_min_freq and resets later after a fixed duration.
Instead of changing scaling_min_freq applications can directly write
to boostpulse and governer resets during regular timer after the time
expires.

Change-Id: Ie5f490ff06b41364aa76dd468573433495da28a4
Signed-off-by: Narayanan Gopalakrishnan <nargop@codeaurora.org>

Conflicts:

	drivers/cpufreq/cpufreq_ondemand.c
cpufreq: ondemand: Fix the boostpulse interface

* Boostpulse was not working because no default frequency was set.
 * We don't need an input handler to push the freq to max, userspace
   does a better job with the Power HAL.
 * Tweak boost time to 500ms

Change-Id: I53f1639457971d0cb216f2a7e9ad7b17ed14811a
cpufreq: ondemand: Add duration for boosting

* Keep default behavior of 500ms boost if "1" is given, otherwise use
   the value (microseconds) as the boost duration.

Change-Id: I459802453a2f921e1c1c31bd995d200e39714618
drivers: cpufreq: Add max duration for boosting

* Don't allow boosting for more than 5 seconds.

Change-Id: Ie79d4dfe946ad413df7e36818d1297add113d83f
cpufreq: ondemand: Default to max

Change-Id: If5bccb5e9d831246323e433c48b3762daf92f5ea
drivers: cpufreq: Send a uevent when governor changes

 * Useful so userspace tools can reconfigure.

Change-Id: Ib423910b8b9ac791ebe81a75bf399f58272f64f2
Replace VSYNC uevent thread with a custom IOCTL.

* The uevents were causing high CPU usage in android
  system_server for really no good reason since it
  doesn't need to watch for them

  8e68584758ea2502118ff481ff6e804ad8df46a3

Change-Id: Ia5dd0b5f33e10cc63f96117e94c08dfc40cf5824
s3cfb: Don't lock for vsync poll

Ioctl vsync polling runs in its own thread and will always hold
a lock on the framebuffer, only releasing on a vsync event, causing
microlags. Do not lock to prevent the issue from happening.

Not locking should not have any negative effect because the original
uevent code does not lock anyway.

Change-Id: I27f34170d1ec3a3d150aa54816f9166365b8da16
samsung_infuse4g: Take 30mb from cache and make system 380mb
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>

Change-Id: Ib581e1ae6aa206c770b4b3a14e7420c0f3f7543a
cpufreq: Add a boostpulse interface to ondemand

For applications that require a one-shot increase in frequency,
the boostpulse interface would help to scale to max for the time
specified in boostime. This helps applications that currently
increases scaling_min_freq and resets later after a fixed duration.
Instead of changing scaling_min_freq applications can directly write
to boostpulse and governer resets during regular timer after the time
expires.

Change-Id: Ie5f490ff06b41364aa76dd468573433495da28a4
Signed-off-by: Narayanan Gopalakrishnan <nargop@codeaurora.org>

Conflicts:

	drivers/cpufreq/cpufreq_ondemand.c
cpufreq: ondemand: Fix the boostpulse interface

* Boostpulse was not working because no default frequency was set.
 * We don't need an input handler to push the freq to max, userspace
   does a better job with the Power HAL.
 * Tweak boost time to 500ms

Change-Id: I53f1639457971d0cb216f2a7e9ad7b17ed14811a
cpufreq: ondemand: Add duration for boosting

* Keep default behavior of 500ms boost if "1" is given, otherwise use
   the value (microseconds) as the boost duration.

Change-Id: I459802453a2f921e1c1c31bd995d200e39714618