On Thu, 23 May 2019 11:07:37 +0200 Fabien Lahoudere <fabien.lahoud...@collabora.com> wrote:
> The documentation give some exemple on what format can be expected > from sampling_frequency_available sysfs attribute > > Signed-off-by: Fabien Lahoudere <fabien.lahoud...@collabora.com> Great. Applied to the togreg branch of iio.git and pushed out as testing for the autobuilders to completely ignore ;) Thanks, Jonathan > --- > Documentation/ABI/testing/sysfs-bus-iio | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/Documentation/ABI/testing/sysfs-bus-iio > b/Documentation/ABI/testing/sysfs-bus-iio > index 6aef7dbbde44..680451695422 100644 > --- a/Documentation/ABI/testing/sysfs-bus-iio > +++ b/Documentation/ABI/testing/sysfs-bus-iio > @@ -61,8 +61,11 @@ What: > /sys/bus/iio/devices/triggerX/sampling_frequency_available > KernelVersion: 2.6.35 > Contact: linux-...@vger.kernel.org > Description: > - When the internal sampling clock can only take a small > - discrete set of values, this file lists those available. > + When the internal sampling clock can only take a specific set of > + frequencies, we can specify the available values with: > + - a small discrete set of values like "0 2 4 6 8" > + - a range with minimum, step and maximum frequencies like > + "[min step max]" > > What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio > KernelVersion: 2.6.38
