msm_mpdecision: revise sysfs functions and variables

- My testing shows that mpdecision works just fine based only on
  rq_stat load average without checking instantaneous cpu freq.
  Remove the seemingly redundant frequency check for a simpler
  code with less overhead.
- replaced the sysfs store functions with a macro
msm_mpdecision: adjust the hotplug/unplug time thresholds relative to
workqueue delay.

ensure the second core hotplugs ASAP by reducing the hotplug threshold
(90) below workqueue delay (100). msm_mpdecision will have the chance
to bring the second core at every cycle of workqueue. delay unplugging
second core by increasing the unplug threshold (450) above workqueue
delay (100). msm_mpdecision will wait at least five workqueue cycles
before unplugging the extra core after the last hotplug event to avoid
excessive hotplug events.
msm_mpdecision: revise the data structures of time and load limits
this cleans up four unused variables and their sysfs files
Linux 3.0.94
Revert "msm: Add sysfs interface for mfreq"
Remove mfreq sysfs interface as the functionality to boost
CPU clocks to maximum is no longer needed.

This reverts commit c79a2e06447a6253f24142b0143ab9b1b2a1e488.

CRs-Fixed: 335675
Change-Id: Ic6f0ad40e15a0f6c234617a430387517d3556b0c
Signed-off-by: David Ng <dave@codeaurora.org>
cpufreq: interactive: change hispeed_freq with CPUFREQ_GOV_LIMITS
msm: cpufreq: boost freq of online cpu(s) to max on resume
Resume events cause several tasks to initiate such as WiFi connect,
data sync, etc. that require cpu cycles. Instead of waiting for the cpu
governor to increase the cpu frequency which occur after an unpleasant delay,
start at the max frequency and the cpu governor will scale the frequency
back as soon as possible. This shouldn't have any noticeable impact on battery
life.
--mrg666
update config
Linux 3.0.95
update config(s)
shooter_u: fix keypad
cleanup network settings
add localversion
unify shooter_u and shooter header files
cpufreq: interactive: fix show_target_loads and show_above_hispeed_delay

Remove a trailing whitespace from target_loads and above_hispeed_delay. Problem
happens when user-space program tried to restore parameters that saved before
changing parameters. In this case was returned error(EINVAL).

Change-Id: I5a74e3824602cd6f2b74651adda5ec1b627e61e9
Signed-off-by: Minsung Kim <ms925.kim@samsung.com>
workqueue: cond_resched() after processing each work item
commit b22ce2785d97423846206cceec4efee0c4afd980 upstream.

If !PREEMPT, a kworker running work items back to back can hog CPU.
This becomes dangerous when a self-requeueing work item which is
waiting for something to happen races against stop_machine.  Such
self-requeueing work item would requeue itself indefinitely hogging
the kworker and CPU it's running on while stop_machine would wait for
that CPU to enter stop_machine while preventing anything else from
happening on all other CPUs.  The two would deadlock.

Jamie Liu reports that this deadlock scenario exists around
scsi_requeue_run_queue() and libata port multiplier support, where one
port may exclude command processing from other ports.  With the right
timing, scsi_requeue_run_queue() can end up requeueing itself trying
to execute an IO which is asked to be retried while another device has
an exclusive access, which in turn can't make forward progress due to
stop_machine.

Fix it by invoking cond_resched() after executing each work item.

Signed-off-by: Tejun Heo <tj@kernel.org>
Reported-by: Jamie Liu <jamieliu@google.com>
References: http://thread.gmane.org/gmane.linux.kernel/1552567
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 3.0.96