Home
last modified time | relevance | path

Searched refs:finger (Results 1 – 25 of 25) sorted by relevance

/linux-6.1.9/drivers/input/mouse/
Dfocaltech.c123 struct focaltech_finger_state *finger = &state->fingers[i]; in focaltech_report_state() local
124 bool active = finger->active && finger->valid; in focaltech_report_state()
135 clamped_x = clamp(finger->x, 0U, priv->x_max); in focaltech_report_state()
136 clamped_y = clamp(finger->y, 0U, priv->y_max); in focaltech_report_state()
178 unsigned int finger; in focaltech_process_abs_packet() local
180 finger = (packet[1] >> 4) - 1; in focaltech_process_abs_packet()
181 if (finger >= FOC_MAX_FINGERS) { in focaltech_process_abs_packet()
183 finger); in focaltech_process_abs_packet()
189 state->fingers[finger].x = ((packet[1] & 0xf) << 8) | packet[2]; in focaltech_process_abs_packet()
190 state->fingers[finger].y = (packet[3] << 8) | packet[4]; in focaltech_process_abs_packet()
[all …]
Dnavpoint.c81 int finger; in navpoint_packet() local
91 finger = (navpoint->data[1] & 0x01); in navpoint_packet()
96 input_report_key(navpoint->input, BTN_TOUCH, finger); in navpoint_packet()
100 input_report_key(navpoint->input, BTN_TOOL_FINGER, finger); in navpoint_packet()
/linux-6.1.9/Documentation/input/devices/
Delantech.rst26 5.2.2 One/Three finger touch
27 5.2.3 Two finger touch
31 6.2.1 One/Three finger touch
32 6.2.2 Two finger touch
207 single finger width?
282 firmware 1.x seem to map one, two and three finger taps
285 w = 1 when wide finger touch?
301 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
[all …]
Dsentelic.rst164 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
189 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
236 Sample sequence of Multi-finger, Multi-coordinate mode:
256 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
259 Bit4 => finger up/down information. 1: finger down, 0: finger up.
261 Bit2 => finger index, 0 is the first finger, 1 is the second finger.
283 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
286 Bit4 => finger up/down information. 1: finger down, 0: finger up.
288 Bit2 => finger index, 0 is the first finger, 1 is the second finger.
333 Sample sequence of Multi-finger, Multi-coordinate mode:
[all …]
Dappletouch.rst32 will give additional functionalities, like acceleration, scrolling, 2 finger
33 tap for middle button mouse emulation, 3 finger tap for right button mouse
76 is not perfect. If finger movements are not recognized anymore, try reloading
Dntrig.rst42 When the last finger is removed from the device, it sends a number of empty
44 erroneous disconnects, where the sensor may mistakenly not detect a finger that
79 where no finger was actually touching the screen.
110 a mechanism for filtering out ghosts in the form of an extra finger while
Dalps.rst174 bitmaps a given bit is set if there is a finger covering that position on the
176 data, although finger tracking is not possible. This packet also encodes the
390 OVF: 5th finger detected
/linux-6.1.9/drivers/input/touchscreen/
Dsurface3_spi.c67 struct surface3_ts_data_finger *finger) in surface3_spi_report_touch() argument
69 int st = finger->status & 0x01; in surface3_spi_report_touch()
73 get_unaligned_le16(&finger->tracking_id)); in surface3_spi_report_touch()
82 get_unaligned_le16(&finger->x)); in surface3_spi_report_touch()
85 get_unaligned_le16(&finger->y)); in surface3_spi_report_touch()
88 get_unaligned_le16(&finger->width)); in surface3_spi_report_touch()
91 get_unaligned_le16(&finger->height)); in surface3_spi_report_touch()
100 struct surface3_ts_data_finger *finger; in surface3_spi_process_touch() local
102 finger = (struct surface3_ts_data_finger *)&data[17 + in surface3_spi_process_touch()
111 if (finger->status & 0x10) in surface3_spi_process_touch()
[all …]
Dili210x.c48 bool (*parse_touch_data)(const u8 *data, unsigned int finger,
108 unsigned int finger, in ili210x_touchdata_to_coords() argument
112 if (!(touchdata[0] & BIT(finger))) in ili210x_touchdata_to_coords()
115 *x = get_unaligned_be16(touchdata + 1 + (finger * 4) + 0); in ili210x_touchdata_to_coords()
116 *y = get_unaligned_be16(touchdata + 1 + (finger * 4) + 2); in ili210x_touchdata_to_coords()
164 unsigned int finger, in ili211x_touchdata_to_coords() argument
170 data = get_unaligned_be32(touchdata + 1 + (finger * 4) + 0); in ili211x_touchdata_to_coords()
174 *x = ((touchdata[1 + (finger * 4) + 0] & 0xf0) << 4) | in ili211x_touchdata_to_coords()
175 touchdata[1 + (finger * 4) + 1]; in ili211x_touchdata_to_coords()
176 *y = ((touchdata[1 + (finger * 4) + 0] & 0x0f) << 8) | in ili211x_touchdata_to_coords()
[all …]
Dzforce_ts.c239 static int zforce_scan_frequency(struct zforce_ts *ts, u16 idle, u16 finger, in zforce_scan_frequency() argument
245 (finger & 0xff), ((finger >> 8) & 0xff), in zforce_scan_frequency()
250 idle, finger, stylus); in zforce_scan_frequency()
DKconfig395 system. It also supports 5-finger chip models, which can be
/linux-6.1.9/Documentation/input/
Dmulti-touch-protocol.rst62 important. Event filtering and finger tracking is left to user space [#f3]_.
177 looking through a window at someone gently holding a finger against the
179 of the finger actually touching the glass, and one outer region formed by
180 the perimeter of the finger. The center of the touching region (a) is
181 ABS_MT_POSITION_X/Y and the center of the approaching finger (b) is
182 ABS_MT_TOOL_X/Y. The touch diameter is ABS_MT_TOUCH_MAJOR and the finger
183 diameter is ABS_MT_WIDTH_MAJOR. Now imagine the person pressing the finger
213 In addition to the MAJOR parameters, the oval shape of the touch and finger
217 direction of the finger ellipse is given by the vector (a - b).
223 finger or a pen or something else. Finally, the ABS_MT_TRACKING_ID event
[all …]
Devent-codes.rst169 - These codes denote one, two, three, and four finger interaction on a
174 purpose. A trackpad event generated by finger touches should generate events
178 Note: Historically some drivers emitted multiple of the finger count codes with
252 A finger flattens with pressure, causing a larger contact area and thus
406 The guidelines below ensure proper single-touch and multi-finger functionality.
436 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
/linux-6.1.9/net/netfilter/
Dnfnetlink_osf.c222 f = &kf->finger; in nf_osf_match()
281 f = &kf->finger; in nf_osf_find()
322 memcpy(&kf->finger, f, sizeof(struct nf_osf_user_finger)); in nfnl_osf_add_callback()
325 if (memcmp(&sf->finger, f, sizeof(struct nf_osf_user_finger))) in nfnl_osf_add_callback()
362 if (memcmp(&sf->finger, f, sizeof(struct nf_osf_user_finger))) in nfnl_osf_remove_callback()
/linux-6.1.9/Documentation/devicetree/bindings/input/rmi4/
Drmi_f01.txt20 - syna,doze-holdoff-ms: The delay to wait after the last finger lift and the
22 - syna,doze-interval-ms: The time period that the device sleeps between finger
/linux-6.1.9/Documentation/hid/
Dhid-alps.rst47 ReportID-3 (Input Reports) (Vendor Usage: Max 10 finger data) for TP
151 X Absolute data of the "n"th finger
153 Y Absolute data of the "n"th finger
155 Operation area of the "n"th finger
/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-driver-hid-ntrig18 When the last finger is removed from the device, it sends a
21 sensor may mistakenly not detect a finger that is still present.
/linux-6.1.9/include/linux/netfilter/
Dnfnetlink_osf.h21 struct nf_osf_user_finger finger; member
/linux-6.1.9/Documentation/devicetree/bindings/input/touchscreen/
Dimx6ul_tsc.txt10 This xnur-gpio returns to low once the finger leave the touch screen (The
/linux-6.1.9/drivers/hid/
Dhid-logitech-hidpp.c2062 struct hidpp_touchpad_raw_xy_finger *finger) in hidpp_touchpad_touch_event() argument
2067 finger->x = x_m << 6 | data[1]; in hidpp_touchpad_touch_event()
2068 finger->y = y_m << 6 | data[3]; in hidpp_touchpad_touch_event()
2070 finger->contact_type = data[0] >> 6; in hidpp_touchpad_touch_event()
2071 finger->contact_status = data[2] >> 6; in hidpp_touchpad_touch_event()
2073 finger->z = data[4]; in hidpp_touchpad_touch_event()
2074 finger->area = data[5]; in hidpp_touchpad_touch_event()
2075 finger->finger_id = data[6] >> 4; in hidpp_touchpad_touch_event()
Dwacom_sys.c430 bool finger = WACOM_FINGER_FIELD(field); in wacom_usage_mapping() local
441 else if (finger) in wacom_usage_mapping()
451 if (finger) { in wacom_usage_mapping()
462 if (finger) { in wacom_usage_mapping()
/linux-6.1.9/Documentation/devicetree/bindings/input/
Diqs626a.yaml693 Directs the device to interpret axial gestures as a swipe (finger
694 remains on trackpad) instead of a flick (finger leaves trackpad).
/linux-6.1.9/Documentation/process/
D5.Posting.rst122 finger the last patch as the one which caused the problem, even though
/linux-6.1.9/Documentation/driver-api/
Dpin-control.rst398 a certain physical pin (ball, pad, finger, etc) for multiple mutually exclusive
/linux-6.1.9/Documentation/admin-guide/
Dkernel-parameters.txt3334 [MOUSE] Maximum time between finger touching and