leds: hardcode max_current

Instead of relying to scripts to set the max_current at boot time, hardcode the values in the drivers like it was done for zeus board

Change-Id: Ia92a0b0193803fefb3f32569e0414604855c64e9
Signed-off-by: Michael Bestas <mikeioannina@gmail.com>
leds: regrant users access to leds' real safe max current

This extends the patch for hardcoded stock values.
With only it the users can't go above stock values, even though the leds are made to work
on bigger currents between 20-25mA.

This commit fixes it and lets users again to reach hardware's max safe current through scripts and also maintains OEMs' stock values if no script is used.

Signed-off-by: Konstantinos Missos <ctcaer@gmail.com>
anzu: fix ALS

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: Ib3e13b745c422848ef12e4063673f057fdbf849e
Merge pull request #28 from mikeNG/led-fixes

Led fixes
defconfig: update with recent changes
urushi: don't undervolt LCD but undervolt touch
Import TI_ST related drivers from kernel 3.8

Thanks to @M66B

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: I2c7703aa43109de2a9d490e2559e015a5ec9b492
Import UHID driver from kernel 3.8

Thanks to @M66B

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: Ida53032d65b1f09a77195b86320536d2d053cd7c
Adapt TI bluedroid stack for mogami board

Thanks @M66B & @pcfighter

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: I80c585ebecb1bc09036b747d2f22402b0468f176
mogami: remove old rfkill implementation

BT is managed by BT_WILINK & TI_ST drivers now

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: I629c8b098ee85a8b4248d7d3eacada43360dd5f0
mogami defconfigs: Enable BT_WILINK & TI_ST for JB MR1 BlueDroid stack

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: Ic8d0b1e9d5f7e5fd6547a9f5cfe310028c7a12a4
mogami defconfigs: Enable UHID driver

Signed-off-by: Michael Bestas <mikeioannina@gmail.com>

Change-Id: I930a41ad6bb29cf660536e605f2705c106f6337b