msm: cpufreq: Only apply driver limits for scaling_min/max_freq writes

When new values are written to scaling_min/max_freq sysfs files, the
current code applies all the limits imposed by various ADJUST and
INCOMPATIBLE notifiers handlers before storing them.

When the ADJUST and/or INCOMPATIBLE notifiers change their limits
frequently, this behavior makes it almost impossible for a
user/userspace process to store the scaling_min/max_freq limits
that go beyond the instantaneous limits imposed by the notifiers.
Since these sysfs nodes are typically meant to set limits that need
to be enforced for the foreseeable future, this is not a very user
friendly behavior.

So, change the behavior to only apply limits that are enforced by
the cpufreq driver. Typically, these are just the absolute limits
of the HW and don't change very often.

Change-Id: I1ccfaa2d1ee4ea595f882485d359dbdb407a0176
Signed-off-by: Deepak Katragadda <dkatraga@codeaurora.org>
Staging: android: timed_gpio: Fix unreg order

Fix the order of unregister timed output device to avoid
use after free bug.

Change-Id: I7b1e51002f17e7cc277db6cf07188e96217ad13c
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
block: Add URGENT request notification support to CFQ scheduler
> > When the scheduler reports to the block layer that there is an urgent
> > request pending, the device driver may decide to stop the transmission
> > of the current request in order to handle the urgent one. This is done
> > in order to reduce the latency of an urgent request. For example:
> > long WRITE may be stopped to handle an urgent READ.
> >
> > Change-Id: I3072b8a1423870fed9c04c28d93caaf9557a7b89
> > Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>