From: Lorenzo Bianconi <lorenzo@kernel.org>
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: Wed, 11 Dec 2019 15:10:06 +0100 [thread overview]
Message-ID: <20191211141006.GA3779@localhost.localdomain> (raw)
In-Reply-To: <20191210082253.GA867@gerhold.net>
[-- Attachment #1: Type: text/plain, Size: 2717 bytes --]
> On Mon, Dec 09, 2019 at 10:48:52PM +0100, Lorenzo Bianconi 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.
> > >
> >
> > Hi Stephan,
> >
> > thx for working on this. I guess we can skip 'void' iterations defining the
> > array real size, do you agree?
> >
>
> I'm not sure I understand you correctly.
> Do you mean having something like:
>
> struct st_lsm6dsx_settings {
> u8 wai;
> /* ... */
> struct {
> enum st_lsm6dsx_hw_id hw_id;
> const char *name;
> } id[ST_LSM6DSX_MAX_ID];
> int id_num; /* Add this field */
> /* ... */
> };
>
> And then change the loop to use .id_num instead?
>
> I think it is pretty easy to forget to update "id_num"
> when adding new entries. Right now there is no need to worry about that.
Uhm..this approach is even more safe if someone forgets to set name for a given
device. So for the patch:
Acked-by: Lorenzo Bianconi <lorenzo@kernel.org>
Regards,
Lorenzo
>
> Thanks,
> Stephan
>
> > Regards,
> > Lorenzo
> >
> > > 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>
> > > ---
> > > 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)
> > > --
> > > 2.24.0
> > >
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-12-11 14:10 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 [this message]
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
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=20191211141006.GA3779@localhost.localdomain \
--to=lorenzo@kernel.org \
--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).