>> >>> >>>> functions' signature only has one integer >>>> in/out parameter. That makes sense in the context of _raw because the >>>> value isn't yet processed. >>>> >>>> However, as the scale is a number encoded over two ints, the >>>> _processed value should also span two ints. Is there a reason why it's >>>> still only one int? >>> >>> No it certainly should not be one int for exactly the reasons you have >>> stated. >>>> >>>> >> >> I'm not to sure about that. I'd rather add a scale parameter to the >> iio_read_channel_processed, just in the same way the >> convert_raw_to_processed function takes a scale parameter. > > That may be tricky to do given we often have nasty non linear functions > that are the reason we are using processed in the first place. Hmm. > Not sure which way works better. I agree, this is the whole point of using processed. Lars, is there a specific reason why you want to keep reading the value and the scale in different function calls? Guillaume -- 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
