Searched refs:contacts (Results 1 – 8 of 8) sorted by relevance
/linux-4.1.27/drivers/input/mouse/ |
D | cypress_ps2.c | 460 report_data->contacts[0].x = in cypress_parse_packet() 462 report_data->contacts[0].y = in cypress_parse_packet() 465 report_data->contacts[0].z = packet[4]; in cypress_parse_packet() 468 report_data->contacts[0].x = in cypress_parse_packet() 470 report_data->contacts[0].y = in cypress_parse_packet() 473 report_data->contacts[0].z = packet[4]; in cypress_parse_packet() 475 report_data->contacts[1].x = in cypress_parse_packet() 477 report_data->contacts[1].y = in cypress_parse_packet() 480 report_data->contacts[1].z = report_data->contacts[0].z; in cypress_parse_packet() 506 report_data->contacts[i].x, in cypress_parse_packet() [all …]
|
D | cypress_ps2.h | 144 struct cytp_contact contacts[CYTP_MAX_MT_SLOTS]; member
|
/linux-4.1.27/Documentation/input/ |
D | multi-touch-protocol.txt | 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 [all …]
|
D | ntrig.txt | 67 seeing both inappropriately dropped contact and ghosts, contacts reported 71 not address the problem of dropping one of more contacts while other contacts 75 As observed ghost contacts are similar to actual use of the sensor, but they 126 contacts are active they seem to be sorted primarily by Y position.
|
D | alps.txt | 168 number of contacts (f1 and f0 in the table below). 178 usually only appears when there are two or more contacts (although
|
D | event-codes.txt | 272 of multiple contacts without resolving the individual positions; only the 273 number of contacts and a rectangular shape is known. For such
|
/linux-4.1.27/Documentation/security/ |
D | keys-request-key.txt | 110 instantiate key U, using key W as a reference (perhaps it contacts a
|
/linux-4.1.27/fs/cifs/ |
D | Kconfig | 159 an upcall mechanism for CIFS which contacts userspace helper
|