Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games.
2.Broken line.
3.Two Fingers Tapping Easy Connectivity.
4.co-axis problem with two finger.
Change-Id: I4c906bc612a6184a131e52bc69d4e7d4d0e460c1
Signed-off-by: mars_kao <mars_kao@asus.com>
to avoid unexpected retry command in firmware update mechanism.
[9867254]Need to wait for 20 ms before starting communicate with touch IC for boot-code initialization after the hw reset.
Change-Id: I6ae85336cb98e44f1de0344e4831a670d7a11d47
Signed-off-by: mars_kao <mars_kao@asus.com>
Avoid collision with ac mode for update power source to touch ic.
Change-Id: I5ce03351d8f93cd758c2238d3a6836816385a22b
Signed-off-by: mars_kao <mars_kao@asus.com>
1.upload firmware to A032.
2.modify driver to update power source when use slim port to hdmi.
A032 fix issue:
9471817:Hover touches.
9366206:Device show multiple-ghost touch after connect HDMI and tilt device to 40~65 degree.
9471956:Unclean lift offs.
9471962:Edge swipes causing hooks or missing touch points.
Noise problem.
Add ESD Protection Mechanism.
Change-Id: I4d22ecc4433ae5fd755a6954c6cd4af5062fb0b3
Signed-off-by: mars_kao <mars_kao@asus.com>
Fix following issues:
1.Latency on resume
2.Edge swipes lost (notification panel)
3.[Issue 9284036][FLO]ABS_MT_TOUCH_MAJOR values change
base on number of pointers down
Change-Id: I56e6ba907bf2998ac0dcb84d2f100ab4c8ca72f5
Signed-off-by: javid_shu <Javid_Shu@asus.com>
Need calibration for below Issue:
[Issue 9261425] New touch firmware is needed to apply the new parameters.
Change-Id: Ib80d5a9efbe1ae683ae5731c37c4253dfc926559
Signed-off-by: javid_shu <Javid_Shu@asus.com>
Based on A023 and remove the grip information.
1.[Issue 8840158] [FLO] pinch zoom doesnt seem as responsive / reliable as on nakasi.
2.[Issue 8858019] [FLO] Poor touch resolution.
Need calibration to fix these two issue with ER1/ER2 device:
3.[Issue 9052815] [FLO] Dead "Bands" on the touch screen.
4.[Issue 8930391] Spurious touchscreen taps.
Change-Id: I16084c31a289527f0085b475b9d6ea88ff7f9371
Signed-off-by: mars_kao <mars_kao@asus.com>
1.[8388207]Touch controller to report cluster coordinates to be used for grip suppression.
2.[8858019]Poor touch resolution.
3.[8840158]pinch zoom doesnt seem as responsive / reliable as on nakasi.
Signed-off-by: mars_kao <mars_kao@asus.com>
Fix:
8717455: Holding touch panel edge by one finger,the touch action will be affected.
8768005: Holding Flo along the left edge of the device reveals false touch problems.
8840158: Pinch zoom in and out on chrome and maps doesnt seem as accurate / responsive as on nakasi.
8798827: Touch can not be correct clicked.
customer report: pin unlock will lose touch report.
Modification for AC De-noise Mechanism.
Change-Id: If846956114dc51f8d432c881f7b4e3b78b4040c8
Signed-off-by: mars_kao <mars_kao@asus.com>
1.Fix the Sensitivity Problem That Suspend and Wake up When Charging.
2.Modification for Algorithm, and Digital Parameters for ER Module.
a.Improve "double fat finger (22 phi copper)" performance when charging.
Change-Id: I1f2f5697dd5587243dc77003672c9658213db4b0
Signed-off-by: mars_kao <mars_kao@asus.com>
A011 is the lastest touch firmware and used for factory image.
firmware update history:
A009:
Update boot-code Ver: 60.47 (Do not turn off WDT in IAP process).
Add Self Check Mechanism to enter suspend mode.
Modification Algorithm, and Digital Parameters for ER Module.
a. Improve "double fat finger (22 phi copper)" performance.
b. Improve "fast drawing straight line" performance.
c. Improve "multi-finger in co-axis (8 phi copper)" performance.
d. Improve "under table lamp" performance.
A010:
Modify Calibration Mechanism.
A011:
Modify Open/Short Calibration Mechanism for ESD problem.
Improve Stylus Performance
Change-Id: I4e87e9cc69d81872106c7f7bd95b76dd1f1811c1
Signed-off-by: mars_kao <mars_kao@asus.com>
new boot version 6047 is for resolving the ESD problem.
Change-Id: If596dfb27be613e3b26f13e032c23136e659c4a9
Signed-off-by: mars_kao <mars_kao@asus.com>
follow the new bootcode flow in IC to update touch firmware.
Change-Id: I848714e4c24aaf89eab3337f343b22891ee83d55
Signed-off-by: mars_kao <mars_kao@asus.com>
Also change delay to pollrate_ms. This is for easy integration
with the sensor HALs.
Change-Id: I06e5e1f41caf2cee21ea2b218d672681b24ccd22
Signed-off-by: Orkhan Karimov <okarimov@codeaurora.org>
Signed-off-by: Wentao Xu <wentaox@codeaurora.org>
allow sensor HAL control the power state of gyro sensor, so that sensor is
disabled when not used.
Change-Id: Ib9f8e9761ea518534ffcd06f30de4b8f1f198687
Signed-off-by: Orkhan Karimov <okarimov@codeaurora.org>
Sensor regulator could be still invalid at the time of a system
suspend, this change is to avoid freeing NULL regulators under such
occasion.
Change-Id: Ia520b2516b43feaa3fbbbe30628cc47ee7fad96a
Signed-off-by: Wentao Xu <wentaox@codeaurora.org>
Those attributes used to be writable by world. This change allows
read only access by world.
CRs-Fixed: 382751
Change-Id: I2b37763514a86da9beed3fcb7dcb4706c790e44d
Signed-off-by: Wentao Xu <wentaox@codeaurora.org>
Signed-off-by: Neha Pandey <nehap@codeaurora.org>
This reverts commit 304d9f5172c8c0210e2e29b175e8f68ea8257f69.
low power mode changes are causing issues like,delay in reponse to
touch , and controller is not recognizing the touch events as its
scan rate is also low in low power mode state . since controller is
not recognizing the touch in low power mode state , so only way
for the controller to come out of low power mode is to do multi-touch
and controller responds randomly to one of the touches and comes out
of the low power mode.
Signed-off-by: Sreenivasulu Chalam Charla <sreeniva@codeaurora.org>
Change-Id: I35e0797f819cfbce6630d70af443b96546eacfb5
Signed-off-by: Neha Pandey <nehap@codeaurora.org>
Power key could be in pressed state during boot. Set the flag
to track the press status properly by reading press irq status.
(cherry picked from commit bd38250554df6e70657e6ff42ad63415dbd53f1a)
CRs-fixed: 404018
Signed-off-by: Mohan Pallaka <mpallaka@codeaurora.org>
Change-Id: I1b604b63e53803483d3cc2a7bae0a5e7ed98285b
Signed-off-by: Neha Pandey <nehap@codeaurora.org>
Parse the device tree elements and fill platform
data structure.
Signed-off-by: Mohan Pallaka <mpallaka@codeaurora.org>
(cherry picked from commit d96f5032cd8b73450886262fe193d1531038c0f0)
Conflicts:
drivers/input/touchscreen/atmel_mxt_ts.c
Change-Id: I551dadffaa84c991abbe964bfb9f72b7fd11dfee
Signed-off-by: Sudhir Sharma <sudsha@codeaurora.org>
(cherry picked from commit 368b8d73bbda62f6ab217ef06019b685636fc3ba)
Low pass filter bandwidth is configured to be equal to or greater than
half of the sampling freqency.
Signed-off-by: Wentao Xu <wentaox@codeaurora.org>
(cherry picked from commit 04f4cc9ff3707a39af39c23cc9f3aeb5c344c60c)
Signed-off-by: Sudhir Sharma <sudsha@codeaurora.org>
(cherry picked from commit a7d8fe1d40061ec56c938308d8f7265f29b146c1)
Change-Id: I796d30d474aa64c1679781b38ca5f151b37c92fd
Signed-off-by: Sudhir Sharma <sudsha@codeaurora.org>
There is a possibility of receiving a release interrupt
before press when both these actions (press and release) of the
power-key are very close-by (~1-2ms) to the debounce time
of the key. Handle this case by maintaining a state variable.
Also mark the release interrupt as a wakeup source to
wakeup the system when the above mentioned abnormal case
occurs.
CRs-Fixed: 394289
Change-Id: I74475c1e5159dd30e52aca91243eec7e2fac4d57
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
(cherry picked from commit 306e3197b5cc657a62c41823fb6cd03600d35f3f)
Signed-off-by: Sudhir Sharma <sudsha@codeaurora.org>
Move from multitouch protocol A to protocol B, and since some
applications are not working under BTN_2 reporting, all the instances
of HAT are removed along with BTN_2 reporting.
Change-Id: I25c9c811078452eb9ff11159d0f45c9e3f831849
Signed-off-by: Amy Maloche <amaloche@codeaurora.org>
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
(cherry picked from commit 94f65fcf5d89b7943777750b2e358c7421f26400)
Signed-off-by: Sudhir Sharma <sudsha@codeaurora.org>
Power key could be in pressed state during boot. Set the flag
to track the press status properly by reading press irq status.
CRs-fixed: 404018
Change-Id: I93a8584420002d9cb399484b3ac77fa2ed954690
Signed-off-by: Mohan Pallaka <mpallaka@codeaurora.org>
There is a possibility of receiving a release interrupt
before press when both these actions (press and release) of the
power-key are very close-by (~1-2ms) to the debounce time
of the key. Handle this case by maintaining a state variable.
Also mark the release interrupt as a wakeup source to
wakeup the system when the above mentioned abnormal case
occurs.
CRs-Fixed: 394289
Change-Id: I74475c1e5159dd30e52aca91243eec7e2fac4d57
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
If a timeout is requested, a delayed work item will be
scheduled to restart the device. If the keys are released
before the timeout expires, the reset is aborted.
As expected, the reset_fn can be used to reset the device
after the timeout.
Bug: 7344361
Change-Id: I1d77cdb3dcc63f579b1250506f0a30de1e033d67
Signed-off-by: Dima Zavin <dima@android.com>
- Fixed issues in production test
. ghost touch in high and low temperature
. ghost touch with noisy charger connect
. sensing test
- Stablized thumb operation
- Fixed flapping finger width report
Change-Id: I350ed94b9bfcb5a8feba3e0c9529ea86472097cd
Signed-off-by: Iliyan Malchev <malchev@google.com>
Synaptics firmware maintains internal cache to store a scan of
finger data so that the host reads finger data from this cache.
The firmware updates the cache when the host reads it nonsequentially.
The current driver reads only present finger data, which can cause
unexpected nonsequential access to cache and the cache can be updated
before the host reads the data, resulting in losing finger data coherency.
Modified the driver to access data sequentially even if there are
not present fingers in the middle so that the finger data coherency
can be preserved.
Change-Id: I4b975c2ab2445078f2a81c3dd4ce484002d27933
Signed-off-by: Iliyan Malchev <malchev@google.com>
