For UP systems this is not required, and results in a more consistent
sample interval.
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Jocelyn Falempe <jocelyn.falempe@motorola.com>
Signed-off-by: Mike Chan <mike@android.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Dave Jones <davej@redhat.com>
(cherry picked from commit a665df9d510bfd5bac5664f436411f921471264a)
(cherry picked from commit 4dcc8b45d5187ea0cea8d85d4a1ba758fa209b67)
Dominik said:
target_freq cannot be below policy->min or above policy->max.
If it were, the whole cpufreq subsystem is broken.
But (answer):
I think the "ondemand" governor can ask for a target frequency that is
below policy->min.
...
A patch such as below may be needed to sanitize the target frequency
requested by "ondemand". The "conservative" governor already has this check:
Signed-off-by: Thomas Renninger <trenn@suse.de>
Signed-off-by: Dave Jones <davej@redhat.com>
# diff -bur x/drivers/cpufreq/cpufreq_ondemand.c.orig y/drivers/cpufreq/cpufreq_ondemand.c
(cherry picked from commit 1dbf58881f307e21a3df4b990a5bea401360d02e)
(cherry picked from commit 5109f7b2bf70d58302b321919860e91976b93993)
ondemand and conservative governors are messing up time units in the
code path where NO_HZ is not enabled and ignore_nice is set. The walltime
idletime stored is in jiffies and nice time calculation is happening in
microseconds.
The problem was reported and diagnosed by Alexander here.
http://marc.info/?l=linux-kernel&m=125752550404513&w=2
The patch below fixes this thinko.
Reported-by: Alexander Miller <Miller@fmi.uni-stuttgart.de>
Tested-by: Alexander Miller <Miller@fmi.uni-stuttgart.de>
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Signed-off-by: Dave Jones <davej@redhat.com>
(cherry picked from commit 54c9a35d9faef06e00e2a941eb8fe674f1886901)
* add health property and remove the state in the structure that kept the values previously
* reduce cache time to 2.5 seconds to make it quicker to respond to AC events
* add supplicants to the mains supply so that when AC detection hits, battery gets poked too
This patch increases the receive buffer size to HCI_MAX_FRAME_SIZE
which improves the RX throughput considerably.
Tested against BRM/Atheros/CSR USB Dongles with PAN profile using
iperf and chariot. This gave significant (around 40%) increase
in performance (increased from 0.8 to 1.5 Mb/s in Sheld room)
Signed-off-by: Vikram Kandukuri <vikram.kandukuri@atheros.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
(cherry picked from commit 290ba200815fdecb4d40dc942499c4ea6d0c4624)
* Make lid switch, power key and wireless switch into a real input device as it was in the deep dark past..
* weird regression: something changed in GNOME, so you can't suspend by dropping the lid (the option has been
removed from gnome-power-preferences). And because if you suspend with the lid up, the lid switch is not set
to wake, lifting the lid won't unsuspend. The only way to get the system back is with the power key. Damn
you GNOME developers.
* weird behavior: smarttop will immediately come back after suspend