diff options
| author | Dima Zavin <dima@android.com> | 2011-10-20 00:57:58 -0700 |
|---|---|---|
| committer | Dima Zavin <dima@android.com> | 2011-10-20 00:57:58 -0700 |
| commit | 26f37f3f105a898d3597e730b47fdea6234513c7 (patch) | |
| tree | cba3f7ed5d80f82c13dd049f4e0cc516a05ddfa9 /mms144_ts_rev32.fw | |
| parent | eb95f5295e47f15b8b2b8ea6c570e240b6a3042d (diff) | |
| download | device_samsung_tuna-26f37f3f105a898d3597e730b47fdea6234513c7.zip device_samsung_tuna-26f37f3f105a898d3597e730b47fdea6234513c7.tar.gz device_samsung_tuna-26f37f3f105a898d3597e730b47fdea6234513c7.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_rev32.fw')
| -rw-r--r-- | mms144_ts_rev32.fw | bin | 31760 -> 31760 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/mms144_ts_rev32.fw b/mms144_ts_rev32.fw Binary files differindex 0eae9fc..66b0650 100644 --- a/mms144_ts_rev32.fw +++ b/mms144_ts_rev32.fw |