public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: "Gaëtan André" <rvlander@gaetanandre.eu>,
	linux-iio@vger.kernel.org, ~postmarketos/upstreaming@lists.sr.ht,
	"Denis Ciocca" <denis.ciocca@st.com>
Subject: Re: [PATCH v2] iio: st_sensors: make scale channels also shared by type
Date: Sat, 2 May 2020 19:07:51 +0100	[thread overview]
Message-ID: <20200502190751.53123be3@archlinux> (raw)
In-Reply-To: <faf0bf3315c93fddee4f4cdb890bc5e80701c8fd.camel@hadess.net>

On Sun, 26 Apr 2020 13:19:09 +0200
Bastien Nocera <hadess@hadess.net> wrote:

> On Sat, 2020-04-25 at 18:13 +0100, Jonathan Cameron wrote:
> > On Thu, 23 Apr 2020 14:17:15 +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.  
> > As I mentioned in v1, there isn't a strict ABI rule that says that we
> > must
> > do the shared form
> > 
> > +CC'd Bastien for comment on what userspace is assuming and whether
> > we should
> > push this back to stable or not.  
> 
> I have no idea what the effects of this would be on the ABI, and how
> this would impact iio-sensor-proxy.

There goes me being lazy ;)

> 
> Code is here though, so it might be best to test it:
> https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/tree/master/src
> 
> And we accept merge requests :)

Only looks at scale and in_accel_scale

Easy enough to fix...

Note that for some older accelerometers it has to do per channel scales btw.
It used to be hard to have the same range out of the plane of the silicon
than within it, so was common to have sensors with different ranges and hence
scales in z direction from x and y.

I'll apply the kernel patch but good to fix up iio-sensor-proxy as well.

I would ideally like Denis to give this a quick sanity check though as I'd
like to give it a stable tag and don't want any unexpected breakage.

Thanks,

Jonathan

> 


  reply	other threads:[~2020-05-02 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 12:17 [PATCH v2] iio: st_sensors: make scale channels also shared by type Gaëtan André
2020-04-25 17:13 ` Jonathan Cameron
2020-04-26 11:19   ` Bastien Nocera
2020-05-02 18:07     ` Jonathan Cameron [this message]
2020-05-04 10:02       ` Bastien Nocera
2020-05-04 10:22         ` Jonathan Cameron
2020-05-04 11:05           ` Bastien Nocera
2020-05-12 14:11           ` Bastien Nocera

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=20200502190751.53123be3@archlinux \
    --to=jic23@kernel.org \
    --cc=denis.ciocca@st.com \
    --cc=hadess@hadess.net \
    --cc=linux-iio@vger.kernel.org \
    --cc=rvlander@gaetanandre.eu \
    --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