[Blaze] Added enable feature for Ambient Light sensor

Added enable functions for Ambient Light Sensor to bh170gli.c

Change-Id: Icbb18e3191c942fc8f93158b82718e7f655b503d
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>
OMAP4: Workaround to avoid Long Key Press to resume from suspend.

TWL PIH interrupt gets enabled earlier than the module level interrupts.
KeyPress has 2 events. Press and Release event for each Key press. There
is only bit in the Register which maintains  both the status.
Due to delay in interrupt enabling  we are loosing Press event interrupts.
This patch maintains the prev state of keyevent. If current event is
same as prev event we provide press/release event to the upper layer.

Change-Id: I01808c7a52e62c951b8da178b02e1a5f9edb3b03
Signed-off-by: Sivakumar Pothireddy <sivakumar.pothireddy@ti.com>
Signed-off-by: Rajeev Kulkarni <rajeevk@ti.com>
OMAP4:To Fix the Slow Resume during first suspend

The below patch gave a workaround to avoid Long Key Press to resume
from suspend
http://review.omapzoom.org/#change,17913
But after reboot if we go to suspend without pressing the power key
i.e. waiting for timeout, then its not resuming normally.
So with this patch, if its first time we provide press/release
event to the upper layer.

Change-Id: If4d44adcc3e95bdaf8a5eec16b3a7561ae8a7b2a
Signed-off-by: Siva Pothireddy <sivakumar.pothireddy@ti.com>
OMAP4: hack for device is not resuming after suspend

The device is not resumed, in the case if "POWERON" button was
pressed for short time. The algorithm is following:
1. Device is resumed, and system reads the reason of resuming
from TWL status registers. But user releases the "POWERON"
button while system is in resume process. See pic1 and pic2
                          ___
   pic1                  |   |
real button state       /|\ \|/
                 ________|   |___________

   pic2                       |   |
system receive               \|/ \|/
following state  _____________|___|______

      |                            |
     /|\                          \|/
where | is button pressed state    | is button released state

2.We are read the cause of resume and get "button released".
3.After that we get second interrupt "Button released", because
button was really released and second interrupt was happened.
See pic2.
In this situation the system sees this, like two pairs
of "pressButton/releaseButton".
The patch removes a second "pressButton/releaseButton".

Change-Id: Ieec7227db19ed43f7964159169eee44386d7d511
Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
Signed-off-by: Sergii Postulga <x0153364@ti.com>
[Blaze] Kconfig:Add build flag for SFH7741 proximity for 4430 blaze

Added the SFH7741 build flags for the proximity driver

Change-Id: Ifca849bbc78d1541090c09934e146b86266d974f
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>

Conflicts:
	arch/arm/mach-omap2/Kconfig
[Blaze] HMC5843 Digital Compass:Port HMC5843 k39 driver to k3.0

Port HMC5843 k39 driver to k3.0

Change-Id: I7c56afa3884cc451bab4931d179bb76f7ab425d6
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>

Conflicts:
	drivers/input/misc/Makefile
[Tablet] TSL2771 Prox/ALS:Port TSL2771 k35 driver to k3.0

Port TSL2771 k35 driver to k3.0

Change-Id: Ib35625999528711ce110e716401326d053185ffa
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>

Conflicts:
	drivers/input/misc/Kconfig
	drivers/input/misc/Makefile
[Tablet] MPU3050 Gyro:Port MPU3050 k35 driver to k3.0

Port MPU3050 k35 driver to k3.0

Change-Id: I574b4b42626b61bbd915fc6899505032f7492727
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>

Conflicts:
	drivers/input/misc/Kconfig
[Tablet] BMA180 Accelerometer:Port BMA180 k35 driver to k3.0

Port BMA180 k35 driver to k3.0

Change-Id: Ic018de4ae42db15ff50834fe726d2a77e9618678
Signed-off-by: Arthur Philpott <arthur.philpott@ti.com>

Conflicts:
	drivers/input/misc/Kconfig