summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/iio
diff options
context:
space:
mode:
authorFabien Lahoudere <fabien.lahoudere@collabora.com>2019-07-16 11:11:06 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2019-07-27 23:15:08 +0100
commitae7b02ad2f32d39d1434655f346c04a16c1aa703 (patch)
tree9230bbf83261b35be0da7a9e185316742f172d86 /Documentation/devicetree/bindings/iio
parent9566cb1ddb81c4f232d08cb2c7aff5b947959381 (diff)
downloadlinux-ae7b02ad2f32d39d1434655f346c04a16c1aa703.tar.bz2
iio: common: cros_ec_sensors: Expose cros_ec_sensors frequency range via iio sysfs
Embedded controller return minimum and maximum frequencies, unfortunately we have no way to know the step for all available frequencies. Even if not complete, we can return a list of known values using the standard read_avail callback (IIO_CHAN_INFO_SAMP_FREQ) to provide them to userland. Now cros_ec_* sensors provides frequencies values in sysfs like this: "0 min max". 0 is always true to disable the sensor. Default frequencies are provided for earlier protocol. Signed-off-by: Nick Vaccaro <nvaccaro@chromium.org> Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com> [rebased on top of iio/testing and solved conflicts] Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'Documentation/devicetree/bindings/iio')
0 files changed, 0 insertions, 0 deletions