Userspace can also read the range that is acceptable from out_voltage0_raw_available [0 1 2^16-1] and hence not write an invalid value in the first place - which is obviously preferred to getting an error. Scaling etc is also expressed to userspace so it it wants to write a particular voltage it can perform the appropriate scaling. Note that moving linear scaling like this to userspace allows easy use of floating point + may be a significant performance advantage if using the chrdev interface which uses the same approach (and values) as the sysfs interface. Jonathan > > > > > > > I can understand your reasoning but again this is something that I > > > > > > never really saw being enforced. So, I'm more than ok to change it if > > > > > > it really becomes something that we will try to "enforce" in IIO. > > > > > > Otherwise it just feels as a random nitpick :). > > > > > > > > > > No, this is about consistency and common sense. If you define type uXX, > > > > > we have an API for that exact type. It's confusing why POD type APIs > > > > > are used with fixed-width types or vise versa. > > > > > > > > > > Moreover (which is pure theoretical, though) some architectures might > > > > > have no (mutual) equivalency between these types. >
