debugging on capacitive touch screen

最新推荐文章于 2018-03-12 10:12:55 发布

零矩科技

最新推荐文章于 2018-03-12 10:12:55 发布

阅读量471

点赞数

CC 4.0 BY-SA版权

分类专栏： android 文章标签： debugging caching android ui up c

本文链接：https://blog.youkuaiyun.com/flybirdlong/article/details/4595997

android 专栏收录该内容

9 篇文章

订阅专栏

本文针对新进入市场的初级供应商开发人员提供了触控驱动开发的经验分享。主要内容包括：Android UI处理触摸点的方法已成熟，无需质疑上层应用；准确调整工作需由供应商完成且应尽早进行；解决I2C问题，确保遵循Marvell规范；清除触控面板发送到内核的错误点；优化内核以提高触控输入方法的性能。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

if you are the engineer for develop driver with a vendor who just enter into this area (junior vendor), the following experience might help.

1. android UI which handle the touch points is pretty mature. so don't quest on the up level applications.

2. all the accurate adjustment must be done by the vendor.

3. the request of 2. should be early done by vendor as possible.

Performance debugging.

1. I2C issues, touch pannel vendor should make sure all the time sequencing following the spec of Marvell.

the vendor is lazy doing on this, make sure the HW engineer stare at this

2. the touch pannel sometimes send wrong point to kernel, so vendor has responsibility to clear out the mistake point.

3. Kernel optimizing: a. the points should be around 50-60 every second enough for touch imput method, make sure the point sent by kernel satify this requirement.

b. turn on cpu caching config (PXA935 have this option, 310 dont)

c. raise cpu speed to highest when touch happen and restore it back when figure leaves (pxa935 cpu speed automatic adjusts by itself)