> .wipers and .max_pos need not be in max5487_cfg, they are common. > .wipers isn't even used. Which means that if you like, you can > use the ohms reading as the driver_data directly instead of going > via the MAX548x enumeration, see below. Or is there some reason > not doing so? You make a good point. Anyhow we thought of a generic approach. In the future this chip family could support more wipers with different positions. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
