Lines Matching refs:contacts

10 devices, a way to report detailed data from multiple contacts, i.e.,
13 drivers to report details for an arbitrary number of contacts.
16 hardware. For devices handling anonymous contacts (type A), the protocol
17 describes how to send the raw data for all contacts to the receiver. For
18 devices capable of tracking identifiable contacts (type B), the protocol
19 describes how to send updates for individual contacts via event slots.
47 type B slot protocol lies in the usage of identifiable contacts to reduce
53 enumeration of the full set of anonymous contacts currently on the
59 Creation, replacement and destruction of contacts is achieved by modifying
68 Some devices identify and/or track more contacts than they can report to the
73 tracking more contacts than it is currently reporting, the driver should use
74 a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
79 Userspace can detect that a driver can report more total contacts than slots
99 The sequence after moving one of the contacts looks exactly the same; the
100 raw data for all present contacts are sent between every synchronization
165 allows for multiple contacts to be tracked.  If the device supports it, the
215 may be used to track identified contacts over time [5].
346 For devices reporting contacts as rectangular shapes, signed orientation
387 problem.  At each event synchronization, the set of actual contacts is
388 matched to the set of contacts from the previous synchronization. A full