>>> FWIW, hid-multitouch already support those devices. >>> ABS_MT_DISTANCE is set with a min/max of 0/1 when we detect win8 >>> certified panels with hovering capability. By default the spec does not >>> provide the distance IIRC, and you only have one byte: InRange. >> >> Hmm, I missed that and this is unfortunate. The ABS capabilities >> advertised by the devices should match their real capabilities. If >> device can't properly report distance it should not be using >> ABS_MT_DISTANCE/ABS_DISTANCE... > > I think the hid-mt behaviour makes sense. Without explicit resolution (and > no device sets that anyway, IIRC) any distance value > min tells us only that a > tool is within detectable range, but not yet touching. Anything between > min/max is only useful as a relative scale, but effectively that [min,max] > range could be a metre or a millimeter, we can't know. So a device with a > 0/1 range simply has low granularity and is only able to detect whether > something is within range or touching the surface. I agree with this, but I also share Dmitry's concern. A device that can detect hovering, if only binary, does in fact coarsely estimate the distance from the touching surface. A device allowing for a smooth approach of objects would simply support a better resolution. From that perspective, using the ABS_MT_DISTANCE capability makes sense. Pragmatically. However, at no point are we really changing the coordinate system, which remains euclidian space. We are simply changing resolution and thresholds for what constitues a touch. Forcing userland to step away from the simple interpretation is what eventually makes the capability impossible to use as intended. So, if we cannot express, using the abs_info data, something like "contains a detector which can coarsely estimate the distance and then uses a detector threshold to set that distance to zero or one", we had better express it in some other way, which is less ambiguous. How about ABS_MT_PRESENT and/or ABS_PRESENT? It would complement TOUCH in the case of hovering, allow the state where the tool is there but not touching, and would unambiguously advertise the capability of detecting presence. It would also be forward compatible with additional capabilities, such as reporting the actual distance to the surface. Henrik -- 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
