Squashed update of kernel from 3.0.78 to 3.0.79
mmc: Remove a not needed mmc_power_off
video: msm: Fix initial state of LCD backlight

 * For devices which use the LCD backlight (such as D2), we need
   to actually call the function which sets the brightness after
   initializing it in the probe.

Change-Id: Id6b7c0de3cd31181394c56c7f6061bca9defd861
msm_fb: display: Add minimum src/dst image size validation for MDP

MDP4 has minimum size restriction for both source and destination
height and width. Add checks to validate source and destination
layer size.

CRs-fixed: 484728
Change-Id: I8cb8d4b969cd6ab2d8e99d7ed2ebb1a4adce1ef3
Signed-off-by: Mayank Chopra <makchopra@codeaurora.org>
Squashed update of kernel from 3.0.79 to 3.0.80
ariesve: Some changes to gp4 voltage regulators to fix touchscreen voltage

These changes allow to prevent these errors when setting touchscreen voltage:
<3>[    0.063964] ldo10: requested voltage range [1800000, 1800000] does not fit within previously voted range: [2600000, 2600000]
<3>[    0.064086] oliver_tsp_ldo_on: vreg LDO2 set level failed (-22)

The touchscreen after getting this error uses the wrong voltage of
2600000 uV instead of 18000000 uV.

The regulator's core has been changed and the voltage range that doesn't
fit the previously set voltage range is not allowed, so we need to correct
the other occurrences where gp4 regulator has been registered.
ariesve: Some changes to the touchscreen power-on routine
ariesve: Moved the config_gpio_table method outside of the CONFIG_MSM_CAMERA block

This method is used by other drivers init methods
ariesve: Fixed some warnings reported during board compilation
mmc: msm_sdcc: fix a type mismatch in msmsdccc_config_dma()

msmsdcc_prep_xfer() function returns a signed integer value but
caller function msmsdcc_config_dma() is storing this value in an unsigned
integer variable which is obviously not the correct thing to do.

CRs-Fixed: 476578
Change-Id: I39159e2f4f73c7f54de359cbe4faba5e902915ff
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
msm: kgsl: Don't consider active count if not in active state

Don't consider active_cnt variable if not already in ACTIVE state.
The active count variable does not necessarily exactly indicate the
number of open handles to GPU for switching power state. Hence,
only wait for active count to reach zero before switching to SUSPEND
state if, the current state is ACTIVE.

CRs-fixed: 483154
Change-Id: Ie025a1873cfb9237bdfba89204f4c2116549eba4
Signed-off-by: Harsh Vardhan Dwivedi <hdwivedi@codeaurora.org>
Squashed update of kernel from 3.0.79 to 3.0.80