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>
Revert "aries: add input boosting to ondemand"

This reverts commit 37c7eacd66fc86103e6e1ec55288b46900186a9c.
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>
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
Revert "drivers: cpufreq: Send a uevent when governor changes"

This reverts commit e74f095b6842c265dc14c99f895b085be4d11d97.
drivers: cpufreq: Send a uevent when governor changes

 * Useful so userspace tools can reconfigure.

Change-Id: Ib423910b8b9ac791ebe81a75bf399f58272f64f2
config: enable zram and swap

Change-Id: I7f920fe433f1f46c8842451eb21f5d69fee6bed2
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
config: add CONFIG_CPU_FREQ_GOV_INTERACTIVE=y

Change-Id: I181528547b870aa26af1ded50253fad8650d7973
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

Signed-off-by: Nikolay <volk204@mail.ru>
Add ability to under- and overvolt.

Patch set 1: original commit
Patch set 2: removed spaces
Patch set 3: increased stock voltage at 1200MHz to 1325mV
Patch set 4: changed UV interface to allow OV with Voltage Control
Patch set 5: spacing
Patch set 6: rebased
Patch set 7: allow higher OV voltage

Change-Id: Ie5f5d8ca7ed64e63b9be0aa088b99c1b8466b605

Signed-off-by: Nikolay <volk204@mail.ru>
s5pc110: Improved OC code

- Set arm_volt_max back to 1350000 as some users are reporting
  SoD without any OC
- Set arm_volt for 1.2 GHz to 1275000 for now, because higher
  values cause SoD for all devices while this works on most
  devices.

(this basically revert values to what they previously were)

Change-Id: Ic01f606a5fc5145ce9d8e8f6961a80262503e0d6

Signed-off-by: Nikolay <volk204@mail.ru>
Merge remote-tracking branch 'remotes/github/jb_test' into jellybean