On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote: > On Thu, Apr 23, 2015 at 07:10:55PM +0200, Henrik Rydberg wrote: > > > "Creation, replacement and destruction of contacts is achieved by > > > modifying the ABS_MT_TRACKING_ID of the associated slot. A > > > non-negative tracking id is interpreted as a contact, and the value -1 > > > denotes an unused slot. A tracking id not previously present is > > > considered new, and a tracking id no longer present is considered > > > removed." > > > > > > If some userspace is confused with missing -1 tracking ID for that > > > slot, that userspace should be fixed. > > > > I agree. Some userland applications work with add/remove out of convenience, and > > cannot handle the more compressed notation the kernel slot handling allows. > > Fixing those applications will be a good thing. > > > > Unfortunately the patch already appeared in Linus' tree... > > It's in 4.1-rc0 so we can just revert it. > Before we call for a revert, I'd like to hear Peter thoughts about it, as he is the main user of the slotted protocol. Also, Dmitry, can you check if the ChromeOS driver and (or) the android one would need to be adapted? My guess is that none of these drivers are able to handle a silent closing of a slot and the easiest solution might be to simply change the documentation if in fact nobody uses the compressed notation (which removes just one ABS_SLOT event within the frame, so not sure we can call it compressed BTW). Cheers, Benjamin -- 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
