From: Jonathan Cameron <jic23@kernel.org>
To: yarl-baudig@mailoo.org
Cc: linux-iio@vger.kernel.org, "Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Denis Ciocca" <denis.ciocca@st.com>
Subject: Re: [PATCH] iio: st_sensors: rely on odr mask to know if odr can be set
Date: Sun, 12 Apr 2020 10:49:18 +0100 [thread overview]
Message-ID: <20200412104918.36e17c3f@archlinux> (raw)
In-Reply-To: <ea-mime-5e91df36-2302-7e2b01aa@www-2.mailo.com>
On Sat, 11 Apr 2020 17:16:06 +0200 (CEST)
yarl-baudig@mailoo.org wrote:
> Indeed, relying on addr being not 0 cannot work because some device have
> their register to set odr at address 0. As a matter of fact, if the odr
> can be set, then there is a mask.
>
> Sensors with ODR register at address 0 are: lsm303dlh, lsm303dlhc, lsm303dlm
>
> Fixes: 7d245172675a ("iio: common: st_sensors: check odr address value in st_sensors_set_odr()")
> Signed-off-by: Lary Gibaud <yarl-baudig@mailoo.org>
Applied to the fixes-togreg branch of iio.git and marked for
stable.
Thanks,
Jonathan
> ---
> 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 a0c2cbd60c6f..cccd4c26dfa4 100644
> --- a/drivers/iio/common/st_sensors/st_sensors_core.c
> +++ b/drivers/iio/common/st_sensors/st_sensors_core.c
> @@ -79,7 +79,7 @@ int st_sensors_set_odr(struct iio_dev *indio_dev, unsigned int odr)
> struct st_sensor_odr_avl odr_out = {0, 0};
> struct st_sensor_data *sdata = iio_priv(indio_dev);
>
> - if (!sdata->sensor_settings->odr.addr)
> + if (!sdata->sensor_settings->odr.mask)
> return 0;
>
> err = st_sensors_match_odr(sdata->sensor_settings, odr, &odr_out);
next prev parent reply other threads:[~2020-04-12 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:16 [PATCH] iio: st_sensors: rely on odr mask to know if odr can be set yarl-baudig
2020-04-12 9:49 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 13:40 yarl-baudig
2020-04-05 11:57 ` Jonathan Cameron
2020-04-09 11:24 ` yarl-baudig
2020-04-02 13:08 yarl-baudig
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=20200412104918.36e17c3f@archlinux \
--to=jic23@kernel.org \
--cc=denis.ciocca@st.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=yarl-baudig@mailoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.