From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
<linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID
Date: Tue, 14 Jan 2020 09:12:27 +0000 [thread overview]
Message-ID: <20200114091227.00002880@Huawei.com> (raw)
In-Reply-To: <20200114090652.GA932@gerhold.net>
On Tue, 14 Jan 2020 10:06:52 +0100
Stephan Gerhold <stephan@gerhold.net> wrote:
> On Mon, Jan 13, 2020 at 10:12:11PM +0000, Jonathan Cameron wrote:
> > On Sun, 15 Dec 2019 17:23:42 +0000
> > Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > > On Mon, 9 Dec 2019 18:05:41 +0100
> > > Stephan Gerhold <stephan@gerhold.net> wrote:
> > >
> > > > At the moment, attempting to probe a device with ST_LSM6DS3_ID
> > > > (e.g. using the st,lsm6ds3 compatible) fails with:
> > > >
> > > > st_lsm6dsx_i2c 1-006b: unsupported whoami [69]
> > > >
> > > > ... even though 0x69 is the whoami listed for ST_LSM6DS3_ID.
> > > >
> > > > This happens because st_lsm6dsx_check_whoami() also attempts
> > > > to match unspecified (zero-initialized) entries in the "id" array.
> > > > ST_LSM6DS3_ID = 0 will therefore match any entry in
> > > > st_lsm6dsx_sensor_settings (here: the first), because none of them
> > > > actually have all 12 entries listed in the "id" array.
> > > >
> > > > Avoid this by additionally checking if "name" is set,
> > > > which is only set for valid entries in the "id" array.
> > > >
> > > > Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> > > Definitely sounds like this wants backporting.
> > >
> > > If you can figure out a fixes tag that would be great!
> > I've taken a stab at working out when this got introduced and
> > came up with:
> >
> > 81956a93b522 "iio: imu: st_lsm6dsx: get device name from st_lsm6dsx_sensor_settings"
> >
> > If that's wrong please let me know asap.
> >
> > Applied to the togreg branch of iio.git as we are near the merge
> > window opening and marked for stable.
>
> You have already applied the v2 I sent with the fixes/cc stable tags :)
> It's part of your "Second set of IIO fixes for the 5.5 cycle." pull request:
> https://lore.kernel.org/linux-iio/20200105110051.445c9a95@archlinux/
Gah! I clearly wasn't on top form last night. Will drop this one again.
Thanks.
Jonathan
>
> >
> > Thanks,
> >
> > Jonathan
> > >
> > > Thanks,
> > >
> > > Jonathan
> > >
> > > > ---
> > > > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > > > index a7d40c02ce6b..b921dd9e108f 100644
> > > > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > > > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c
> > > > @@ -1301,7 +1301,8 @@ static int st_lsm6dsx_check_whoami(struct st_lsm6dsx_hw *hw, int id,
> > > >
> > > > for (i = 0; i < ARRAY_SIZE(st_lsm6dsx_sensor_settings); i++) {
> > > > for (j = 0; j < ST_LSM6DSX_MAX_ID; j++) {
> > > > - if (id == st_lsm6dsx_sensor_settings[i].id[j].hw_id)
> > > > + if (st_lsm6dsx_sensor_settings[i].id[j].name &&
> > > > + id == st_lsm6dsx_sensor_settings[i].id[j].hw_id)
> > > > break;
> > > > }
> > > > if (j < ST_LSM6DSX_MAX_ID)
> > >
> >
>
prev parent reply other threads:[~2020-01-14 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 17:05 [PATCH] iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID Stephan Gerhold
2019-12-09 21:48 ` Lorenzo Bianconi
2019-12-10 8:22 ` Stephan Gerhold
2019-12-11 14:10 ` Lorenzo Bianconi
2019-12-15 17:23 ` Jonathan Cameron
2020-01-13 22:12 ` Jonathan Cameron
2020-01-14 9:06 ` Stephan Gerhold
2020-01-14 9:12 ` 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=20200114091227.00002880@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=stephan@gerhold.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).