gpu: pvr: Dump active page table when lockup is detected.
gpu: pvr: Update to DDK 1.8@2112805

This is a version number change only, which is required for
compatibility with the user-mode driver.

Change-Id: Id83c23254db8f6aac8f2f7ded8bae9040cbe5402
i2c-s3c2410: prevent mem corruption after i2c timeout

This is a merge of backported changes from
 kernel/exynos android-exynos-3.4

--
  commit 62cb87fd5b32f8cf07bc46a691318f4aa2cfc07d
  i2c-s3c2410: clean up i2c irq after timeout

  Otherwise, later irq handler will try to access freed memory region
  and may crash.

  Change-Id: I0ab9157b6f0d48d3a413e59a27641e88cd9db2eb
  Signed-off-by: Jinhee Hyeon <jh0722.hyen@samsung.com>

  Conflicts:

          drivers/i2c/busses/i2c-s3c2410.c
--
  commit cd668911107bd1432047406e31f3be7278dc4046
  i2c-s3c2410: add missing stop sequence for I2C transfer

  To clearly terminate the connection, clear pending bit and
  serial out disable settings are added

  Change-Id: Ic5ccd80941a724f63ed7f22e777408725c5414ee
  Signed-off-by: HoJune Byun <hjune.byun@samsung.com>

--
  commit 6aeac78519c91d50757dc492ff12fbabc4cc756b
  i2c-s3c2410: I2C connection termination forcely

  To forcely terminate the connection, Serial Out bit is disabled.
  In case of timeout, or HDMIPHY bug

  Change-Id: I29c9ef2b8c35c7c970cbef4d5a856e178794de6e
  Signed-off-by: HoJune Byun <hjune.byun@samsung.com>
--
  commit 2951f354549bf65cf9a4733565841553fbc8a964
  i2c-s3c2410: added STATE_STOP checking codes

  To prevent duplicated stop execution, added STATE_STOP checking codes
  before s3c24xx_i2c_stop function.

  Change-Id: I29417d4dbf94280e1d629338e85e54ad79e6be89
  Signed-off-by: Taekgyun Ko <taeggyun.ko@samsung.com>

  Conflicts:

          drivers/i2c/busses/i2c-s3c2410.c

Change-Id: I78ea9b014ed9656d6b5c4628d36bc8edd668b8e0
Signed-off-by: JP Abgrall <jpa@google.com>
USB: gadget: s3c: Fix isochronous endpoint support in fullspeed mode

isochronous endpoints are not limited to 64 bytes

Signed-off-by: Mike Lockwood <lockwood@google.com>
USB: gadget: f_audio_source: Fix error handling and increase packet size

Fixes watchdog reset on USB disconnect
Larger packet size fixes performance in fullspeed mode

Signed-off-by: Mike Lockwood <lockwood@google.com>
USB: gadget: f_audio_source: Fix use after free in audio_unbind

When USB was disconnected, we were freeing our audio_dev struct in audio_unbind
before the audio system had cleaned up, resulting in a hang in audio_pcm_close.
We now statically allocate the audio_dev struct to avoid this problem.

Change-Id: I58ad21eaa20dcf4aa74ee614ef3b6ed2c91d52a1
Signed-off-by: Mike Lockwood <lockwood@google.com>
USB: gadget: f_audio_source: Fix compilation error

Change-Id: I1b785c47bda03208d396473a9d1c94631f5624d9
Signed-off-by: Mike Lockwood <lockwood@google.com>
netfilter: xt_IDLETIMER: Rename INTERFACE to LABEL in netlink notification.

Signed-off-by: Ashish Sharma <ashishsharma@google.com>
netfilter: xt_qtaguid: report only uid tags to non-privileged processes

In the past, a process could only see its own stats (uid-based summary,
and details).
Now we allow any process to see other UIDs uid-based stats, but still
hide the detailed stats.

Change-Id: I7666961ed244ac1d9359c339b048799e5db9facc
Signed-off-by: JP Abgrall <jpa@google.com>
net: wireless: bcmdhd: Report proper mcs rate mask

Setting proper mcs rate mask allows to connect in 802.11n-only mode

Change-Id: Iffd47a60c92a74d29e42d81d79fa64463f5895c5
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
Update charging animation to match OSS charger

Thanks to stratosk

Change-Id: I0c167afd817ad7ab0bedfab3eabe04469bfd5d32
aries: Use DVFS locks instead of cpufreq policy mangling in pvr.

The pvr driver requires that the memory bus speed is kept fast while the
GPU is active.  Since the memory bus speed is tied to the CPU frequency,
pvr (previously) used a cpufreq notifier called on policy updates to ensure
the CPU is running at a minimum 200 MHz while active.  The problem with
this approach is that any changes to scaling_min_freq while the GPU is
active (e.g., while interacting with the Processor settings menu) get
clamped to 200 MHz, which persists even when the GPU is inactive.

By switching to DVFS locks, changes to scaling_min_freq persist, and so
allows the use of 100 MHz when the GPU is inactive.  Fixes epiccm #14.

Change-Id: I12bf5a6f3cba2da853d5528f4c62a659a1489806
aries-vibrator: add sysfs interface to control vibration intensity

Change-Id: Ia69e9fe28111a36fb9fa32410e54e69f84fbcd57
Merge branch 'android-samsung-3.0-jb-mr0' of https://android.googlesource.com/kernel/samsung into HEAD

Conflicts:
	drivers/gpu/pvr/pvrversion.h

Change-Id: I93433944a5870a934ea7783df66994bffda2673e
Don't require gstat on OSX

stat -f "%z" also works and is more compatible

Change-Id: I1768bd402cbac09117726fc5008b8ab245495aaa
USB: gadget: fascinatemtd only has one lun

Change-Id: I9ba97809da6fdc9ef4c278e50f8ecf6b644d1218
Call cpufreq_update_policy on DVFS events.

Calls cpufreq_update_policy on DVFS lock/unlock events to ensure that DVFS
locks take effect with the governor's preferred frequency (if higher than
the lock frequency).  Previously the lock would set the frequency to the
target level and expect the governor to reevaluate on a timer, which
ondemand does, but powersave and performance do not.

Change-Id: I19a454d7173afdb99d0a87845285f84606cf24e1
config: enable zram and swap

Change-Id: I83264d79eea4b93997552b1361f413fde68d652d
cpufreq: enable and update interactive governor

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>

cpufreq: interactive: add boostpulse duration
This makes up for the portions missing that would've been written
by Narayanan Gopalakrishnan but they were missing (duration, and boost
time) and also adds the ability to set duration (which was originally
created by cyanogen)

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

Change-Id: Iba70ed3580dd04704b0d7b4acde178df7a843b5f
enable 1.2GHz OC

* keep same voltage settings as 1GHz
* properly update APLL values
* set max freq to 1GHz on bootup, up to the user to OC

Change-Id: I643cb1b54dd684b9dbe6066fbdef1a86b9123d79