Verify Sync with latest INTELLIDEMAND config

Sync with last INTELLIDEMAND_VERSION v3.2

Add LIMIT_MAX_FREQ for Intellidemand

Sync with last INTELLIDEMAND cpufreq governor

Tweak and Fix INTELLIDEMAND

cpufreq_intellidemand.c: Tweak Governor

cpufreq_intellidemand.c: Tweak Governor II

intellidemand: tweaked hysteresis value for better UI response
Add New NIGHTMARE Governor [Hijacked Commit]

cpufreq_nightmare.c: Tweak Governor

cpufreq_nightmare.c: Fix Compile error INIT_DEFERRABLE_WORK

cpufreq_nightmare.c: Fix and Match with AK Kernel
row: Adding support for reinsert already dispatched req

Add support for reinserting already dispatched request back to the
schedulers internal data structures.
The request will be reinserted back to the queue (head) it was
dispatched from as if it was never dispatched.

Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
row: Add support for urgent request handling

This patch add support for handling urgent requests.
ROW queue can be marked as "urgent". If an urgent queue was
un-served in a previous dispatch cycle and a request was added
to it - it will trigger issuing urgent request to the device driver.

Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
block: Add support for reinsert a dispatched req

Add support for reinserting a dispatched request back to the
scheduler's internal data structures.
This capability is used by the device driver when it chooses to
interrupt the current request transmission and execute another (more
urgent) pending request. For example: interrupting long write in order
to handle pending read. The device driver re-inserts the
remaining write request back to the scheduler, to be rescheduled
for transmission later on.

Add API for verifying whether the current scheduler
supports reinserting requests mechanism. If reinsert mechanism isn't
supported by the scheduler, this code path will never be activated.

Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>

Conflicts:
	include/linux/elevator.h
block: Add support for reinsert a dispatched req

This patch add support in block & elevator layers for handling
urgent requests. The decision if a request is urgent or not is taken
by the scheduler. Urgent request notification is passed to the underlying
block device driver (eMMC for example). Block device driver may decide to
interrupt the currently running low priority request to serve the new
urgent request. By doing so READ latency is greatly reduced in read&write
collision scenarios.

Note that if the current scheduler doesn't implement the urgent request
mechanism, this code path is never activated.

Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
Update SIO Scheduler v0.2