public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gaëtan André" <rvlander@gaetanandre.eu>
To: Jonathan Cameron <jic23@kernel.org>
Cc: <linux-iio@vger.kernel.org>, <~postmarketos/upstreaming@lists.sr.ht>
Subject: Re: [PATCH] iio: st_sensors: make scale channels also shared by type
Date: Sun, 5 Apr 2020 13:51:39 +0200	[thread overview]
Message-ID: <20200405115139.GA189531@ADVI0116> (raw)
In-Reply-To: <20200405110217.0f6a38d0@archlinux>

On Sun, Apr 05, 2020 at 11:02:17AM +0100, Jonathan Cameron wrote:
> On Mon, 30 Mar 2020 16:59:20 +0200
> Gaëtan André <rvlander@gaetanandre.eu> wrote:
> 
> > Scale channels are available by axis. For example for accelerometers,
> > in_accel_x_scale, in_accel_y_scale and in_accel_z_scale are available.
> > 
> > However, they should be shared by type as documented in
> > Documentation/ABI/testing/sysfs-bus-iio.
> > 
> > For each sensor (acceleros, gyros and magnetos) only one value is specified
> > for all the axes.
> > 
> > Existing, by axis, entries are preserved in order to to leave the old ABI
> > untouched.
> Hi Gaëtan,
> 
> Thanks for this.  Whilst I agree the ideal ABI would be to have just the
> shared version userspace should cope with the current version anyway as
> it would be the right option if for example the scale of x and y are controlled
> by one register field and z by another (this used to be common for accelerometers)
> 
> Any userspace software using this will have to assign a precedence to the
> two files that result and the most likely option is more specific first meaning
> the shared version is unused.
> 
> Hence I'd argue we aren't broke (just non ideal) and adding the additional
> interface just confuses matters.  Hence I would rather leave things how they
> currently are.  Do we have some userspace that is broken by this being less
> than ideal?
> 
Hi Jonathan,

Thanks for taking time to answer.

I don't have any point of view regarding what is better.

What I know is that iio-sensor-proxy [1] only looks for a common scale.
Hence, it won't work with ST sensors as is.

I could either do this patch or patch iio-sensor-proxy. What decided me
is that all ST sensors, if I am correct, use only one scale value for all axis.

If things are to be kept as is, then iio-sensor-proxy should be patched.

Also, note that currently in_acceleration_scale_{x, y, z} don't seem to
be documented.

Thanks,

Gaëtan

[1] iio-sensor-proxy: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/

> Thanks
> 
> Jonathan
> 
> > 
> > Signed-off-by: Gaëtan André <rvlander@gaetanandre.eu>
> > ---
> >  include/linux/iio/common/st_sensors.h | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/include/linux/iio/common/st_sensors.h b/include/linux/iio/common/st_sensors.h
> > index 33e939977444..f31e309f0fd1 100644
> > --- a/include/linux/iio/common/st_sensors.h
> > +++ b/include/linux/iio/common/st_sensors.h
> > @@ -52,6 +52,7 @@
> >  	.type = device_type, \
> >  	.modified = mod, \
> >  	.info_mask_separate = mask, \
> > +	.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), \
> >  	.info_mask_shared_by_all = BIT(IIO_CHAN_INFO_SAMP_FREQ), \
> >  	.scan_index = index, \
> >  	.channel2 = ch2, \
> > 
> > base-commit: b723e9431b77976b83efb90178dfcada3405321c
> 

  reply	other threads:[~2020-04-05 11:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 14:59 [PATCH] iio: st_sensors: make scale channels also shared by type Gaëtan André
2020-04-05 10:02 ` Jonathan Cameron
2020-04-05 11:51   ` Gaëtan André [this message]
2020-04-05 12:24     ` 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=20200405115139.GA189531@ADVI0116 \
    --to=rvlander@gaetanandre.eu \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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