Hi Jonathan, [...] > >> For the range, it's an interesting one. Again the term range could > >> mean too many things within the wider ABI. We need to make it more > >> specific. > >> > >> Actually reading the datasheet, I think this is fundamentally about the > >> maximum sampling frequency rather than directly about the range. > >> The only reason you'd reduce the range is to speed that up. It doesn't > >> improve the resolution, the device simply answers quicker. > >> > >> So I'd support this as sampling_frequency. You could then use > >> the the iio_info_mask_*_available and relevant callback to provide > >> info on what it then restricts the possible output values to > >> (rather than controlling it directly). > >> > > > > By changing the range one cannot influence the sampling frequency directly. I > > have seen on the oszilloscope that the telegrams arrive almost at the same time > > with different settings of range and the same gain. > > > > Only if the gain is also adjusted the sensor works faster and a higher frequency > > can be used. But the gain is also used to adjust the sensitivity of the sensor. > That's rather weird and not what the datasheet suggests. Ah well. > > > > What about calling it "sensor_domain" or "sensor_max_range"? > hmm. Not sure - propose that with appropriate Docs and we can think more on it. > > > > I made a mistake in the earlier mentioned measurement which i have to correct: The telegrams arrive faster with a smaller range and the same gain. But we cannot use the sensor at a higher frequency if we are not adjusting the gain of the sensor as well. This is because of echos of the former cycle which are still around. And this setting of the gain depends on the surrounding where the sensor is used. So in the driver we cannot estimate it. Therefore i'll send out the next version with the attribute name "sensor_max_range" together with documentation as proposal. Andreas -- -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
