From: Jonathan Cameron <jic23@kernel.org>
To: Jian-Hong Pan <jian-hong@endlessm.com>
Cc: denis.ciocca@st.com, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Dominique Martinet <asmadeus@codewreck.org>,
linux-iio@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux@endlessm.com
Subject: Re: [PATCH] iio: st_sensors: Fix the sleep time for sampling
Date: Sun, 25 Nov 2018 13:22:57 +0000 [thread overview]
Message-ID: <20181125132257.6ae9fe82@archlinux> (raw)
In-Reply-To: <CAPpJ_ed-A_mkPJieZA4pHaRbY0SGpOEXP04aY4g1b60PzMGQuA@mail.gmail.com>
On Wed, 21 Nov 2018 13:13:40 +0800
Jian-Hong Pan <jian-hong@endlessm.com> wrote:
> Denis CIOCCA <denis.ciocca@st.com> 於 2018年11月20日 週二 上午3:05寫道:
> >
> > Hi Jian,
> >
> > Not clear to me why should be + instead of *.
> >
> > ODR is expressed in Hz, so (1/Hz) = period in seconds (1 sample sampling time) [s]
> > 1000 * (1/Hz) = period in milliseconds (1 sample sampling time) [ms]
> > n * 1000 * (1/Hz) = n times period in milliseconds (n times sample sampling time) [ms]
> >
> > In your case you assume bootime is in milliseconds.
>
> Yes, I assume that according to the original comment.
>
> >Maybe we can change the comment and use 'number of samples ...'.
>
> Making the meaning more clear is better.
>
> However, does the bootime of the measurement need as the long time to
> be enabled?
> If the sampling rate is 1Hz and n is 2, then they will do msleep with
> 2000 ms for each st_sensors_read_info_raw.
Superficially that seems correct as we need to be sure that a reading
has occurred. If you want it to be quicker than the ODR should be set
faster so that the reading shows up reasonably quickly. At 1Hz and
you want to drop 2 samples, it will indeed take 2 seconds.
I'm not understanding why this is unexpected?
Jonathan
>
> Regards,
> Jian-Hong Pan
>
> >
> >
> > -----Original Message-----
> > From: linux-iio-owner@vger.kernel.org <linux-iio-owner@vger.kernel.org> On Behalf Of Jian-Hong Pan
> > Sent: Sunday, November 18, 2018 10:12 PM
> > To: Jonathan Cameron <jic23@kernel.org>; Hartmut Knaack <knaack.h@gmx.de>; Lars-Peter Clausen <lars@metafoo.de>; Peter Meerwald-Stadler <pmeerw@pmeerw.net>; Dominique Martinet <asmadeus@codewreck.org>
> > Cc: linux-iio@vger.kernel.org; linux-kernel@vger.kernel.org; linux@endlessm.com; Jian-Hong Pan <jian-hong@endlessm.com>
> > Subject: [PATCH] iio: st_sensors: Fix the sleep time for sampling
> >
> > According to the description of st_sensor_settings and st_sensor_data structures' comments:
> > - bootime: samples to discard when sensor passing from power-down to power-up.
> > - odr: Output data rate of the sensor [Hz].
> >
> > The sleep time should be
> > sdata->sensor_settings->bootime + 1000 / sdata->odr ms.
> >
> > Signed-off-by: Jian-Hong Pan <jian-hong@endlessm.com>
> > ---
> > drivers/iio/common/st_sensors/st_sensors_core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/common/st_sensors/st_sensors_core.c b/drivers/iio/common/st_sensors/st_sensors_core.c
> > index 26fbd1bd9413..6b87ea657a92 100644
> > --- a/drivers/iio/common/st_sensors/st_sensors_core.c
> > +++ b/drivers/iio/common/st_sensors/st_sensors_core.c
> > @@ -594,7 +594,7 @@ int st_sensors_read_info_raw(struct iio_dev *indio_dev,
> > if (err < 0)
> > goto out;
> >
> > - msleep((sdata->sensor_settings->bootime * 1000) / sdata->odr);
> > + msleep(sdata->sensor_settings->bootime + 1000 / sdata->odr);
> > err = st_sensors_read_axis_data(indio_dev, ch, val);
> > if (err < 0)
> > goto out;
> > --
> > 2.11.0
> >
next prev parent reply other threads:[~2018-11-25 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 6:12 [PATCH] iio: st_sensors: Fix the sleep time for sampling Jian-Hong Pan
2018-11-19 19:04 ` Denis CIOCCA
2018-11-21 5:13 ` Jian-Hong Pan
2018-11-25 13:22 ` Jonathan Cameron [this message]
2018-11-27 7:23 ` Jian-Hong Pan
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=20181125132257.6ae9fe82@archlinux \
--to=jic23@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=denis.ciocca@st.com \
--cc=jian-hong@endlessm.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.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