The IIO_CHAN_INFO_PEAK info element is used for maximum values and currently there is no equivalent for minimum values. Instead of overloading the existing peak info element, a new info element can be added. In principle there is no need to add a _TROUGH_SCALE element as the scale will be the same as the one required for INFO_PEAK, which in turn is sometimes omitted if a single scale for peaks and raw values is required. Add an IIO_CHAN_INFO_TROUGH info element for minimum values. Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com> Link: https://lore.kernel.org/r/20231211122747.9723-1-579lpy@gmail.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> |
||
|---|---|---|
| .. | ||
| accel | ||
| adc | ||
| afe | ||
| common | ||
| dac | ||
| frequency | ||
| gyro | ||
| imu | ||
| timer | ||
| buffer-dma.h | ||
| buffer-dmaengine.h | ||
| buffer.h | ||
| buffer_impl.h | ||
| configfs.h | ||
| consumer.h | ||
| driver.h | ||
| events.h | ||
| hw-consumer.h | ||
| iio-gts-helper.h | ||
| iio-opaque.h | ||
| iio.h | ||
| kfifo_buf.h | ||
| machine.h | ||
| sw_device.h | ||
| sw_trigger.h | ||
| sysfs.h | ||
| trigger.h | ||
| trigger_consumer.h | ||
| triggered_buffer.h | ||
| triggered_event.h | ||
| types.h | ||