summaryrefslogtreecommitdiffstats
path: root/mms144_ts_rev31.fw
diff options
context:
space:
mode:
authorDima Zavin <dima@android.com>2011-10-20 00:57:58 -0700
committerDima Zavin <dima@android.com>2011-10-20 00:57:58 -0700
commit4d03b36780d6563c0aa331cf653fa785510d12c8 (patch)
treeafc0a430525609eaf760d0af388306dbf0721370 /mms144_ts_rev31.fw
parent7a66efed63ad63761d29827d472b4541703280d6 (diff)
downloaddevice_samsung_tuna-4d03b36780d6563c0aa331cf653fa785510d12c8.zip
device_samsung_tuna-4d03b36780d6563c0aa331cf653fa785510d12c8.tar.gz
device_samsung_tuna-4d03b36780d6563c0aa331cf653fa785510d12c8.tar.bz2
tuna: update touch firmware to version 0x57/0x37
Updates are described below. - Suspend/Resume handling has been modified due to i2c failure on wake-up state. We have de-glitch function on SCL/SDA implemented which should be turned off on sleep mode. (de-glitch is activated by internal oscillator and can't be produced while we turn off oscillator at sleep mode) Problem might has been caused by toggling de-glitch function on/off when i2c communicate was on process. And I think sleep/wake-up command could not be received at instance at normal condition, but I scoped a signal transmitted to IC that is composed of sleep command and wake up command within 150us, which could cause IC trouble for handling toggling de-glitch function. Added an hardwired i2c reset command, right after toggling de-glitch(sleep/wake-up) to prevent i2c failure. Change-Id: I8512ba7b33485817dc4386c765b6f4228233da8d
Diffstat (limited to 'mms144_ts_rev31.fw')
-rw-r--r--mms144_ts_rev31.fwbin31760 -> 31760 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/mms144_ts_rev31.fw b/mms144_ts_rev31.fw
index 07c5699..1c9a061 100644
--- a/mms144_ts_rev31.fw
+++ b/mms144_ts_rev31.fw
Binary files differ