From: Jonathan Cameron <jic23@kernel.org>
To: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Cc: kernel@collabora.com, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Gwendal Grignou <gwendal@chromium.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] docs: iio: add precision about sampling_frequency_available
Date: Sun, 26 May 2019 18:40:42 +0100 [thread overview]
Message-ID: <20190526184016.11a56ee0@archlinux> (raw)
In-Reply-To: <c1c56310da539b6af66811084bd69806622e1903.1558601329.git.fabien.lahoudere@collabora.com>
On Thu, 23 May 2019 11:07:37 +0200
Fabien Lahoudere <fabien.lahoudere@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.lahoudere@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-iio@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
prev parent reply other threads:[~2019-05-26 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 9:07 [PATCH v2 0/3] Expose cros_ec_sensors frequency range via iio sysfs Fabien Lahoudere
2019-05-23 9:07 ` [PATCH v2 1/3] iio: common: cros_ec_sensors: support protocol v3 message Fabien Lahoudere
2019-06-12 8:42 ` Lee Jones
2019-06-12 9:58 ` Fabien Lahoudere
2019-05-23 9:07 ` [PATCH v2 2/3] iio: common: cros_ec_sensors: add sysfs attribute for frequencies Fabien Lahoudere
2019-05-26 17:45 ` Jonathan Cameron
2019-05-27 9:55 ` Fabien Lahoudere
2019-05-28 11:04 ` Gwendal Grignou
2019-06-04 14:21 ` Fabien Lahoudere
2019-05-23 9:07 ` [PATCH v2 3/3] docs: iio: add precision about sampling_frequency_available Fabien Lahoudere
2019-05-26 17:40 ` Jonathan Cameron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190526184016.11a56ee0@archlinux \
--to=jic23@kernel.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=fabien.lahoudere@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).