Lines Matching refs:contacts

14 devices, a way to report detailed data from multiple contacts, i.e.,
17 drivers to report details for an arbitrary number of contacts.
20 hardware. For devices handling anonymous contacts (type A), the protocol
21 describes how to send the raw data for all contacts to the receiver. For
22 devices capable of tracking identifiable contacts (type B), the protocol
23 describes how to send updates for individual contacts via event slots.
54 type B slot protocol lies in the usage of identifiable contacts to reduce
60 enumeration of the full set of anonymous contacts currently on the
66 Creation, replacement and destruction of contacts is achieved by modifying
75 Some devices identify and/or track more contacts than they can report to the
80 tracking more contacts than it is currently reporting, the driver should use
81 a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
86 Userspace can detect that a driver can report more total contacts than slots
106 The sequence after moving one of the contacts looks exactly the same; the
107 raw data for all present contacts are sent between every synchronization
172 allows for multiple contacts to be tracked.  If the device supports it, the
224 may be used to track identified contacts over time [#f5]_.
342 For devices reporting contacts as rectangular shapes, signed orientation
383 problem.  At each event synchronization, the set of actual contacts is
384 matched to the set of contacts from the previous synchronization. A full