Lines Matching refs:should

52 For type A devices, the kernel driver should generate an arbitrary
57 For type B devices, the kernel driver should associate a slot with each
69 driver.  A driver for such a device should associate one type B slot with each
71 contact associated with a slot changes, the driver should invalidate that
73 tracking more contacts than it is currently reporting, the driver should use
75 being tracked by the hardware at that moment.  The driver should do this by
78 The driver should only advertise as many slots as the hardware can report.
218 implicitly handled by input core; drivers should instead call
227 The length of the major axis of the contact. The length should be given in
239 tool. This should be understood as the size of the tool itself. The
267 The orientation of the touching ellipse. The value should describe a signed
269 range is arbitrary, but zero should be returned for an ellipse aligned with
272 right. When completely aligned with the X axis, the range max should be
278 range max * 2 should be returned.
284 ABS_MT_ORIENTATION should be [0, 1] [4].
315 event should be omitted. The protocol currently supports MT_TOOL_FINGER,
317 by input core; drivers should instead use input_mt_report_slot_state().
327 should not be confused with the high-level trackingID [5]. Most type A
333 [5]. The value range of the TRACKING_ID should be large enough to ensure
336 should instead use input_mt_report_slot_state().
355 The range of ABS_MT_ORIENTATION should be set to [0, 1], to indicate that
378 ellipse should align with the vector (T - C), so the diameter must