MIPI TouchSM Specification MIPI Mobile Touch

David Johnson, Qualcomm Technologies,

Inc.

2

Announcing a MIPI Touch

Interface architecture

MOTIVATION FOR MIPI TOUCH Leveraging MIPI Specifications

3

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

Standardizing touch

5

MIPI identified multiple usages for

standard touch and stylus

Build MIPI Touch within

the MIPI ecosystem

❶

❷

Multi-Touch

6

Stylus

7

Automotive

8

SYSTEM TOPOLOGY

9

AP

OSApps

Touchdata

Touchdata

Touchcmdsandcontrols

Instruc2ons

TC/AFE

MIPITouchinterface

MIPITouchso;ware

MIPI Touch / topology

Topology inside the module

•  Point-to-point or

• Multi-drop

11

REQUIREMENTS

12

Power vs. bit rate Requirements

13

nJ/bit

1Mb/s 10Mb/s

5uW 5uW

SOLUTION ARCHITECTURE

14

MIPI Touch Architecture

Page 15

Touch commands

MIPI I3C

I3C profile

OS Touch Driver Stack

Touchspecific2016

I3C drivers 2017

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

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

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

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

PLANNING

20

Execution plan / Schedule

21

2016 AUG SEPT OCT NOV DEC 2017

Dra;s0.2to0.4 Dra;0.5 Dra;0.7 FinalSpecifica2on

CONCLUSIONS AND CALL

22

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

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

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