Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

MIPI DevCon 2016: MIPI Mobile Touch Specification

676 views

Published on

David Johnson of Qualcomm Technologies presents an overview of the forthcoming MIPI Touch specification, which will provide a comprehensive touch interface for use in mobile phones, tablets, automotive dashboards and infotainment displays, and other devices and applications.

Published in: Mobile
  • Be the first to comment

  • Be the first to like this

MIPI DevCon 2016: MIPI Mobile Touch Specification

  1. 1. MIPI TouchSM Specification MIPI Mobile Touch David Johnson, Qualcomm Technologies, Inc.
  2. 2. 2 Announcing a MIPI Touch Interface architecture
  3. 3. MOTIVATION FOR MIPI TOUCH Leveraging MIPI Specifications 3
  4. 4. Current Industry Touch Status •  Non-standard Software Command Set •  Multiple Interfaces use a non-standard protocol •  SPI •  I2C •  Not optimized •  low-power mobile performance •  low-cost pin-count interfaces •  Require more touch bandwidth 4
  5. 5. Standardizing touch 5 MIPI identified multiple usages for standard touch and stylus Build MIPI Touch within the MIPI ecosystem ❶ ❷
  6. 6. Multi-Touch 6
  7. 7. Stylus 7
  8. 8. Automotive 8
  9. 9. SYSTEM TOPOLOGY 9
  10. 10. AP OS Apps Touch data Touch data Touch cmds and controls Instruc2ons TC/AFE MIPI Touch interface MIPI Touch so;ware MIPI Touch / topology
  11. 11. Topology inside the module •  Point-to-point or •  Multi-drop 11
  12. 12. REQUIREMENTS 12
  13. 13. Power vs. bit rate Requirements 13 nJ/bit 1 Mb/s 10 Mb/s 5uW 5uW
  14. 14. SOLUTION ARCHITECTURE 14
  15. 15. MIPI Touch Architecture Page 15 Touch commands MIPI I3C I3C profile OS Touch Driver Stack Touch specific 2016 I3C drivers 2017
  16. 16. Touch Architecture Benefits •  Standardized Command Set •  OS agnostic and OS independent •  Reduced effort for software development •  A two-way street for sensing and feedback •  Supports any touch or pen data •  MIPI Touch uses the new MIPI I3CSM 16
  17. 17. MIPI Touch Leverages MIPI I3C •  Optimized for speed and power •  Pin-optimized using in-band interrupt eliminated GPIO interrupts •  Robust protocols for bus management •  Improved bandwidth 17
  18. 18. Example Touch Commands •  Power Configuration Commands •  Software RESET •  Configure Normal/Idle/Power Mode •  Self-Diagnostic Functions •  General Proprietary Raw and Processed Touch Report Functions •  Get raw and processed touch data •  Proprietary Touch Command Set (PCS) Categories •  Get/Set Proprietary Commands 18
  19. 19. Cross-functional support for MIPI Touch •  MIPI Software Working Group alignment for drivers and OS compatibility •  MIPI Sensor Working Group collaboration for I3C compatibility •  Universal Stylus Initiative (USI) liaison for active stylus and touch data comparisons •  OS independence through alignment of relevant OS and compatibility requirements 19
  20. 20. PLANNING 20
  21. 21. Execution plan / Schedule 21 2016 AUG SEPT OCT NOV DEC 2017 Dra;s 0.2 to 0.4 Dra; 0.5 Dra; 0.7 Final Specifica2on
  22. 22. CONCLUSIONS AND CALL 22
  23. 23. Conclusions •  Standard open software •  Touch profiles simplifies design for touch •  Standard commands speed TTM •  MIPI I3C is optimized for speed/power •  MIPI I3C has in-band interrupts no extra “IRQ” pins 23
  24. 24. Next Steps •  Join the MIPI Display Working Group to engage with experts on touch specifications •  Start implementations of MIPI I3C •  Did you miss the MIPI I3C presentation? great intro 24
  25. 25. Acknowledgements The author wishes to thank the Display Working Group Touch team and in particular the following contributors and reviewers of this presentation’s content, Robert Gough and Nobu Suzuki, Intel Corporation, Peter Lefkin and Laura Nixon, MIPI Alliance, Paul Kimmelman, NXP, James Goel, and Radu Pitogoi-Aron, Qualcomm Technologies, Inc., Dale Stolitzka, Samsung Display Co., Jeff Lukanc, Synaptics, Inc. 25

×