Daniel Kurtz wrote: > Instead of carrying around per-finger state in the driver instance, just > report each finger as it arrives to the input layer, and let the input > layer (evdev) hold the event state (which it does anyway). > > Also, the atmel pad reports "amplitude", which is reported to userspace > using the "PRESSURE" event type. The variables now reflect this. > > Note: this driver does not really do MT-B properly. Each input report > (a goup of input events followed by a SYN_REPORT) only contains data for > a single contact. When multiple fingers are present on a device, each is > properly reported in its own MT_SLOT. However, there is only ever one > MT_SLOT per SYN_REPORT. This is fixed in a subsequent patch. > > Signed-off-by: Daniel Kurtz <djkurtz@xxxxxxxxxxxx> This seems to be a good improvement, assuming it is valid. Which platforms have you tested it on? -- Nick Dyer Software Engineer, ITDev Ltd Hardware and Software Development Consultancy Website: http://www.itdev.co.uk -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
