Lines Matching refs:finger

28         5.2.2 One/Three finger touch
29         5.2.3 Two finger touch
33         6.2.1 One/Three finger touch
34         6.2.2 Two finger touch
213          single finger width?
284                firmware 1.x seem to map one, two and three finger taps
287             w = 1 when wide finger touch?
303 when 1 finger is touching, the first 2 position reports must be discarded.
331             tw = 1 when two finger touch
332             th = 1 when three finger touch
333             f  = 1 when finger touch
406 …         (((SA1 & 0x0C) != 0x0C) && ((SA1 & 0xC0) == 0x80)) || // check Byte 1 (one finger pressed)
409 …         (((SB1 & 0x0E) != 0x08) && ((SA1 & 0xC0) == 0x80)) || // check Byte 4 (one finger pressed)
421 5.2.2 One/Three finger touch
450 	 vf = a kind of flag ? (only on EF123, 0 when finger is over one
452 	 w3..w0 = width of the finger touch (not EF113)
478 5.2.3 Two finger touch
499 	 ax8..ax0 = lower-left finger absolute x value
506 	 ay8..ay0 = lower-left finger absolute y value
518          bx8..bx0 = upper-right finger absolute x value
525          by8..by0 = upper-right finger absolute y value
540          T: 1 = enable two finger mode auto correct
546 1 and 3 finger touch shares the same 6-byte packet format, except that
547 3 finger touch only reports the position of the center of all three fingers.
549 Firmware would send 12 bytes of data for 2 finger touch.
553 when number of finger changes, F/W would send "debounce packet" to inform
564 6.2.1 One/Three finger touch
592          w3..w0 = width of the finger touch
608 6.2.2 Two finger touch
611 The packet format is exactly the same for two finger touch, except the hardware
612 sends two 6 byte packets. The first packet contains data for the first finger,
613 the second packet has data for the second finger. So for two finger touch a
638 head packets or motion packets. A head packet contains data of finger id, finger
643 can expect two following head packets. If the finger status doesn't change,
644 the following packets would be motion packets, only sending delta of finger
647 One exception is one finger touch. when a status packet tells us there is only
648 one finger, the hardware would just send head packets afterwards.
665          ft4 ft3 ft2 ft1 ft0 ftn = 1 when finger n is on touchpad
694         w3..w0 = finger width (spans how many trace lines)
713        id2..id0 = finger id
738        id2..id0 = finger id
761        id2..id0 = finger id
777         byte 0 ~ 2 for one finger