sphinx.addnodesdocument)}( rawsource children]( translations
LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba
attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget./translations/zh_CN/input/multi-touch-protocolmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah }(h ]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/zh_TW/input/multi-touch-protocolmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah }(h ]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/it_IT/input/multi-touch-protocolmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah }(h ]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/ja_JP/input/multi-touch-protocolmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah }(h ]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/ko_KR/input/multi-touch-protocolmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah }(h ]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/pt_BR/input/multi-touch-protocolmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah }(h ]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget./translations/sp_SP/input/multi-touch-protocolmodnameN classnameN refexplicituh1hhh ubeh }(h ]h ]h"]h$]h&]current_languageEnglishuh1h
hh _documenthsourceNlineNubhcomment)}(h4This data file has been placed in the public domain.h]h4This data file has been placed in the public domain.}hhsbah }(h ]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhho/srv/docbuild/lib/venvs/build-kernel-docs/lib64/python3.9/site-packages/docutils/parsers/rst/include/isonum.txthKubh)}(hDerived from the Unicode character mappings available from
.
Processed by unicode2rstsubs.py, part of Docutils:
.h]hDerived from the Unicode character mappings available from
.
Processed by unicode2rstsubs.py, part of Docutils:
.}hhsbah }(h ]h ]h"]h$]h&]hhuh1hhhhhhhhKubhsubstitution_definition)}(h*.. |amp| unicode:: U+00026 .. AMPERSANDh]h&}hhsbah }(h ]h ]h"]ampah$]h&]uh1hhhhKhhhhubh)}(h+.. |apos| unicode:: U+00027 .. APOSTROPHEh]h'}hhsbah }(h ]h ]h"]aposah$]h&]uh1hhhhKhhhhubh)}(h).. |ast| unicode:: U+0002A .. ASTERISKh]h*}hhsbah }(h ]h ]h"]astah$]h&]uh1hhhhK hhhhubh)}(h+.. |brvbar| unicode:: U+000A6 .. BROKEN BARh]h¦}hj sbah }(h ]h ]h"]brvbarah$]h&]uh1hhhhK
hhhhubh)}(h0.. |bsol| unicode:: U+0005C .. REVERSE SOLIDUSh]h\}hj sbah }(h ]h ]h"]bsolah$]h&]uh1hhhhK hhhhubh)}(h*.. |cent| unicode:: U+000A2 .. CENT SIGNh]h¢}hj# sbah }(h ]h ]h"]centah$]h&]uh1hhhhK hhhhubh)}(h&.. |colon| unicode:: U+0003A .. COLONh]h:}hj2 sbah }(h ]h ]h"]colonah$]h&]uh1hhhhK
hhhhubh)}(h&.. |comma| unicode:: U+0002C .. COMMAh]h,}hjA sbah }(h ]h ]h"]commaah$]h&]uh1hhhhKhhhhubh)}(h... |commat| unicode:: U+00040 .. COMMERCIAL ATh]h@}hjP sbah }(h ]h ]h"]commatah$]h&]uh1hhhhKhhhhubh)}(h/.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGNh]h©}hj_ sbah }(h ]h ]h"]copyah$]h&]uh1hhhhKhhhhubh)}(h... |curren| unicode:: U+000A4 .. CURRENCY SIGNh]h¤}hjn sbah }(h ]h ]h"]currenah$]h&]uh1hhhhKhhhhubh)}(h0.. |darr| unicode:: U+02193 .. DOWNWARDS ARROWh]h↓}hj} sbah }(h ]h ]h"]darrah$]h&]uh1hhhhKhhhhubh)}(h,.. |deg| unicode:: U+000B0 .. DEGREE SIGNh]h°}hj sbah }(h ]h ]h"]degah$]h&]uh1hhhhKhhhhubh)}(h... |divide| unicode:: U+000F7 .. DIVISION SIGNh]h÷}hj sbah }(h ]h ]h"]divideah$]h&]uh1hhhhKhhhhubh)}(h,.. |dollar| unicode:: U+00024 .. DOLLAR SIGNh]h$}hj sbah }(h ]h ]h"]dollarah$]h&]uh1hhhhKhhhhubh)}(h,.. |equals| unicode:: U+0003D .. EQUALS SIGNh]h=}hj sbah }(h ]h ]h"]equalsah$]h&]uh1hhhhKhhhhubh)}(h1.. |excl| unicode:: U+00021 .. EXCLAMATION MARKh]h!}hj sbah }(h ]h ]h"]exclah$]h&]uh1hhhhKhhhhubh)}(h9.. |frac12| unicode:: U+000BD .. VULGAR FRACTION ONE HALFh]h½}hj sbah }(h ]h ]h"]frac12ah$]h&]uh1hhhhKhhhhubh)}(h<.. |frac14| unicode:: U+000BC .. VULGAR FRACTION ONE QUARTERh]h¼}hj sbah }(h ]h ]h"]frac14ah$]h&]uh1hhhhKhhhhubh)}(h;.. |frac18| unicode:: U+0215B .. VULGAR FRACTION ONE EIGHTHh]h⅛}hj sbah }(h ]h ]h"]frac18ah$]h&]uh1hhhhKhhhhubh)}(h?.. |frac34| unicode:: U+000BE .. VULGAR FRACTION THREE QUARTERSh]h¾}hj sbah }(h ]h ]h"]frac34ah$]h&]uh1hhhhKhhhhubh)}(h>.. |frac38| unicode:: U+0215C .. VULGAR FRACTION THREE EIGHTHSh]h⅜}hj sbah }(h ]h ]h"]frac38ah$]h&]uh1hhhhK hhhhubh)}(h=.. |frac58| unicode:: U+0215D .. VULGAR FRACTION FIVE EIGHTHSh]h⅝}hj" sbah }(h ]h ]h"]frac58ah$]h&]uh1hhhhK hhhhubh)}(h>.. |frac78| unicode:: U+0215E .. VULGAR FRACTION SEVEN EIGHTHSh]h⅞}hj1 sbah }(h ]h ]h"]frac78ah$]h&]uh1hhhhK hhhhubh)}(h2.. |gt| unicode:: U+0003E .. GREATER-THAN SIGNh]h>}hj@ sbah }(h ]h ]h"]gtah$]h&]uh1hhhhK hhhhubh)}(h9.. |half| unicode:: U+000BD .. VULGAR FRACTION ONE HALFh]h½}hjO sbah }(h ]h ]h"]halfah$]h&]uh1hhhhK hhhhubh)}(h/.. |horbar| unicode:: U+02015 .. HORIZONTAL BARh]h―}hj^ sbah }(h ]h ]h"]horbarah$]h&]uh1hhhhK!hhhhubh)}(h'.. |hyphen| unicode:: U+02010 .. HYPHENh]h‐}hjm sbah }(h ]h ]h"]hyphenah$]h&]uh1hhhhK"hhhhubh)}(h:.. |iexcl| unicode:: U+000A1 .. INVERTED EXCLAMATION MARKh]h¡}hj| sbah }(h ]h ]h"]iexclah$]h&]uh1hhhhK#hhhhubh)}(h7.. |iquest| unicode:: U+000BF .. INVERTED QUESTION MARKh]h¿}hj sbah }(h ]h ]h"]iquestah$]h&]uh1hhhhK$hhhhubh)}(hJ.. |laquo| unicode:: U+000AB .. LEFT-POINTING DOUBLE ANGLE QUOTATION MARKh]h«}hj sbah }(h ]h ]h"]laquoah$]h&]uh1hhhhK%hhhhubh)}(h0.. |larr| unicode:: U+02190 .. LEFTWARDS ARROWh]h←}hj sbah }(h ]h ]h"]larrah$]h&]uh1hhhhK&hhhhubh)}(h3.. |lcub| unicode:: U+0007B .. LEFT CURLY BRACKETh]h{}hj sbah }(h ]h ]h"]lcubah$]h&]uh1hhhhK'hhhhubh)}(h;.. |ldquo| unicode:: U+0201C .. LEFT DOUBLE QUOTATION MARKh]h“}hj sbah }(h ]h ]h"]ldquoah$]h&]uh1hhhhK(hhhhubh)}(h).. |lowbar| unicode:: U+0005F .. LOW LINEh]h_}hj sbah }(h ]h ]h"]lowbarah$]h&]uh1hhhhK)hhhhubh)}(h1.. |lpar| unicode:: U+00028 .. LEFT PARENTHESISh]h(}hj sbah }(h ]h ]h"]lparah$]h&]uh1hhhhK*hhhhubh)}(h4.. |lsqb| unicode:: U+0005B .. LEFT SQUARE BRACKETh]h[}hj sbah }(h ]h ]h"]lsqbah$]h&]uh1hhhhK+hhhhubh)}(h;.. |lsquo| unicode:: U+02018 .. LEFT SINGLE QUOTATION MARKh]h‘}hj sbah }(h ]h ]h"]lsquoah$]h&]uh1hhhhK,hhhhubh)}(h/.. |lt| unicode:: U+0003C .. LESS-THAN SIGNh]h<}hj sbah }(h ]h ]h"]ltah$]h&]uh1hhhhK-hhhhubh)}(h+.. |micro| unicode:: U+000B5 .. MICRO SIGNh]hµ}hj! sbah }(h ]h ]h"]microah$]h&]uh1hhhhK.hhhhubh)}(h+.. |middot| unicode:: U+000B7 .. MIDDLE DOTh]h·}hj0 sbah }(h ]h ]h"]middotah$]h&]uh1hhhhK/hhhhubh)}(h/.. |nbsp| unicode:: U+000A0 .. NO-BREAK SPACEh]h }hj? sbah }(h ]h ]h"]nbspah$]h&]uh1hhhhK0hhhhubh)}(h).. |not| unicode:: U+000AC .. NOT SIGNh]h¬}hjN sbah }(h ]h ]h"]notah$]h&]uh1hhhhK1hhhhubh)}(h,.. |num| unicode:: U+00023 .. NUMBER SIGNh]h#}hj] sbah }(h ]h ]h"]numah$]h&]uh1hhhhK2hhhhubh)}(h).. |ohm| unicode:: U+02126 .. OHM SIGNh]hΩ}hjl sbah }(h ]h ]h"]ohmah$]h&]uh1hhhhK3hhhhubh)}(h;.. |ordf| unicode:: U+000AA .. FEMININE ORDINAL INDICATORh]hª}hj{ sbah }(h ]h ]h"]ordfah$]h&]uh1hhhhK4hhhhubh)}(h<.. |ordm| unicode:: U+000BA .. MASCULINE ORDINAL INDICATORh]hº}hj sbah }(h ]h ]h"]ordmah$]h&]uh1hhhhK5hhhhubh)}(h-.. |para| unicode:: U+000B6 .. PILCROW SIGNh]h¶}hj sbah }(h ]h ]h"]paraah$]h&]uh1hhhhK6hhhhubh)}(h-.. |percnt| unicode:: U+00025 .. PERCENT SIGNh]h%}hj sbah }(h ]h ]h"]percntah$]h&]uh1hhhhK7hhhhubh)}(h*.. |period| unicode:: U+0002E .. FULL STOPh]h.}hj sbah }(h ]h ]h"]periodah$]h&]uh1hhhhK8hhhhubh)}(h*.. |plus| unicode:: U+0002B .. PLUS SIGNh]h+}hj sbah }(h ]h ]h"]plusah$]h&]uh1hhhhK9hhhhubh)}(h0.. |plusmn| unicode:: U+000B1 .. PLUS-MINUS SIGNh]h±}hj sbah }(h ]h ]h"]plusmnah$]h&]uh1hhhhK:hhhhubh)}(h+.. |pound| unicode:: U+000A3 .. POUND SIGNh]h£}hj sbah }(h ]h ]h"]poundah$]h&]uh1hhhhK;hhhhubh)}(h... |quest| unicode:: U+0003F .. QUESTION MARKh]h?}hj sbah }(h ]h ]h"]questah$]h&]uh1hhhhKhhhhubh)}(h1.. |rarr| unicode:: U+02192 .. RIGHTWARDS ARROWh]h→}hj sbah }(h ]h ]h"]rarrah$]h&]uh1hhhhK?hhhhubh)}(h4.. |rcub| unicode:: U+0007D .. RIGHT CURLY BRACKETh]h}}hj/ sbah }(h ]h ]h"]rcubah$]h&]uh1hhhhK@hhhhubh)}(h<.. |rdquo| unicode:: U+0201D .. RIGHT DOUBLE QUOTATION MARKh]h”}hj> sbah }(h ]h ]h"]rdquoah$]h&]uh1hhhhKAhhhhubh)}(h0.. |reg| unicode:: U+000AE .. REGISTERED SIGNh]h®}hjM sbah }(h ]h ]h"]regah$]h&]uh1hhhhKBhhhhubh)}(h2.. |rpar| unicode:: U+00029 .. RIGHT PARENTHESISh]h)}hj\ sbah }(h ]h ]h"]rparah$]h&]uh1hhhhKChhhhubh)}(h5.. |rsqb| unicode:: U+0005D .. RIGHT SQUARE BRACKETh]h]}hjk sbah }(h ]h ]h"]rsqbah$]h&]uh1hhhhKDhhhhubh)}(h<.. |rsquo| unicode:: U+02019 .. RIGHT SINGLE QUOTATION MARKh]h’}hjz sbah }(h ]h ]h"]rsquoah$]h&]uh1hhhhKEhhhhubh)}(h-.. |sect| unicode:: U+000A7 .. SECTION SIGNh]h§}hj sbah }(h ]h ]h"]sectah$]h&]uh1hhhhKFhhhhubh)}(h*.. |semi| unicode:: U+0003B .. SEMICOLONh]h;}hj sbah }(h ]h ]h"]semiah$]h&]uh1hhhhKGhhhhubh)}(h,.. |shy| unicode:: U+000AD .. SOFT HYPHENh]h}hj sbah }(h ]h ]h"]shyah$]h&]uh1hhhhKHhhhhubh)}(h(.. |sol| unicode:: U+0002F .. SOLIDUSh]h/}hj sbah }(h ]h ]h"]solah$]h&]uh1hhhhKIhhhhubh)}(h,.. |sung| unicode:: U+0266A .. EIGHTH NOTEh]h♪}hj sbah }(h ]h ]h"]sungah$]h&]uh1hhhhKJhhhhubh)}(h0.. |sup1| unicode:: U+000B9 .. SUPERSCRIPT ONEh]h¹}hj sbah }(h ]h ]h"]sup1ah$]h&]uh1hhhhKKhhhhubh)}(h0.. |sup2| unicode:: U+000B2 .. SUPERSCRIPT TWOh]h²}hj sbah }(h ]h ]h"]sup2ah$]h&]uh1hhhhKLhhhhubh)}(h2.. |sup3| unicode:: U+000B3 .. SUPERSCRIPT THREEh]h³}hj sbah }(h ]h ]h"]sup3ah$]h&]uh1hhhhKMhhhhubh)}(h4.. |times| unicode:: U+000D7 .. MULTIPLICATION SIGNh]h×}hj sbah }(h ]h ]h"]timesah$]h&]uh1hhhhKNhhhhubh)}(h0.. |trade| unicode:: U+02122 .. TRADE MARK SIGNh]h™}hj sbah }(h ]h ]h"]tradeah$]h&]uh1hhhhKOhhhhubh)}(h... |uarr| unicode:: U+02191 .. UPWARDS ARROWh]h↑}hj sbah }(h ]h ]h"]uarrah$]h&]uh1hhhhKPhhhhubh)}(h... |verbar| unicode:: U+0007C .. VERTICAL LINEh]h|}hj. sbah }(h ]h ]h"]verbarah$]h&]uh1hhhhKQhhhhubh)}(h*.. |yen| unicode:: U+000A5 .. YEN SIGN
h]h¥}hj= sbah }(h ]h ]h"]yenah$]h&]uh1hhhhKRhhhhubhsection)}(hhh](htitle)}(hMulti-touch (MT) Protocolh]hMulti-touch (MT) Protocol}(hjS hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hjN hhhH/var/lib/git/docbuild/linux/Documentation/input/multi-touch-protocol.rsthKubh
field_list)}(hhh]hfield)}(hhh](h
field_name)}(h Copyrighth]h Copyright}(hjn hhhNhNubah }(h ]h ]h"]h$]h&]uh1jl hji hja hK ubh
field_body)}(h:|copy| 2009-2010 Henrik Rydberg
h]h paragraph)}(h8|copy| 2009-2010 Henrik Rydberg h](h©}(hj hhhNhNubh 2009-2010 Henrik Rydberg <}(hj hhhNhNubh reference)}(hrydberg@euromail.seh]hrydberg@euromail.se}(hj hhhNhNubah }(h ]h ]h"]h$]h&]refurimailto:rydberg@euromail.seuh1j hj ubh>}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj~ ubah }(h ]h ]h"]h$]h&]uh1j| hji ubeh }(h ]h ]h"]h$]h&]uh1jg hja hKhjd hhubah }(h ]h ]h"]h$]h&]uh1jb hjN hhhja hKubjM )}(hhh](jR )}(h Introductionh]h Introduction}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj hhhja hK ubj )}(hXU In order to utilize the full power of the new multi-touch and multi-user
devices, a way to report detailed data from multiple contacts, i.e.,
objects in direct contact with the device surface, is needed. This
document describes the multi-touch (MT) protocol which allows kernel
drivers to report details for an arbitrary number of contacts.h]hXU In order to utilize the full power of the new multi-touch and multi-user
devices, a way to report detailed data from multiple contacts, i.e.,
objects in direct contact with the device surface, is needed. This
document describes the multi-touch (MT) protocol which allows kernel
drivers to report details for an arbitrary number of contacts.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK
hj hhubj )}(hXn The protocol is divided into two types, depending on the capabilities of the
hardware. For devices handling anonymous contacts (type A), the protocol
describes how to send the raw data for all contacts to the receiver. For
devices capable of tracking identifiable contacts (type B), the protocol
describes how to send updates for individual contacts via event slots.h]hXn The protocol is divided into two types, depending on the capabilities of the
hardware. For devices handling anonymous contacts (type A), the protocol
describes how to send the raw data for all contacts to the receiver. For
devices capable of tracking identifiable contacts (type B), the protocol
describes how to send updates for individual contacts via event slots.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubhnote)}(hUMT protocol type A is obsolete, all kernel drivers have been
converted to use type B.h]j )}(hUMT protocol type A is obsolete, all kernel drivers have been
converted to use type B.h]hUMT protocol type A is obsolete, all kernel drivers have been
converted to use type B.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj ubah }(h ]h ]h"]h$]h&]uh1j hj hhhja hNubeh }(h ] introductionah ]h"] introductionah$]h&]uh1jL hjN hhhja hK ubjM )}(hhh](jR )}(hProtocol Usageh]hProtocol Usage}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj
hhhja hK ubj )}(hX, Contact details are sent sequentially as separate packets of ABS_MT
events. Only the ABS_MT events are recognized as part of a contact
packet. Since these events are ignored by current single-touch (ST)
applications, the MT protocol can be implemented on top of the ST protocol
in an existing driver.h]hX, Contact details are sent sequentially as separate packets of ABS_MT
events. Only the ABS_MT events are recognized as part of a contact
packet. Since these events are ignored by current single-touch (ST)
applications, the MT protocol can be implemented on top of the ST protocol
in an existing driver.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK hj
hhubj )}(hDrivers for type A devices separate contact packets by calling
input_mt_sync() at the end of each packet. This generates a SYN_MT_REPORT
event, which instructs the receiver to accept the data for the current
contact and prepare to receive another.h]hDrivers for type A devices separate contact packets by calling
input_mt_sync() at the end of each packet. This generates a SYN_MT_REPORT
event, which instructs the receiver to accept the data for the current
contact and prepare to receive another.}(hj, hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK&hj
hhubj )}(hDrivers for type B devices separate contact packets by calling
input_mt_slot(), with a slot as argument, at the beginning of each packet.
This generates an ABS_MT_SLOT event, which instructs the receiver to
prepare for updates of the given slot.h]hDrivers for type B devices separate contact packets by calling
input_mt_slot(), with a slot as argument, at the beginning of each packet.
This generates an ABS_MT_SLOT event, which instructs the receiver to
prepare for updates of the given slot.}(hj: hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK+hj
hhubj )}(hAll drivers mark the end of a multi-touch transfer by calling the usual
input_sync() function. This instructs the receiver to act upon events
accumulated since last EV_SYN/SYN_REPORT and prepare to receive a new set
of events/packets.h]hAll drivers mark the end of a multi-touch transfer by calling the usual
input_sync() function. This instructs the receiver to act upon events
accumulated since last EV_SYN/SYN_REPORT and prepare to receive a new set
of events/packets.}(hjH hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK0hj
hhubj )}(hX> The main difference between the stateless type A protocol and the stateful
type B slot protocol lies in the usage of identifiable contacts to reduce
the amount of data sent to userspace. The slot protocol requires the use of
the ABS_MT_TRACKING_ID, either provided by the hardware or computed from
the raw data [#f5]_.h](hX7 The main difference between the stateless type A protocol and the stateful
type B slot protocol lies in the usage of identifiable contacts to reduce
the amount of data sent to userspace. The slot protocol requires the use of
the ABS_MT_TRACKING_ID, either provided by the hardware or computed from
the raw data }(hjV hhhNhNubhfootnote_reference)}(h[#f5]_h]h5}(hj` hhhNhNubah }(h ]id1ah ]h"]h$]h&]autoKrefidf5docnameinput/multi-touch-protocoluh1j^ hjV resolvedKubh.}(hjV hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hK5hj
hhubj )}(hX For type A devices, the kernel driver should generate an arbitrary
enumeration of the full set of anonymous contacts currently on the
surface. The order in which the packets appear in the event stream is not
important. Event filtering and finger tracking is left to user space [#f3]_.h](hX For type A devices, the kernel driver should generate an arbitrary
enumeration of the full set of anonymous contacts currently on the
surface. The order in which the packets appear in the event stream is not
important. Event filtering and finger tracking is left to user space }(hj hhhNhNubj_ )}(h[#f3]_h]h3}(hj hhhNhNubah }(h ]id2ah ]h"]h$]h&]jo Kjp f3jr js uh1j^ hj jt Kubh.}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hK;hj
hhubj )}(hX For type B devices, the kernel driver should associate a slot with each
identified contact, and use that slot to propagate changes for the contact.
Creation, replacement and destruction of contacts is achieved by modifying
the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
is interpreted as a contact, and the value -1 denotes an unused slot. A
tracking id not previously present is considered new, and a tracking id no
longer present is considered removed. Since only changes are propagated,
the full state of each initiated contact has to reside in the receiving
end. Upon receiving an MT event, one simply updates the appropriate
attribute of the current slot.h]hX For type B devices, the kernel driver should associate a slot with each
identified contact, and use that slot to propagate changes for the contact.
Creation, replacement and destruction of contacts is achieved by modifying
the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
is interpreted as a contact, and the value -1 denotes an unused slot. A
tracking id not previously present is considered new, and a tracking id no
longer present is considered removed. Since only changes are propagated,
the full state of each initiated contact has to reside in the receiving
end. Upon receiving an MT event, one simply updates the appropriate
attribute of the current slot.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK@hj
hhubj )}(hX Some devices identify and/or track more contacts than they can report to the
driver. A driver for such a device should associate one type B slot with each
contact that is reported by the hardware. Whenever the identity of the
contact associated with a slot changes, the driver should invalidate that
slot by changing its ABS_MT_TRACKING_ID. If the hardware signals that it is
tracking more contacts than it is currently reporting, the driver should use
a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
being tracked by the hardware at that moment. The driver should do this by
explicitly sending the corresponding BTN_TOOL_*TAP event and setting
use_count to false when calling input_mt_report_pointer_emulation().
The driver should only advertise as many slots as the hardware can report.
Userspace can detect that a driver can report more total contacts than slots
by noting that the largest supported BTN_TOOL_*TAP event is larger than the
total number of type B slots reported in the absinfo for the ABS_MT_SLOT axis.h]hX Some devices identify and/or track more contacts than they can report to the
driver. A driver for such a device should associate one type B slot with each
contact that is reported by the hardware. Whenever the identity of the
contact associated with a slot changes, the driver should invalidate that
slot by changing its ABS_MT_TRACKING_ID. If the hardware signals that it is
tracking more contacts than it is currently reporting, the driver should use
a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
being tracked by the hardware at that moment. The driver should do this by
explicitly sending the corresponding BTN_TOOL_*TAP event and setting
use_count to false when calling input_mt_report_pointer_emulation().
The driver should only advertise as many slots as the hardware can report.
Userspace can detect that a driver can report more total contacts than slots
by noting that the largest supported BTN_TOOL_*TAP event is larger than the
total number of type B slots reported in the absinfo for the ABS_MT_SLOT axis.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKKhj
hhubj )}(h4The minimum value of the ABS_MT_SLOT axis must be 0.h]h4The minimum value of the ABS_MT_SLOT axis must be 0.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKZhj
hhubeh }(h ]protocol-usageah ]h"]protocol usageah$]h&]uh1jL hjN hhhja hK ubjM )}(hhh](jR )}(hProtocol Example Ah]hProtocol Example A}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj hhhja hK]ubj )}(hcHere is what a minimal event sequence for a two-contact touch would look
like for a type A device::h]hbHere is what a minimal event sequence for a two-contact touch would look
like for a type A device:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hK_hj hhubh
literal_block)}(hABS_MT_POSITION_X x[0]
ABS_MT_POSITION_Y y[0]
SYN_MT_REPORT
ABS_MT_POSITION_X x[1]
ABS_MT_POSITION_Y y[1]
SYN_MT_REPORT
SYN_REPORTh]hABS_MT_POSITION_X x[0]
ABS_MT_POSITION_Y y[0]
SYN_MT_REPORT
ABS_MT_POSITION_X x[1]
ABS_MT_POSITION_Y y[1]
SYN_MT_REPORT
SYN_REPORT}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKbhj hhubj )}(hThe sequence after moving one of the contacts looks exactly the same; the
raw data for all present contacts are sent between every synchronization
with SYN_REPORT.h]hThe sequence after moving one of the contacts looks exactly the same; the
raw data for all present contacts are sent between every synchronization
with SYN_REPORT.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKjhj hhubj )}(h6Here is the sequence after lifting the first contact::h]h5Here is the sequence after lifting the first contact:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKnhj hhubj )}(hFABS_MT_POSITION_X x[1]
ABS_MT_POSITION_Y y[1]
SYN_MT_REPORT
SYN_REPORTh]hFABS_MT_POSITION_X x[1]
ABS_MT_POSITION_Y y[1]
SYN_MT_REPORT
SYN_REPORT}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKphj hhubj )}(h;And here is the sequence after lifting the second contact::h]h:And here is the sequence after lifting the second contact:}(hj, hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKuhj hhubj )}(hSYN_MT_REPORT
SYN_REPORTh]hSYN_MT_REPORT
SYN_REPORT}hj: sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKwhj hhubj )}(hIf the driver reports one of BTN_TOUCH or ABS_PRESSURE in addition to the
ABS_MT events, the last SYN_MT_REPORT event may be omitted. Otherwise, the
last SYN_REPORT will be dropped by the input core, resulting in no
zero-contact event reaching userland.h]hIf the driver reports one of BTN_TOUCH or ABS_PRESSURE in addition to the
ABS_MT events, the last SYN_MT_REPORT event may be omitted. Otherwise, the
last SYN_REPORT will be dropped by the input core, resulting in no
zero-contact event reaching userland.}(hjH hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKzhj hhubeh }(h ]protocol-example-aah ]h"]protocol example aah$]h&]uh1jL hjN hhhja hK]ubjM )}(hhh](jR )}(hProtocol Example Bh]hProtocol Example B}(hja hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj^ hhhja hKubj )}(hcHere is what a minimal event sequence for a two-contact touch would look
like for a type B device::h]hbHere is what a minimal event sequence for a two-contact touch would look
like for a type B device:}(hjo hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj^ hhubj )}(hABS_MT_SLOT 0
ABS_MT_TRACKING_ID 45
ABS_MT_POSITION_X x[0]
ABS_MT_POSITION_Y y[0]
ABS_MT_SLOT 1
ABS_MT_TRACKING_ID 46
ABS_MT_POSITION_X x[1]
ABS_MT_POSITION_Y y[1]
SYN_REPORTh]hABS_MT_SLOT 0
ABS_MT_TRACKING_ID 45
ABS_MT_POSITION_X x[0]
ABS_MT_POSITION_Y y[0]
ABS_MT_SLOT 1
ABS_MT_TRACKING_ID 46
ABS_MT_POSITION_X x[1]
ABS_MT_POSITION_Y y[1]
SYN_REPORT}hj} sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKhj^ hhubj )}(hAHere is the sequence after moving contact 45 in the x direction::h]h@Here is the sequence after moving contact 45 in the x direction:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj^ hhubj )}(h/ABS_MT_SLOT 0
ABS_MT_POSITION_X x[0]
SYN_REPORTh]h/ABS_MT_SLOT 0
ABS_MT_POSITION_X x[0]
SYN_REPORT}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKhj^ hhubj )}(h:Here is the sequence after lifting the contact in slot 0::h]h9Here is the sequence after lifting the contact in slot 0:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj^ hhubj )}(h ABS_MT_TRACKING_ID -1
SYN_REPORTh]h ABS_MT_TRACKING_ID -1
SYN_REPORT}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKhj^ hhubj )}(hThe slot being modified is already 0, so the ABS_MT_SLOT is omitted. The
message removes the association of slot 0 with contact 45, thereby
destroying contact 45 and freeing slot 0 to be reused for another contact.h]hThe slot being modified is already 0, so the ABS_MT_SLOT is omitted. The
message removes the association of slot 0 with contact 45, thereby
destroying contact 45 and freeing slot 0 to be reused for another contact.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj^ hhubj )}(h@Finally, here is the sequence after lifting the second contact::h]h?Finally, here is the sequence after lifting the second contact:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj^ hhubj )}(h.ABS_MT_SLOT 1
ABS_MT_TRACKING_ID -1
SYN_REPORTh]h.ABS_MT_SLOT 1
ABS_MT_TRACKING_ID -1
SYN_REPORT}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKhj^ hhubeh }(h ]protocol-example-bah ]h"]protocol example bah$]h&]uh1jL hjN hhhja hKubjM )}(hhh](jR )}(h Event Usageh]h Event Usage}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj hhhja hKubj )}(hX A set of ABS_MT events with the desired properties is defined. The events
are divided into categories, to allow for partial implementation. The
minimum set consists of ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which
allows for multiple contacts to be tracked. If the device supports it, the
ABS_MT_TOUCH_MAJOR and ABS_MT_WIDTH_MAJOR may be used to provide the size
of the contact area and approaching tool, respectively.h]hX A set of ABS_MT events with the desired properties is defined. The events
are divided into categories, to allow for partial implementation. The
minimum set consists of ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which
allows for multiple contacts to be tracked. If the device supports it, the
ABS_MT_TOUCH_MAJOR and ABS_MT_WIDTH_MAJOR may be used to provide the size
of the contact area and approaching tool, respectively.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(hX The TOUCH and WIDTH parameters have a geometrical interpretation; imagine
looking through a window at someone gently holding a finger against the
glass. You will see two regions, one inner region consisting of the part
of the finger actually touching the glass, and one outer region formed by
the perimeter of the finger. The center of the touching region (a) is
ABS_MT_POSITION_X/Y and the center of the approaching finger (b) is
ABS_MT_TOOL_X/Y. The touch diameter is ABS_MT_TOUCH_MAJOR and the finger
diameter is ABS_MT_WIDTH_MAJOR. Now imagine the person pressing the finger
harder against the glass. The touch region will increase, and in general,
the ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR, which is always smaller
than unity, is related to the contact pressure. For pressure-based devices,
ABS_MT_PRESSURE may be used to provide the pressure on the contact area
instead. Devices capable of contact hovering can use ABS_MT_DISTANCE to
indicate the distance between the contact and the surface.h]hX The TOUCH and WIDTH parameters have a geometrical interpretation; imagine
looking through a window at someone gently holding a finger against the
glass. You will see two regions, one inner region consisting of the part
of the finger actually touching the glass, and one outer region formed by
the perimeter of the finger. The center of the touching region (a) is
ABS_MT_POSITION_X/Y and the center of the approaching finger (b) is
ABS_MT_TOOL_X/Y. The touch diameter is ABS_MT_TOUCH_MAJOR and the finger
diameter is ABS_MT_WIDTH_MAJOR. Now imagine the person pressing the finger
harder against the glass. The touch region will increase, and in general,
the ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR, which is always smaller
than unity, is related to the contact pressure. For pressure-based devices,
ABS_MT_PRESSURE may be used to provide the pressure on the contact area
instead. Devices capable of contact hovering can use ABS_MT_DISTANCE to
indicate the distance between the contact and the surface.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(hX Linux MT Win8
__________ _______________________
/ \ | |
/ \ | |
/ ____ \ | |
/ / \ \ | |
\ \ a \ \ | a |
\ \____/ \ | |
\ \ | |
\ b \ | b |
\ \ | |
\ \ | |
\ \ | |
\ / | |
\ / | |
\ / | |
\__________/ |_______________________|h]hX Linux MT Win8
__________ _______________________
/ \ | |
/ \ | |
/ ____ \ | |
/ / \ \ | |
\ \ a \ \ | a |
\ \____/ \ | |
\ \ | |
\ b \ | b |
\ \ | |
\ \ | |
\ \ | |
\ / | |
\ / | |
\ / | |
\__________/ |_______________________|}hj" sbah }(h ]h ]h"]h$]h&]hhuh1j hja hKhj hhubj )}(hXh In addition to the MAJOR parameters, the oval shape of the touch and finger
regions can be described by adding the MINOR parameters, such that MAJOR
and MINOR are the major and minor axis of an ellipse. The orientation of
the touch ellipse can be described with the ORIENTATION parameter, and the
direction of the finger ellipse is given by the vector (a - b).h]hXh In addition to the MAJOR parameters, the oval shape of the touch and finger
regions can be described by adding the MINOR parameters, such that MAJOR
and MINOR are the major and minor axis of an ellipse. The orientation of
the touch ellipse can be described with the ORIENTATION parameter, and the
direction of the finger ellipse is given by the vector (a - b).}(hj0 hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(h\For type A devices, further specification of the touch shape is possible
via ABS_MT_BLOB_ID.h]h\For type A devices, further specification of the touch shape is possible
via ABS_MT_BLOB_ID.}(hj> hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(hThe ABS_MT_TOOL_TYPE may be used to specify whether the touching tool is a
finger or a pen or something else. Finally, the ABS_MT_TRACKING_ID event
may be used to track identified contacts over time [#f5]_.h](hThe ABS_MT_TOOL_TYPE may be used to specify whether the touching tool is a
finger or a pen or something else. Finally, the ABS_MT_TRACKING_ID event
may be used to track identified contacts over time }(hjL hhhNhNubj_ )}(h[#f5]_h]h5}(hjT hhhNhNubah }(h ]id3ah ]h"]h$]h&]jo Kjp jq jr js uh1j^ hjL jt Kubh.}(hjL hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(hIn the type B protocol, ABS_MT_TOOL_TYPE and ABS_MT_TRACKING_ID are
implicitly handled by input core; drivers should instead call
input_mt_report_slot_state().h]hIn the type B protocol, ABS_MT_TOOL_TYPE and ABS_MT_TRACKING_ID are
implicitly handled by input core; drivers should instead call
input_mt_report_slot_state().}(hjm hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubeh }(h ] event-usageah ]h"] event usageah$]h&]uh1jL hjN hhhja hKubjM )}(hhh](jR )}(hEvent Semanticsh]hEvent Semantics}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj hhhja hKubhdefinition_list)}(hhh](hdefinition_list_item)}(hABS_MT_TOUCH_MAJOR
The length of the major axis of the contact. The length should be given in
surface units. If the surface has an X times Y resolution, the largest
possible value of ABS_MT_TOUCH_MAJOR is sqrt(X^2 + Y^2), the diagonal [#f4]_.
h](hterm)}(hABS_MT_TOUCH_MAJORh]hABS_MT_TOUCH_MAJOR}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj ubh
definition)}(hhh]j )}(hThe length of the major axis of the contact. The length should be given in
surface units. If the surface has an X times Y resolution, the largest
possible value of ABS_MT_TOUCH_MAJOR is sqrt(X^2 + Y^2), the diagonal [#f4]_.h](hThe length of the major axis of the contact. The length should be given in
surface units. If the surface has an X times Y resolution, the largest
possible value of ABS_MT_TOUCH_MAJOR is sqrt(X^2 + Y^2), the diagonal }(hj hhhNhNubj_ )}(h[#f4]_h]h4}(hj hhhNhNubah }(h ]id4ah ]h"]h$]h&]jo Kjp f4jr js uh1j^ hj jt Kubh.}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj ubah }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj ubj )}(hABS_MT_TOUCH_MINOR
The length, in surface units, of the minor axis of the contact. If the
contact is circular, this event can be omitted [#f4]_.
h](j )}(hABS_MT_TOUCH_MINORh]hABS_MT_TOUCH_MINOR}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj ubj )}(hhh]j )}(h}The length, in surface units, of the minor axis of the contact. If the
contact is circular, this event can be omitted [#f4]_.h](hvThe length, in surface units, of the minor axis of the contact. If the
contact is circular, this event can be omitted }(hj hhhNhNubj_ )}(h[#f4]_h]h4}(hj hhhNhNubah }(h ]id5ah ]h"]h$]h&]jo Kjp j jr js uh1j^ hj jt Kubh.}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj ubah }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(hABS_MT_WIDTH_MAJOR
The length, in surface units, of the major axis of the approaching
tool. This should be understood as the size of the tool itself. The
orientation of the contact and the approaching tool are assumed to be the
same [#f4]_.
h](j )}(hABS_MT_WIDTH_MAJORh]hABS_MT_WIDTH_MAJOR}(hj( hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhj$ ubj )}(hhh]j )}(hThe length, in surface units, of the major axis of the approaching
tool. This should be understood as the size of the tool itself. The
orientation of the contact and the approaching tool are assumed to be the
same [#f4]_.h](hThe length, in surface units, of the major axis of the approaching
tool. This should be understood as the size of the tool itself. The
orientation of the contact and the approaching tool are assumed to be the
same }(hj9 hhhNhNubj_ )}(h[#f4]_h]h4}(hjA hhhNhNubah }(h ]id6ah ]h"]h$]h&]jo Kjp j jr js uh1j^ hj9 jt Kubh.}(hj9 hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj6 ubah }(h ]h ]h"]h$]h&]uh1j hj$ ubeh }(h ]h ]h"]h$]h&]uh1j hja hKhj hhubj )}(hXr ABS_MT_WIDTH_MINOR
The length, in surface units, of the minor axis of the approaching
tool. Omit if circular [#f4]_.
The above four values can be used to derive additional information about
the contact. The ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR approximates
the notion of pressure. The fingers of the hand and the palm all have
different characteristic widths.
h](j )}(hABS_MT_WIDTH_MINORh]hABS_MT_WIDTH_MINOR}(hjj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM hjf ubj )}(hhh](j )}(haThe length, in surface units, of the minor axis of the approaching
tool. Omit if circular [#f4]_.h](hZThe length, in surface units, of the minor axis of the approaching
tool. Omit if circular }(hj{ hhhNhNubj_ )}(h[#f4]_h]h4}(hj hhhNhNubah }(h ]id7ah ]h"]h$]h&]jo Kjp j jr js uh1j^ hj{ jt Kubh.}(hj{ hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hKhjx ubj )}(hThe above four values can be used to derive additional information about
the contact. The ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR approximates
the notion of pressure. The fingers of the hand and the palm all have
different characteristic widths.h]hThe above four values can be used to derive additional information about
the contact. The ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR approximates
the notion of pressure. The fingers of the hand and the palm all have
different characteristic widths.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hKhjx ubeh }(h ]h ]h"]h$]h&]uh1j hjf ubeh }(h ]h ]h"]h$]h&]uh1j hja hM hj hhubj )}(hXw ABS_MT_PRESSURE
The pressure, in arbitrary units, on the contact area. May be used instead
of TOUCH and WIDTH for pressure-based devices or any device with a spatial
signal intensity distribution.
If the resolution is zero, the pressure data is in arbitrary units.
If the resolution is non-zero, the pressure data is in units/gram. See
:ref:`input-event-codes` for details.
h](j )}(hABS_MT_PRESSUREh]hABS_MT_PRESSURE}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM hj ubj )}(hhh](j )}(hThe pressure, in arbitrary units, on the contact area. May be used instead
of TOUCH and WIDTH for pressure-based devices or any device with a spatial
signal intensity distribution.h]hThe pressure, in arbitrary units, on the contact area. May be used instead
of TOUCH and WIDTH for pressure-based devices or any device with a spatial
signal intensity distribution.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj ubj )}(hIf the resolution is zero, the pressure data is in arbitrary units.
If the resolution is non-zero, the pressure data is in units/gram. See
:ref:`input-event-codes` for details.h](hIf the resolution is zero, the pressure data is in arbitrary units.
If the resolution is non-zero, the pressure data is in units/gram. See
}(hj hhhNhNubh)}(h:ref:`input-event-codes`h]hinline)}(hj h]hinput-event-codes}(hj hhhNhNubah }(h ]h ](xrefstdstd-refeh"]h$]h&]uh1j hj ubah }(h ]h ]h"]h$]h&]refdocjs refdomainj reftyperef refexplicitrefwarn reftargetinput-event-codesuh1hhja hMhj ubh
for details.}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hMhj ubeh }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hM hj hhubj )}(hABS_MT_DISTANCE
The distance, in surface units, between the contact and the surface. Zero
distance means the contact is touching the surface. A positive number means
the contact is hovering above the surface.
h](j )}(hABS_MT_DISTANCEh]hABS_MT_DISTANCE}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj
ubj )}(hhh]j )}(hThe distance, in surface units, between the contact and the surface. Zero
distance means the contact is touching the surface. A positive number means
the contact is hovering above the surface.h]hThe distance, in surface units, between the contact and the surface. Zero
distance means the contact is touching the surface. A positive number means
the contact is hovering above the surface.}(hj0
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM hj-
ubah }(h ]h ]h"]h$]h&]uh1j hj
ubeh }(h ]h ]h"]h$]h&]uh1j hja hMhj hhubj )}(hX ABS_MT_ORIENTATION
The orientation of the touching ellipse. The value should describe a signed
quarter of a revolution clockwise around the touch center. The signed value
range is arbitrary, but zero should be returned for an ellipse aligned with
the Y axis (north) of the surface, a negative value when the ellipse is
turned to the left, and a positive value when the ellipse is turned to the
right. When aligned with the X axis in the positive direction, the range
max should be returned; when aligned with the X axis in the negative
direction, the range -max should be returned.
Touch ellipses are symmetrical by default. For devices capable of true 360
degree orientation, the reported orientation must exceed the range max to
indicate more than a quarter of a revolution. For an upside-down finger,
range max * 2 should be returned.
Orientation can be omitted if the touch area is circular, or if the
information is not available in the kernel driver. Partial orientation
support is possible if the device can distinguish between the two axes, but
not (uniquely) any values in between. In such cases, the range of
ABS_MT_ORIENTATION should be [0, 1] [#f4]_.
h](j )}(hABS_MT_ORIENTATIONh]hABS_MT_ORIENTATION}(hjN
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM#hjJ
ubj )}(hhh](j )}(hX2 The orientation of the touching ellipse. The value should describe a signed
quarter of a revolution clockwise around the touch center. The signed value
range is arbitrary, but zero should be returned for an ellipse aligned with
the Y axis (north) of the surface, a negative value when the ellipse is
turned to the left, and a positive value when the ellipse is turned to the
right. When aligned with the X axis in the positive direction, the range
max should be returned; when aligned with the X axis in the negative
direction, the range -max should be returned.h]hX2 The orientation of the touching ellipse. The value should describe a signed
quarter of a revolution clockwise around the touch center. The signed value
range is arbitrary, but zero should be returned for an ellipse aligned with
the Y axis (north) of the surface, a negative value when the ellipse is
turned to the left, and a positive value when the ellipse is turned to the
right. When aligned with the X axis in the positive direction, the range
max should be returned; when aligned with the X axis in the negative
direction, the range -max should be returned.}(hj_
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj\
ubj )}(hTouch ellipses are symmetrical by default. For devices capable of true 360
degree orientation, the reported orientation must exceed the range max to
indicate more than a quarter of a revolution. For an upside-down finger,
range max * 2 should be returned.h]hTouch ellipses are symmetrical by default. For devices capable of true 360
degree orientation, the reported orientation must exceed the range max to
indicate more than a quarter of a revolution. For an upside-down finger,
range max * 2 should be returned.}(hjm
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj\
ubj )}(hXD Orientation can be omitted if the touch area is circular, or if the
information is not available in the kernel driver. Partial orientation
support is possible if the device can distinguish between the two axes, but
not (uniquely) any values in between. In such cases, the range of
ABS_MT_ORIENTATION should be [0, 1] [#f4]_.h](hX= Orientation can be omitted if the touch area is circular, or if the
information is not available in the kernel driver. Partial orientation
support is possible if the device can distinguish between the two axes, but
not (uniquely) any values in between. In such cases, the range of
ABS_MT_ORIENTATION should be [0, 1] }(hj{
hhhNhNubj_ )}(h[#f4]_h]h4}(hj
hhhNhNubah }(h ]id8ah ]h"]h$]h&]jo Kjp j jr js uh1j^ hj{
jt Kubh.}(hj{
hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hM hj\
ubeh }(h ]h ]h"]h$]h&]uh1j hjJ
ubeh }(h ]h ]h"]h$]h&]uh1j hja hM#hj hhubj )}(hRABS_MT_POSITION_X
The surface X coordinate of the center of the touching ellipse.
h](j )}(hABS_MT_POSITION_Xh]hABS_MT_POSITION_X}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM&hj
ubj )}(hhh]j )}(h?The surface X coordinate of the center of the touching ellipse.h]h?The surface X coordinate of the center of the touching ellipse.}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM&hj
ubah }(h ]h ]h"]h$]h&]uh1j hj
ubeh }(h ]h ]h"]h$]h&]uh1j hja hM&hj hhubj )}(hRABS_MT_POSITION_Y
The surface Y coordinate of the center of the touching ellipse.
h](j )}(hABS_MT_POSITION_Yh]hABS_MT_POSITION_Y}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM)hj
ubj )}(hhh]j )}(h?The surface Y coordinate of the center of the touching ellipse.h]h?The surface Y coordinate of the center of the touching ellipse.}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM)hj
ubah }(h ]h ]h"]h$]h&]uh1j hj
ubeh }(h ]h ]h"]h$]h&]uh1j hja hM)hj hhubj )}(hABS_MT_TOOL_X
The surface X coordinate of the center of the approaching tool. Omit if
the device cannot distinguish between the intended touch point and the
tool itself.
h](j )}(h
ABS_MT_TOOL_Xh]h
ABS_MT_TOOL_X}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM.hj ubj )}(hhh]j )}(hThe surface X coordinate of the center of the approaching tool. Omit if
the device cannot distinguish between the intended touch point and the
tool itself.h]hThe surface X coordinate of the center of the approaching tool. Omit if
the device cannot distinguish between the intended touch point and the
tool itself.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM,hj ubah }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hM.hj hhubj )}(hX ABS_MT_TOOL_Y
The surface Y coordinate of the center of the approaching tool. Omit if the
device cannot distinguish between the intended touch point and the tool
itself.
The four position values can be used to separate the position of the touch
from the position of the tool. If both positions are present, the major
tool axis points towards the touch point [#f1]_. Otherwise, the tool axes are
aligned with the touch axes.
h](j )}(h
ABS_MT_TOOL_Yh]h
ABS_MT_TOOL_Y}(hj9 hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM8hj5 ubj )}(hhh](j )}(hThe surface Y coordinate of the center of the approaching tool. Omit if the
device cannot distinguish between the intended touch point and the tool
itself.h]hThe surface Y coordinate of the center of the approaching tool. Omit if the
device cannot distinguish between the intended touch point and the tool
itself.}(hjJ hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hM1hjG ubj )}(hThe four position values can be used to separate the position of the touch
from the position of the tool. If both positions are present, the major
tool axis points towards the touch point [#f1]_. Otherwise, the tool axes are
aligned with the touch axes.h](hThe four position values can be used to separate the position of the touch
from the position of the tool. If both positions are present, the major
tool axis points towards the touch point }(hjX hhhNhNubj_ )}(h[#f1]_h]h1}(hj` hhhNhNubah }(h ]id9ah ]h"]h$]h&]jo Kjp f1jr js uh1j^ hjX jt Kubh;. Otherwise, the tool axes are
aligned with the touch axes.}(hjX hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hM5hjG ubeh }(h ]h ]h"]h$]h&]uh1j hj5 ubeh }(h ]h ]h"]h$]h&]uh1j hja hM8hj hhubj )}(hXC ABS_MT_TOOL_TYPE
The type of approaching tool. A lot of kernel drivers cannot distinguish
between different tool types, such as a finger or a pen. In such cases, the
event should be omitted. The protocol currently mainly supports
MT_TOOL_FINGER, MT_TOOL_PEN, and MT_TOOL_PALM [#f2]_.
For type B devices, this event is handled by input core; drivers should
instead use input_mt_report_slot_state(). A contact's ABS_MT_TOOL_TYPE may
change over time while still touching the device, because the firmware may
not be able to determine which tool is being used when it first appears.
h](j )}(hABS_MT_TOOL_TYPEh]hABS_MT_TOOL_TYPE}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMBhj ubj )}(hhh]j )}(hX1 The type of approaching tool. A lot of kernel drivers cannot distinguish
between different tool types, such as a finger or a pen. In such cases, the
event should be omitted. The protocol currently mainly supports
MT_TOOL_FINGER, MT_TOOL_PEN, and MT_TOOL_PALM [#f2]_.
For type B devices, this event is handled by input core; drivers should
instead use input_mt_report_slot_state(). A contact's ABS_MT_TOOL_TYPE may
change over time while still touching the device, because the firmware may
not be able to determine which tool is being used when it first appears.h](hX The type of approaching tool. A lot of kernel drivers cannot distinguish
between different tool types, such as a finger or a pen. In such cases, the
event should be omitted. The protocol currently mainly supports
MT_TOOL_FINGER, MT_TOOL_PEN, and MT_TOOL_PALM }(hj hhhNhNubj_ )}(h[#f2]_h]h2}(hj hhhNhNubah }(h ]id10ah ]h"]h$]h&]jo Kjp f2jr js uh1j^ hj jt KubhX* .
For type B devices, this event is handled by input core; drivers should
instead use input_mt_report_slot_state(). A contact’s ABS_MT_TOOL_TYPE may
change over time while still touching the device, because the firmware may
not be able to determine which tool is being used when it first appears.}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hM;hj ubah }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hMBhj hhubj )}(hX ABS_MT_BLOB_ID
The BLOB_ID groups several packets together into one arbitrarily shaped
contact. The sequence of points forms a polygon which defines the shape of
the contact. This is a low-level anonymous grouping for type A devices, and
should not be confused with the high-level trackingID [#f5]_. Most type A
devices do not have blob capability, so drivers can safely omit this event.
h](j )}(hABS_MT_BLOB_IDh]hABS_MT_BLOB_ID}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMIhj ubj )}(hhh]j )}(hXt The BLOB_ID groups several packets together into one arbitrarily shaped
contact. The sequence of points forms a polygon which defines the shape of
the contact. This is a low-level anonymous grouping for type A devices, and
should not be confused with the high-level trackingID [#f5]_. Most type A
devices do not have blob capability, so drivers can safely omit this event.h](hX The BLOB_ID groups several packets together into one arbitrarily shaped
contact. The sequence of points forms a polygon which defines the shape of
the contact. This is a low-level anonymous grouping for type A devices, and
should not be confused with the high-level trackingID }(hj hhhNhNubj_ )}(h[#f5]_h]h5}(hj hhhNhNubah }(h ]id11ah ]h"]h$]h&]jo Kjp jq jr js uh1j^ hj jt KubhY. Most type A
devices do not have blob capability, so drivers can safely omit this event.}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hMEhj ubah }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hMIhj hhubj )}(hXk ABS_MT_TRACKING_ID
The TRACKING_ID identifies an initiated contact throughout its life cycle
[#f5]_. The value range of the TRACKING_ID should be large enough to ensure
unique identification of a contact maintained over an extended period of
time. For type B devices, this event is handled by input core; drivers
should instead use input_mt_report_slot_state().
h](j )}(hABS_MT_TRACKING_IDh]hABS_MT_TRACKING_ID}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMQhj ubj )}(hhh]j )}(hXV The TRACKING_ID identifies an initiated contact throughout its life cycle
[#f5]_. The value range of the TRACKING_ID should be large enough to ensure
unique identification of a contact maintained over an extended period of
time. For type B devices, this event is handled by input core; drivers
should instead use input_mt_report_slot_state().h](hJThe TRACKING_ID identifies an initiated contact throughout its life cycle
}(hj hhhNhNubj_ )}(h[#f5]_h]h5}(hj( hhhNhNubah }(h ]id12ah ]h"]h$]h&]jo Kjp jq jr js uh1j^ hj jt KubhX . The value range of the TRACKING_ID should be large enough to ensure
unique identification of a contact maintained over an extended period of
time. For type B devices, this event is handled by input core; drivers
should instead use input_mt_report_slot_state().}(hj hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hMLhj ubah }(h ]h ]h"]h$]h&]uh1j hj ubeh }(h ]h ]h"]h$]h&]uh1j hja hMQhj hhubeh }(h ]h ]h"]h$]h&]uh1j hj hhhja hNubeh }(h ]event-semanticsah ]h"]event semanticsah$]h&]uh1jL hjN hhhja hKubjM )}(hhh](jR )}(hEvent Computationh]hEvent Computation}(hj^ hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj[ hhhja hMTubj )}(hThe flora of different hardware unavoidably leads to some devices fitting
better to the MT protocol than others. To simplify and unify the mapping,
this section gives recipes for how to compute certain events.h]hThe flora of different hardware unavoidably leads to some devices fitting
better to the MT protocol than others. To simplify and unify the mapping,
this section gives recipes for how to compute certain events.}(hjl hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMVhj[ hhubj )}(hFor devices reporting contacts as rectangular shapes, signed orientation
cannot be obtained. Assuming X and Y are the lengths of the sides of the
touching rectangle, here is a simple formula that retains the most
information possible::h]hFor devices reporting contacts as rectangular shapes, signed orientation
cannot be obtained. Assuming X and Y are the lengths of the sides of the
touching rectangle, here is a simple formula that retains the most
information possible:}(hjz hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMZhj[ hhubj )}(haABS_MT_TOUCH_MAJOR := max(X, Y)
ABS_MT_TOUCH_MINOR := min(X, Y)
ABS_MT_ORIENTATION := bool(X > Y)h]haABS_MT_TOUCH_MAJOR := max(X, Y)
ABS_MT_TOUCH_MINOR := min(X, Y)
ABS_MT_ORIENTATION := bool(X > Y)}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hM_hj[ hhubj )}(hThe range of ABS_MT_ORIENTATION should be set to [0, 1], to indicate that
the device can distinguish between a finger along the Y axis (0) and a
finger along the X axis (1).h]hThe range of ABS_MT_ORIENTATION should be set to [0, 1], to indicate that
the device can distinguish between a finger along the Y axis (0) and a
finger along the X axis (1).}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMchj[ hhubj )}(hIFor Win8 devices with both T and C coordinates, the position mapping is::h]hHFor Win8 devices with both T and C coordinates, the position mapping is:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMghj[ hhubj )}(h[ABS_MT_POSITION_X := T_X
ABS_MT_POSITION_Y := T_Y
ABS_MT_TOOL_X := C_X
ABS_MT_TOOL_Y := C_Yh]h[ABS_MT_POSITION_X := T_X
ABS_MT_POSITION_Y := T_Y
ABS_MT_TOOL_X := C_X
ABS_MT_TOOL_Y := C_Y}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hMihj[ hhubj )}(hUnfortunately, there is not enough information to specify both the touching
ellipse and the tool ellipse, so one has to resort to approximations. One
simple scheme, which is compatible with earlier usage, is::h]hUnfortunately, there is not enough information to specify both the touching
ellipse and the tool ellipse, so one has to resort to approximations. One
simple scheme, which is compatible with earlier usage, is:}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMnhj[ hhubj )}(hABS_MT_TOUCH_MAJOR := min(X, Y)
ABS_MT_TOUCH_MINOR :=
ABS_MT_ORIENTATION :=
ABS_MT_WIDTH_MAJOR := min(X, Y) + distance(T, C)
ABS_MT_WIDTH_MINOR := min(X, Y)h]hABS_MT_TOUCH_MAJOR := min(X, Y)
ABS_MT_TOUCH_MINOR :=
ABS_MT_ORIENTATION :=
ABS_MT_WIDTH_MAJOR := min(X, Y) + distance(T, C)
ABS_MT_WIDTH_MINOR := min(X, Y)}hj sbah }(h ]h ]h"]h$]h&]hhuh1j hja hMrhj[ hhubj )}(hX[ Rationale: We have no information about the orientation of the touching
ellipse, so approximate it with an inscribed circle instead. The tool
ellipse should align with the vector (T - C), so the diameter must
increase with distance(T, C). Finally, assume that the touch diameter is
equal to the tool thickness, and we arrive at the formulas above.h]hX[ Rationale: We have no information about the orientation of the touching
ellipse, so approximate it with an inscribed circle instead. The tool
ellipse should align with the vector (T - C), so the diameter must
increase with distance(T, C). Finally, assume that the touch diameter is
equal to the tool thickness, and we arrive at the formulas above.}(hj hhhNhNubah }(h ]h ]h"]h$]h&( ]uh1j hja hMxhj[ hhubeh }(h ]event-computationah ]h"]event computationah$]h&]uh1jL hjN hhhja hMTubjM )}(hhh](jR )}(hFinger Trackingh]hFinger Tracking}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj hhhja hMubj )}(hXF The process of finger tracking, i.e., to assign a unique trackingID to each
initiated contact on the surface, is a Euclidean Bipartite Matching
problem. At each event synchronization, the set of actual contacts is
matched to the set of contacts from the previous synchronization. A full
implementation can be found in [#f3]_.h](hX? The process of finger tracking, i.e., to assign a unique trackingID to each
initiated contact on the surface, is a Euclidean Bipartite Matching
problem. At each event synchronization, the set of actual contacts is
matched to the set of contacts from the previous synchronization. A full
implementation can be found in }(hj
hhhNhNubj_ )}(h[#f3]_h]h3}(hj
hhhNhNubah }(h ]id13ah ]h"]h$]h&]jo Kjp j jr js uh1j^ hj
jt Kubh.}(hj
hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hMhj hhubeh }(h ]finger-trackingah ]h"]finger trackingah$]h&]uh1jL hjN hhhja hMubjM )}(hhh](jR )}(hGesturesh]hGestures}(hj/
hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hj,
hhhja hMubj )}(hXf In the specific application of creating gesture events, the TOUCH and WIDTH
parameters can be used to, e.g., approximate finger pressure or distinguish
between index finger and thumb. With the addition of the MINOR parameters,
one can also distinguish between a sweeping finger and a pointing finger,
and with ORIENTATION, one can detect twisting of fingers.h]hXf In the specific application of creating gesture events, the TOUCH and WIDTH
parameters can be used to, e.g., approximate finger pressure or distinguish
between index finger and thumb. With the addition of the MINOR parameters,
one can also distinguish between a sweeping finger and a pointing finger,
and with ORIENTATION, one can detect twisting of fingers.}(hj=
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj,
hhubeh }(h ]gesturesah ]h"]gesturesah$]h&]uh1jL hjN hhhja hMubjM )}(hhh](jR )}(hNotesh]hNotes}(hjV
hhhNhNubah }(h ]h ]h"]h$]h&]uh1jQ hjS
hhhja hMubj )}(hIn order to stay compatible with existing applications, the data reported
in a finger packet must not be recognized as single-touch events.h]hIn order to stay compatible with existing applications, the data reported
in a finger packet must not be recognized as single-touch events.}(hjd
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhjS
hhubj )}(hFor type A devices, all finger data bypasses input filtering, since
subsequent events of the same type refer to different fingers.h]hFor type A devices, all finger data bypasses input filtering, since
subsequent events of the same type refer to different fingers.}(hjr
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhjS
hhubhfootnote)}(hEAlso, the difference (TOOL_X - POSITION_X) can be used to model tilt.h](hlabel)}(hhh]h1}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j
hj
hhhNhNubj )}(hj
h]hEAlso, the difference (TOOL_X - POSITION_X) can be used to model tilt.}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj
ubeh }(h ]jo ah ]h"]f1ah$]h&]jj ajo Kjr js uh1j
hja hMhjS
hhubj
)}(h#The list can of course be extended.h](j
)}(hhh]h2}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j
hj
hhhNhNubj )}(hj
h]h#The list can of course be extended.}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj
ubeh }(h ]j ah ]h"]f2ah$]h&]j ajo Kjr js uh1j
hja hMhjS
hhubj
)}(h2The mtdev project: http://bitmath.org/code/mtdev/.h](j
)}(hhh]h3}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j
hj
hhhNhNubj )}(hj
h](hThe mtdev project: }(hj
hhhNhNubj )}(h http://bitmath.org/code/mtdev/h]h http://bitmath.org/code/mtdev/}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]refurij
uh1j hj
ubh.}(hj
hhhNhNubeh }(h ]h ]h"]h$]h&]uh1j hja hMhj
ubeh }(h ]j ah ]h"]f3ah$]h&](j j
ejo Kjr js uh1j
hja hMhjS
hhubj
)}(h%See the section on event computation.h](j
)}(hhh]h4}(hj
hhhNhNubah }(h ]h ]h"]h$]h&]uh1j
hj hhhNhNubj )}(hj h]h%See the section on event computation.}(hj hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj ubeh }(h ]j ah ]h"]f4ah$]h&](j j jK j j
ejo Kjr js uh1j
hja hMhjS
hhubj
)}(h#See the section on finger tracking.h](j
)}(hhh]h5}(hj/ hhhNhNubah }(h ]h ]h"]h$]h&]uh1j
hj+ hhhNhNubj )}(hj- h]h#See the section on finger tracking.}(hj< hhhNhNubah }(h ]h ]h"]h$]h&]uh1j hja hMhj+ ubeh }(h ]jq ah ]h"]f5ah$]h&](jj j^ j j2 ejo Kjr js uh1j
hja hMhjS
hhubeh }(h ]notesah ]h"]notesah$]h&]uh1jL hjN hhhja hMubeh }(h ]multi-touch-mt-protocolah ]h"]multi-touch (mt) protocolah$]h&]uh1jL hhhhhja hKubeh }(h ]h ]h"]h$]h&]sourceja uh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(jQ N generatorN datestampN source_linkN
source_urlN
toc_backlinksentryfootnote_backlinksK
sectnum_xformKstrip_commentsNstrip_elements_with_classesN
strip_classesN report_levelK
halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-sig input_encoding_error_handlerstrictoutput_encodingutf-8 output_encoding_error_handlerj error_encodingutf-8 error_encoding_error_handlerbackslashreplace
language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid
dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourceja _destinationN
_config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthK trim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales] character_level_inline_markupdoctitle_xform
docinfo_xformKsectsubtitle_xform
image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}(hhhhj hj j j j j/ j# j> j2 jM jA j\ jP jk j_ jz jn j j} j j j j j j j j j j j j j j j j j j j j j. j" j= j1 jL j@ j[ jO jj j^ jy jm j j| j j j j j j j j j j j j j j j j j j j j j- j! j< j0 jK j? jZ jN ji j] jx jl j j{ j j j j j j j j j j j j j j j j j j j j j, j j; j/ jJ j> jY jM jh j\ jw jk j jz j j j j j j j j j j j j j j j j j
j j j j+ j j: j. jI j= usubstitution_names}(amphaposhastj brvbarj bsolj centj/ colonj> commajM commatj\ copyjk currenjz darrj degj dividej dollarj equalsj exclj frac12j frac14j frac18j frac34j frac38j frac58j. frac78j= gtjL halfj[ horbarjj hyphenjy iexclj iquestj laquoj larrj lcubj ldquoj lowbarj lparj lsqbj lsquoj ltj microj- middotj< nbspjK notjZ numji ohmjx ordfj ordmj paraj percntj periodj plusj plusmnj poundj questj quotj raquoj rarrj, rcubj; rdquojJ regjY rparjh rsqbjw rsquoj sectj semij shyj solj sungj sup1j sup2j sup3j timesj
tradej uarrj+ verbarj: yenjI urefnames}(f5](j` jT j j( ef3](j j
ef4](j j jA j j
ef1]j` af2]j aurefids}(jo ]j` aj ]j aj ](j j
ej ](j j jA j j
ejq ](j` jT j j( eunameids}(j] jZ j
j j j j[ jX j j j j} jX jU j j j)
j&
jP
jM
jU jR j
jo j
j j j j( j jM jq u nametypes}(j] j
j j[ j j jX j j)
jP
jU j
j
j j( jM uh }(jZ jN j j j j
jj j` j j jX j j j^ j} j j^ jT jU j j j j j jK jA j j j
j
jj j` j j j j j2 j( j j[ j&
j j
j
jM
j,
jR jS
jo j
j j
j j
j j jq j+ u
footnote_refs}(j ](j` jT j j( ej ](j j
ej ](j j jA j j
ej ]j` aj ]j au
citation_refs}
autofootnotes](j
j
j
j j+ eautofootnote_refs](j` j jT j j jA j j
j` j j j( j
esymbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK
id_counter collectionsCounter}j K
sRparse_messages]transform_messages] transformerN include_log],Documentation/input/multi-touch-protocol.rst(NNNNta
decorationNhhub.