linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario TESI <mario.tesi@st.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>,
	"jic23@kernel.org" <jic23@kernel.org>
Cc: "lorenzo.bianconi@redhat.com" <lorenzo.bianconi@redhat.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 0/2] support rational ODRs in st_lsm6dsx
Date: Thu, 31 Oct 2019 14:43:39 +0000	[thread overview]
Message-ID: <6d746aaa-ad45-1a29-6f9d-ddc9ffa8f760@st.com> (raw)
In-Reply-To: <cover.1572203759.git.lorenzo@kernel.org>

Tested-by: Mario Tesi <mario.tesi@st.com>


On 10/27/19 8:21 PM, Lorenzo Bianconi wrote:
> Express ODRs in HZ / 10 in order to support rational ODRs (e.g. 12.5Hz).
> This series will fix an Android CTS failure.
> Explicitly define odr table size.
> This series is based on 'iio: imu: st_lsm6dsx: fix ODR check in
> st_lsm6dsx_write_raw'
> https://patchwork.kernel.org/patch/11214281/
>
> Lorenzo Bianconi (2):
>    iio: imu: st_lsm6dsx: explicitly define odr table size
>    iio: imu: st_lsm6dsx: express odr in HZ / 10
>
>   drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h      |   4 +-
>   drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 206 ++++++++++---------
>   drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c |  33 +--
>   3 files changed, 133 insertions(+), 110 deletions(-)
>

      parent reply	other threads:[~2019-10-31 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-27 19:21 [PATCH 0/2] support rational ODRs in st_lsm6dsx Lorenzo Bianconi
2019-10-27 19:21 ` [PATCH 1/2] iio: imu: st_lsm6dsx: explicitly define odr table size Lorenzo Bianconi
2019-10-27 19:21 ` [PATCH 2/2] iio: imu: st_lsm6dsx: express odr in HZ / 10 Lorenzo Bianconi
2019-11-03 10:13   ` Jonathan Cameron
2019-11-03 13:06     ` Lorenzo Bianconi
2019-10-31 14:43 ` Mario TESI [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=6d746aaa-ad45-1a29-6f9d-ddc9ffa8f760@st.com \
    --to=mario.tesi@st.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@kernel.org \
    /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).