Lines Matching refs:of

9 In order to utilize the full power of the new multi-touch and multi-user
13 drivers to report details for an arbitrary number of contacts.
15 The protocol is divided into two types, depending on the capabilities of the
18 devices capable of tracking identifiable contacts (type B), the protocol
25 Contact details are sent sequentially as separate packets of ABS_MT
26 events. Only the ABS_MT events are recognized as part of a contact
28 applications, the MT protocol can be implemented on top of the ST protocol
32 input_mt_sync() at the end of each packet. This generates a SYN_MT_REPORT
37 input_mt_slot(), with a slot as argument, at the beginning of each packet.
39 prepare for updates of the given slot.
41 All drivers mark the end of a multi-touch transfer by calling the usual
44 of events/packets.
47 type B slot protocol lies in the usage of identifiable contacts to reduce
48 the amount of data sent to userspace. The slot protocol requires the use of
53 enumeration of the full set of anonymous contacts currently on the
59 Creation, replacement and destruction of contacts is achieved by modifying
60 the ABS_MT_TRACKING_ID of the associated slot.  A non-negative tracking id
64 the full state of each initiated contact has to reside in the receiving
66 attribute of the current slot.
70 contact that is reported by the hardware.  Whenever the identity of the
74 a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
81 total number of type B slots reported in the absinfo for the ABS_MT_SLOT axis.
83 The minimum value of the ABS_MT_SLOT axis must be 0.
99 The sequence after moving one of the contacts looks exactly the same; the
115 If the driver reports one of BTN_TOUCH or ABS_PRESSURE in addition to the
149 message removes the association of slot 0 with contact 45, thereby
162 A set of ABS_MT events with the desired properties is defined. The events
164 minimum set consists of ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which
167 of the contact area and approaching tool, respectively.
171 glass.  You will see two regions, one inner region consisting of the part
172 of the finger actually touching the glass, and one outer region formed by
173 the perimeter of the finger. The center of the touching region (a) is
174 ABS_MT_POSITION_X/Y and the center of the approaching finger (b) is
181 instead. Devices capable of contact hovering can use ABS_MT_DISTANCE to
204 In addition to the MAJOR parameters, the oval shape of the touch and finger
206 and MINOR are the major and minor axis of an ellipse. The orientation of
208 direction of the finger ellipse is given by the vector (a - b).
210 For type A devices, further specification of the touch shape is possible
227 The length of the major axis of the contact. The length should be given in
229 possible value of ABS_MT_TOUCH_MAJOR is sqrt(X^2 + Y^2), the diagonal [4].
233 The length, in surface units, of the minor axis of the contact. If the
238 The length, in surface units, of the major axis of the approaching
239 tool. This should be understood as the size of the tool itself. The
240 orientation of the contact and the approaching tool are assumed to be the
245 The length, in surface units, of the minor axis of the approaching
250 the notion of pressure. The fingers of the hand and the palm all have
256 of TOUCH and WIDTH for pressure-based devices or any device with a spatial
267 The orientation of the touching ellipse. The value should describe a signed
268 quarter of a revolution clockwise around the touch center. The signed value
270 the Y axis of the surface, a negative value when the ellipse is turned to
275 Touch ellipsis are symmetrical by default. For devices capable of true 360
277 indicate more than a quarter of a revolution. For an upside-down finger,
283 not (uniquely) any values in between. In such cases, the range of
288 The surface X coordinate of the center of the touching ellipse.
292 The surface Y coordinate of the center of the touching ellipse.
296 The surface X coordinate of the center of the approaching tool. Omit if
302 The surface Y coordinate of the center of the approaching tool. Omit if the
306 The four position values can be used to separate the position of the touch
307 from the position of the tool. If both positions are present, the major
313 The type of approaching tool. A lot of kernel drivers cannot distinguish
325 contact. The sequence of points forms a polygon which defines the shape of
333 [5]. The value range of the TRACKING_ID should be large enough to ensure
334 unique identification of a contact maintained over an extended period of
342 The flora of different hardware unavoidably leads to some devices fitting
347 cannot be obtained. Assuming X and Y are the lengths of the sides of the
355 The range of ABS_MT_ORIENTATION should be set to [0, 1], to indicate that
376 Rationale: We have no information about the orientation of the touching
385 The process of finger tracking, i.e., to assign a unique trackingID to each
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
395 In the specific application of creating gesture events, the TOUCH and WIDTH
397 between index finger and thumb. With the addition of the MINOR parameters,
399 and with ORIENTATION, one can detect twisting of fingers.
409 subsequent events of the same type refer to different fingers.
411 For example usage of the type A protocol, see the bcm5974 driver. For
412 example usage of the type B protocol, see the hid-egalax driver.
415 [2] The list can of course be extended.