> >> I'm not in favor of a quirk in this particular case: the information > >> is already here: max > 0. > > > > Only if min == 0, which is far from always the case. And setting a > > special value for a special hardware does what a quirk does, so maybe > > it is a quirk after all. > > > > I think there is a misunderstanding: > if the class provides max_x (so > 0), or min_x, that means that the > person in charge of adding the driver wants to replace the two values > min/max. What I meant is that (min_x < max_x) is the proper test. > No need for a quirk that will be redundant with the hand-provided values. Yes, but I think we might be better off using a quirk than a generic way to replace the values provided by the hardware. 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
