From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Marcin Niestroj <m.niestroj@grinn-global.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Gregor Boirie <gregor.boirie@parrot.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: st_pressure: Export sampling frequency for lps25h and lps331ap
Date: Fri, 30 Dec 2016 11:34:39 +0000 [thread overview]
Message-ID: <6fdaebff-16bd-9d73-013c-fdddfdc21bbc@kernel.org> (raw)
In-Reply-To: <CACRpkda3H15KSv9U8e38hb0C+7dNz01MrdgCYwb=PqEdq89q0Q@mail.gmail.com>
On 13/12/16 08:52, Linus Walleij wrote:
> On Mon, Dec 12, 2016 at 5:58 PM, Marcin Niestroj
> <m.niestroj@grinn-global.com> wrote:
>
>> Both devices are using the same iio_chan_spec to define which settings
>> are exported with sysfs. Both are properly configured to set/get
>> sampling frequency for pressure and temperature. They also properly
>> export available sampling frequencies. The only missing thing is
>> sampling_frequency sysfs file, which allows to set/get this property
>> from userspace.
>>
>> Add sampling frequency to iio channel info mask, so sampling_frequency
>> file is properly exported using sysfs.
>>
>> Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Yours,
> Linus Walleij
>
Applied to the togreg branch of iio.git and pushed out as
testing for the autobuilders to play with it.
Thanks,
Jonathan
next prev parent reply other threads:[~2016-12-30 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 16:58 [PATCH 1/2] iio: st_pressure: Fix data sign Marcin Niestroj
2016-12-12 16:58 ` [PATCH 2/2] iio: st_pressure: Export sampling frequency for lps25h and lps331ap Marcin Niestroj
2016-12-13 8:52 ` Linus Walleij
2016-12-30 11:34 ` Jonathan Cameron [this message]
2016-12-13 8:51 ` [PATCH 1/2] iio: st_pressure: Fix data sign Linus Walleij
2016-12-30 11:33 ` Jonathan Cameron
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=6fdaebff-16bd-9d73-013c-fdddfdc21bbc@kernel.org \
--to=jic23@kernel.org \
--cc=gregor.boirie@parrot.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=m.niestroj@grinn-global.com \
--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).