From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>, lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v1 1/4] iio: chemical: Add IIO_CONCENTRATION channel type
Date: Sat, 5 Sep 2015 16:51:04 +0100 [thread overview]
Message-ID: <55EB0F68.8090908@kernel.org> (raw)
In-Reply-To: <1441432406-4761-2-git-send-email-mranostay@gmail.com>
On 05/09/15 06:53, Matt Ranostay wrote:
> There are air quality sensors that report data back in parts per million
> of VOC (Volatile Organic Compounds) which are usually indexed from CO2
> or another common pollutant.
>
> This patchset adds an IIO_CONCENTRATION type and IIO_MOD_PPM/PPB modifiers
> because no other channels types fit this use case.
Fine with concentration, not with the modifiers. See below.
>
> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
> ---
> Documentation/ABI/testing/sysfs-bus-iio | 10 ++++++++++
> drivers/iio/industrialio-core.c | 3 +++
> include/uapi/linux/iio/types.h | 3 +++
> 3 files changed, 16 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 42d360f..a3803a1 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -1459,3 +1459,13 @@ Description:
> measurements and return the average value as output data. Each
> value resulted from <type>[_name]_oversampling_ratio measurements
> is considered as one sample for <type>[_name]_sampling_frequency.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_raw
> +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_ppm_raw
> +What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_ppb_raw
> +KernelVersion: 4.3
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Raw (unscaled no offset etc.) concentration reading of data like
> + CO2 or VOC (Volatile Organic Compounds) substances with or without
> + ppm (Part Per Million) or ppb (Parts Per Billion) channel modifiers.
See below. ppm / ppb should not be modifiers. That's not what they are for.
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index b3fcc2c..ea9e31a 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -75,6 +75,7 @@ static const char * const iio_chan_type_name_spec[] = {
> [IIO_ENERGY] = "energy",
> [IIO_DISTANCE] = "distance",
> [IIO_VELOCITY] = "velocity",
> + [IIO_CONCENTRATION] = "concentration",
> };
>
> static const char * const iio_modifier_names[] = {
> @@ -111,6 +112,8 @@ static const char * const iio_modifier_names[] = {
> [IIO_MOD_ROOT_SUM_SQUARED_X_Y_Z] = "sqrt(x^2+y^2+z^2)",
> [IIO_MOD_I] = "i",
> [IIO_MOD_Q] = "q",
> + [IIO_MOD_PPM] = "ppm",
> + [IIO_MOD_PPB] = "ppb",
> };
>
> /* relies on pairs of these shared then separate */
> diff --git a/include/uapi/linux/iio/types.h b/include/uapi/linux/iio/types.h
> index 2f8b117..dfb8b8c 100644
> --- a/include/uapi/linux/iio/types.h
> +++ b/include/uapi/linux/iio/types.h
> @@ -35,6 +35,7 @@ enum iio_chan_type {
> IIO_ENERGY,
> IIO_DISTANCE,
> IIO_VELOCITY,
> + IIO_CONCENTRATION,
> };
>
> enum iio_modifier {
> @@ -72,6 +73,8 @@ enum iio_modifier {
> IIO_MOD_ROOT_SUM_SQUARED_X_Y_Z,
> IIO_MOD_I,
> IIO_MOD_Q,
> + IIO_MOD_PPM,
The use of modifiers is not about units. Those should be well specified
in the ABI docs for the given channel type. Hence I'd expect modifiers
for the type of chemical being detected not the unit.
PPB can be handled by PPM and a different return type
IIO_INT_PLUS_NANO etc. If there isn't an appropriate return type for
the scale needed, then we can easily add more of those ;)
> + IIO_MOD_PPB,
> };
>
> enum iio_event_type {
>
next prev parent reply other threads:[~2015-09-05 15:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 5:53 [RFC v1 0/4] iio: new chemical sensor framework and channel types Matt Ranostay
2015-09-05 5:53 ` [RFC v1 1/4] iio: chemical: Add IIO_CONCENTRATION channel type Matt Ranostay
2015-09-05 7:23 ` Peter Meerwald
2015-09-05 15:51 ` Jonathan Cameron [this message]
2015-09-05 5:53 ` [RFC v1 2/4] iio: resistance: add IIO_RESISTANCE " Matt Ranostay
2015-09-05 15:57 ` Jonathan Cameron
2015-09-05 5:53 ` [RFC v1 3/4] devicetree: add SGX Sensortech vendor id Matt Ranostay
2015-09-05 8:10 ` Daniel Baluta
2015-09-05 5:53 ` [RFC v1 4/4] iio: chemical: add SGX VZ89x VOC sensor support Matt Ranostay
2015-09-05 7:45 ` Peter Meerwald
2015-09-05 8:02 ` Matt Ranostay
2015-09-05 8:11 ` Peter Meerwald
2015-09-05 22:58 ` Matt Ranostay
2015-09-05 8:08 ` Daniel Baluta
2015-09-05 16:14 ` Jonathan Cameron
2015-09-05 22:17 ` Matt Ranostay
2015-09-05 8:20 ` [RFC v1 0/4] iio: new chemical sensor framework and channel types Daniel Baluta
2015-09-05 15:55 ` 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=55EB0F68.8090908@kernel.org \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=pmeerw@pmeerw.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).