Home
last modified time | relevance | path

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

/linux-4.1.27/drivers/input/touchscreen/
Dst1232.c53 struct st1232_ts_finger finger[MAX_FINGERS]; member
60 struct st1232_ts_finger *finger = ts->finger; in st1232_ts_read_data() local
84 finger[0].is_valid = buf[2] >> 7; in st1232_ts_read_data()
85 finger[1].is_valid = buf[5] >> 7; in st1232_ts_read_data()
88 if (finger[0].is_valid) { in st1232_ts_read_data()
89 finger[0].x = ((buf[2] & 0x0070) << 4) | buf[3]; in st1232_ts_read_data()
90 finger[0].y = ((buf[2] & 0x0007) << 8) | buf[4]; in st1232_ts_read_data()
91 finger[0].t = buf[8]; in st1232_ts_read_data()
94 if (finger[1].is_valid) { in st1232_ts_read_data()
95 finger[1].x = ((buf[5] & 0x0070) << 4) | buf[6]; in st1232_ts_read_data()
[all …]
Dili210x.c20 struct finger { struct
29 struct finger finger[MAX_TOUCHES]; member
33 struct finger finger_max;
84 const struct finger *finger; in ili210x_report_events() local
89 finger = &touchdata->finger[i]; in ili210x_report_events()
94 x = finger->x_low | (finger->x_high << 8); in ili210x_report_events()
95 y = finger->y_low | (finger->y_high << 8); in ili210x_report_events()
Dzforce_ts.c236 static int zforce_scan_frequency(struct zforce_ts *ts, u16 idle, u16 finger, in zforce_scan_frequency() argument
242 (finger & 0xff), ((finger >> 8) & 0xff), in zforce_scan_frequency()
247 idle, finger, stylus); in zforce_scan_frequency()
DKconfig317 system. It also supports 5-finger chip models, which can be
/linux-4.1.27/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()
177 unsigned int finger; in focaltech_process_abs_packet() local
179 finger = (packet[1] >> 4) - 1; in focaltech_process_abs_packet()
180 if (finger >= FOC_MAX_FINGERS) { in focaltech_process_abs_packet()
182 finger); in focaltech_process_abs_packet()
188 state->fingers[finger].x = ((packet[1] & 0xf) << 8) | packet[2]; in focaltech_process_abs_packet()
189 state->fingers[finger].y = (packet[3] << 8) | packet[4]; in focaltech_process_abs_packet()
[all …]
Dnavpoint.c84 int finger; in navpoint_packet() local
94 finger = (navpoint->data[1] & 0x01); in navpoint_packet()
99 input_report_key(navpoint->input, BTN_TOUCH, finger); in navpoint_packet()
103 input_report_key(navpoint->input, BTN_TOOL_FINGER, finger); in navpoint_packet()
/linux-4.1.27/Documentation/input/
Delantech.txt28 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
[all …]
Dsentelic.txt144 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
169 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
216 Sample sequence of Multi-finger, Multi-coordinate mode:
234 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
237 Bit4 => finger up/down information. 1: finger down, 0: finger up.
239 Bit2 => finger index, 0 is the first finger, 1 is the second finger.
261 Bit5 => Valid bit, 0 means that the coordinate is invalid or finger up.
264 Bit4 => finger up/down information. 1: finger down, 0: finger up.
266 Bit2 => finger index, 0 is the first finger, 1 is the second finger.
310 Sample sequence of Multi-finger, Multi-coordinate mode:
[all …]
Dmulti-touch-protocol.txt55 important. Event filtering and finger tracking is left to user space [3].
170 looking through a window at someone gently holding a finger against the
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
175 ABS_MT_TOOL_X/Y. The touch diameter is ABS_MT_TOUCH_MAJOR and the finger
176 diameter is ABS_MT_WIDTH_MAJOR. Now imagine the person pressing the finger
204 In addition to the MAJOR parameters, the oval shape of the touch and finger
208 direction of the finger ellipse is given by the vector (a - b).
214 finger or a pen or something else. Finally, the ABS_MT_TRACKING_ID event
[all …]
Dappletouch.txt27 will give additional functionalities, like acceleration, scrolling, 2 finger
28 tap for middle button mouse emulation, 3 finger tap for right button mouse
71 is not perfect. If finger movements are not recognized anymore, try reloading
Dntrig.txt36 When the last finger is removed from the device, it sends a number of empty
38 erroneous disconnects, where the sensor may mistakenly not detect a finger that
68 where no finger was actually touching the screen.
99 a mechanism for filtering out ghosts in the form of an extra finger while
Devent-codes.txt135 - These codes denote one, two, three, and four finger interaction on a
140 purpose. A trackpad event generated by finger touches should generate events
144 Note: Historically some drivers emitted multiple of the finger count codes with
305 The guidelines below ensure proper single-touch and multi-finger functionality.
332 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
Dalps.txt165 bitmaps a given bit is set if there is a finger covering that position on the
167 data, although finger tracking is not possible. This packet also encodes the
/linux-4.1.27/net/netfilter/
Dxt_osf.c42 struct xt_osf_user_finger finger; member
84 memcpy(&kf->finger, f, sizeof(struct xt_osf_user_finger)); in xt_osf_add_callback()
87 if (memcmp(&sf->finger, f, sizeof(struct xt_osf_user_finger))) in xt_osf_add_callback()
121 if (memcmp(&sf->finger, f, sizeof(struct xt_osf_user_finger))) in xt_osf_remove_callback()
230 f = &kf->finger; in xt_osf_match_packet()
/linux-4.1.27/drivers/staging/ste_rmi4/
Dsynaptics_i2c_rmi4.c307 int finger; in synpatics_rmi4_touchpad_report() local
351 for (finger = 0; finger < fingers_supported; finger++) { in synpatics_rmi4_touchpad_report()
353 reg = finger/4; in synpatics_rmi4_touchpad_report()
355 finger_shift = (finger % 4) * 2; in synpatics_rmi4_touchpad_report()
361 input_mt_slot(input_dev, finger); in synpatics_rmi4_touchpad_report()
368 ((finger * data_reg_blk_size) + in synpatics_rmi4_touchpad_report()
/linux-4.1.27/drivers/hid/
Dhid-logitech-hidpp.c650 struct hidpp_touchpad_raw_xy_finger *finger) in hidpp_touchpad_touch_event() argument
655 finger->x = x_m << 6 | data[1]; in hidpp_touchpad_touch_event()
656 finger->y = y_m << 6 | data[3]; in hidpp_touchpad_touch_event()
658 finger->contact_type = data[0] >> 6; in hidpp_touchpad_touch_event()
659 finger->contact_status = data[2] >> 6; in hidpp_touchpad_touch_event()
661 finger->z = data[4]; in hidpp_touchpad_touch_event()
662 finger->area = data[5]; in hidpp_touchpad_touch_event()
663 finger->finger_id = data[6] >> 4; in hidpp_touchpad_touch_event()
Dwacom_sys.c176 bool finger = WACOM_FINGER_FIELD(field); in wacom_usage_mapping() local
184 if (!pen && !finger) in wacom_usage_mapping()
193 if (finger && !features->touch_max) in wacom_usage_mapping()
200 if (finger) { in wacom_usage_mapping()
213 if (finger) { in wacom_usage_mapping()
/linux-4.1.27/Documentation/development-process/
D5.Posting116 finger the last patch as the one which caused the problem, even though
/linux-4.1.27/Documentation/
Dpinctrl.txt398 a certain physical pin (ball, pad, finger, etc) for multiple mutually exclusive
Dkernel-parameters.txt2094 [MOUSE] Maximum time between finger touching and