> Originally, I set an arbitrary maximum bound of 20 slots. In the > interests of keeping it simple, I decided to remove that bound when I > submitted the patch for review here. > > How about: > > mt_slots = min(MAX_MT_SLOTS_TO_INFER_FROM_TRACKING_ID_RANGE, > dev->absinfo[ABS_MT_TRACKING_ID].maximum - > dev->absinfo[ABS_MT_TRACKING_ID].minimum + 1); > > Where MAX_MT_SLOTS_TO_INFER_FROM_TRACKING_ID_RANGE is set to 32 or something. Sure, 32 works for me. > There's also the question of how many slots we should infer when > neither ABS_MT_SLOT or ABS_MT_TRACKING_ID is available. The drivers > I've seen that don't provide tracking ids, are very basic and tend to > only support 2 touch points. There is the bcm5974 driver, but it sets its own limit, so 2 is fine. > I guess we could add a DEFAULT_NUMBER_OF_MT_SLOTS constant to handle that case. > > Please feel free to suggest better names for these constants. With the same interest of keeping it simple in mind, inserting the actual values is fine. We do not expect to duplicate the decisions made in this function anywhere else. Thanks, 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
