From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Philippe De Muyter <phdm@macq.eu>, <linux-iio@vger.kernel.org>
Subject: Re: sysfs mount_matrix for st_lsm6dsx gyro
Date: Thu, 12 Jan 2023 15:19:37 +0000 [thread overview]
Message-ID: <20230112151937.0000505a@Huawei.com> (raw)
In-Reply-To: <Y7/vu7IwRmQS7CSf@lore-desk>
On Thu, 12 Jan 2023 12:32:11 +0100
Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> > Hello Lorenzo,
> >
> > On Thu, Jan 12, 2023 at 10:51:03AM +0100, Lorenzo Bianconi wrote:
> > > Date: Thu, 12 Jan 2023 10:51:03 +0100
> > > From: Lorenzo Bianconi <lorenzo@kernel.org>
> > > To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > Cc: Philippe De Muyter <phdm@macq.eu>, linux-iio@vger.kernel.org
> > > Subject: Re: sysfs mount_matrix for st_lsm6dsx gyro
> > >
> > > > On Wed, 11 Jan 2023 13:09:40 +0100
> > > > Philippe De Muyter <phdm@macq.eu> wrote:
> > > >
> > > > > Hello Lorenzo and list,
> > > > >
> > > > > I do not find a "*mount_matrix" entry in sysfs for a 'ism330dlc_gyro'
> > > > > iio device.
> > > > > Is that normal ?
> > > > > Is a fix available ?
> > > >
> > > > Looks like the channel definition for the gyro does not include an
> > > > appropriate ext_info entry unlike the accelerometer channels which
> > > > have one with mount_matrix support.
> > > >
> > > > From a quick glance looks like a simple fix. Add that entry.
> > >
> > > I am not sure if accel and gyro can be mounted with a different orientation.
> > > Do you think we should have a per-sensor mount_matrix?
> >
> > My chip is a 'ism330dlc'. It's one chip containing an accel and a gyro,
> > so the mount_matrix should be the same for the accel and the gyro.
> > Unfortunately the accel and the gyro are presented in /sysfs as two
> > separate devices, and only the accel one has a 'mount_matrix' entry.
> > So a user looking for any gyro will find the gyro entry, but without
> > 'mount_matrix'.
> >
> > I have followed Jonathan's proposal and added this simple patch in
> > the definition of the ST_LSM6DSX_CHANNEL macro :
> >
> > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > index d80ba2e688ed..9d18145d5041 100644
> > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > @@ -96,6 +96,7 @@ enum st_lsm6dsx_hw_id {
> > .storagebits = 16, \
> > .endianness = IIO_LE, \
> > }, \
> > + .ext_info = st_lsm6dsx_accel_ext_info, \
> > }
>
> I am fine with this approach, probably having a per-sensor mount_matrix is
> unnecessary. Can you please just rename st_lsm6dsx_accel_ext_info in
> st_lsm6dsx_ext_info?
>
> Regards,
> Lorenzo
>
> >
> > struct st_lsm6dsx_reg {
> >
> > Another fix would be to create only one chip entry in sysfs, but that's
> > above my knowledge of this driver.
We can't make that change. It would be ABI breakage - userspace code would
stop working.
Jonathan
> >
> > Best regards
> >
> > Philippe
>
next prev parent reply other threads:[~2023-01-12 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 12:09 sysfs mount_matrix for st_lsm6dsx gyro Philippe De Muyter
2023-01-11 17:17 ` Jonathan Cameron
2023-01-12 9:51 ` Lorenzo Bianconi
2023-01-12 11:27 ` Philippe De Muyter
2023-01-12 11:32 ` Lorenzo Bianconi
2023-01-12 15:19 ` Jonathan Cameron [this message]
2023-01-13 14:45 ` Philippe De Muyter
2023-01-12 10:12 ` Lorenzo Bianconi
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=20230112151937.0000505a@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=phdm@macq.eu \
/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.