From: Jonathan Cameron <jic23@kernel.org>
To: "Gaëtan André" <rvlander@gaetanandre.eu>
Cc: <linux-iio@vger.kernel.org>,
<~postmarketos/upstreaming@lists.sr.ht>,
Bastien Nocera <hadess@hadess.net>
Subject: Re: [PATCH v2] iio: st_sensors: make scale channels also shared by type
Date: Sat, 25 Apr 2020 18:13:59 +0100 [thread overview]
Message-ID: <20200425181359.1e30e315@archlinux> (raw)
In-Reply-To: <20200423121714.607262-1-rvlander@gaetanandre.eu>
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.
Thanks,
Jonathan
>
> Signed-off-by: Gaëtan André <rvlander@gaetanandre.eu>
> ---
> v1->v2: add comment explaining why we are doing both.
>
> include/linux/iio/common/st_sensors.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/linux/iio/common/st_sensors.h b/include/linux/iio/common/st_sensors.h
> index 33e939977444..42663fbab085 100644
> --- a/include/linux/iio/common/st_sensors.h
> +++ b/include/linux/iio/common/st_sensors.h
> @@ -46,12 +46,19 @@
> #define ST_SENSORS_MAX_NAME 17
> #define ST_SENSORS_MAX_4WAI 8
>
> +/*
> + * Scale channels are configured both by type and by axis.
> + * - By axis to keep the previous ABI and flexibility.
> + * - By type because it is how some userland
> + * applications are expecting them (ex: iio-sensor-proxy).
> + */
> #define ST_SENSORS_LSM_CHANNELS(device_type, mask, index, mod, \
> ch2, s, endian, rbits, sbits, addr) \
> { \
> .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: 2de8c02349f02d014e51b43f306d28fc7a23ea6e
next prev parent reply other threads:[~2020-04-25 17:14 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 [this message]
2020-04-26 11:19 ` Bastien Nocera
2020-05-02 18:07 ` Jonathan Cameron
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=20200425181359.1e30e315@archlinux \
--to=jic23@kernel.org \
--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