defconfig: enable SD card detection retries
latona: atmel: don't set any MXT_SPT_GPIOPWM value
drivers: max17040_battery: force RCOMP value

Taken from latona 2.6.35.
Without this patch the RCOMP value is set to d01e.
drivers: leds: latona: code cleanup and fixes

 * Let LEDs be turned off from the userspace
 * Turn both the LEDs on when softkeys are touched
 * Keep LEDs on while touching
panel: latona: set brightness to zero while turning on Hitachi panels

It was observed that Hitachi panels rarely set high brightness
values when they are turned on for a very short time.
Set the brightness to zero while they are powered on as it's done
for all the other panels to prevent this.
panel: latona: limit only Hitachi(17mA) panels

The changes were tested only on Hitachi(20mA). In old sources drop, where
Hitachi(17mA) panels are not mentioned, there are no limits.

Rework also the algorithm to limit the brightness to have a linear increase.
panel: latona: declare several functions as static
latona: properly remove the bus tput constraint
mach: opp: restore voltages
initramfs: don't create /emmc

It breaks the symlink for backward compatibility.
The directory is created whenever required.
latona: update C-state latencies and thresholds

Enable only the energy-wise interesting C-states.

For detailed information, refer to:
http://www.omappedia.org/wiki/Power_Management_Device_Latencies_Measurement#cpuidle_results
fbearlysuspend: add delay to properly play screen off animations
usb: fixup multiple luns [reworked]
Revert changes for asynchronous compaction

Revert "drivers: staging: android: lmk compile fixup"

This reverts commit dcf48969dc931cd22609472879fe2befaeca4421.

------
Revert "lowmemorykiller: Use asynchronous compaction"

This reverts commit 073a0da1ddc39cca52253da5eb3284cea4756d71.

-----
Revert "lowmemorykiller: Compact memory when killing processes"

This reverts commit 35f477281c55d72bf6530edbeacb4dcfd1836c44.
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.

Change-Id: I5c982a66b651ebf544aae60063ac8a340d79e67f
Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
block: Add API for urgent request handling

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.

Change-Id: I8aa74b9b45c0d3a2221bd4e82ea76eb4103e7cfa
Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
block: Add ROW I/O Scheduler by Qualcomm

Change-Id: Icf563116d3c2a4ffd2bd65eb061dceb96052737c
defconfig: enable ROW and use it as default scheduler
cpufreq: ondemand: add boostpulse interface

Squashed commit consisting of the following:
--------
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.

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

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.

drivers: cpufreq: Add max duration for boosting

* Don't allow boosting for more than 5 seconds.

From: Steve Kondik<shade@chemlab.org>
--------
cpufreq: ondemand: Default to max

From: Daniel Bateman<jetison.24@gmail.com>
--------
Change-Id: Ib272703616b9dabc9ab54221f6e2c84c9e9c6dda
latona: reduce spam messages in kernel logs [3]