[PORT FROM R2] atmel_mxt224: change idle acquisition interval back to 32ms

BZ: 20572

Idle acquisition interval can impact power consumption for idle-display-on
case on our platform. The 25mW interval consumes ~14mW, while 32ms
consumes ~7mW and can still maintain the user experience, no touch delay
from idle to active.

Change-Id: I5277eb4d9a00f10ba15960a080831d9753f39dc8
Orig-Change-Id: Ic0b60816bd710b8c80e2dc6f1cf5e538fcda7f49
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34461
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

diff --git a/drivers/input/touchscreen/atmel_mxt224.c b/drivers/input/touchscreen/atmel_mxt224.c
index 6b9c4ee..04eab9e 100644 (file)
--- a/drivers/input/touchscreen/atmel_mxt224.c
+++ b/drivers/input/touchscreen/atmel_mxt224.c
@@ -54,7 +54,7 @@ void mxt_late_resume(struct early_suspend *h);
 #endif
 
 #define DRIVER_VERSION "0.9a"
-#define MXT_CONFIG_VERSION 7
+#define MXT_CONFIG_VERSION 8
 
 #define MXT_BACKNVM_DELAY 25 /* ms */
 #define MXT_RESET_DELAY   65 /* ms */
@@ -258,7 +258,7 @@ void mxt_config_init(struct mxt_data *mxt)
         * Please refer to "mXT224 Firmware 2.x Protocol Guide" for
         * the meaning of the config data for each object.
         */
-       u8 v20_T7[]  = { 25, 10, 50 };
+       u8 v20_T7[]  = { 32, 10, 50 };
        u8 v20_T8[]  = { 6, 0, 5, 5, 0, 0, 5, 50, 5, 192 };
        u8 v20_T9[]  = { 143, 0, 0, 18, 11, 1, 32, 65, 2, 1, 0, 3, 5,
                         0, 2, 10, 35, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0,