devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li peiyu <579lpy@gmail.com>
To: jic23@kernel.org
Cc: javier.carrasco.cruz@gmail.com, lars@metafoo.de,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 1/4] iio: core: introduce trough modifier for minimum  values
Date: Wed,  6 Dec 2023 21:48:19 +0800	[thread overview]
Message-ID: <20231206134819.559496-1-579lpy@gmail.com> (raw)
In-Reply-To: <20231206134655.559474-1-579lpy@gmail.com>

From: Javier Carrasco <javier.carrasco.cruz@gmail.com>

The IIO_CHAN_INFO_PEAK modifier is used for maximum values and currently
there is no equivalent for minimum values. Instead of overloading the
existing peak modifier, a new modifier can be added.

In principle there is no need to add a _TROUGH_SCALE modifier as the
scale will be the same as the one required for the INFO_PEAK modifier,
which in turn is sometimes omitted if a single scale for peaks and raw
values is required.

Add an IIO_CHAN_INFO_TROUGH modifier for minimum values.

Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
 drivers/iio/industrialio-core.c | 1 +
 include/linux/iio/types.h       | 1 +
 2 files changed, 2 insertions(+)

diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
index c77745b594bd..351c64c2f4da 100644
--- a/drivers/iio/industrialio-core.c
+++ b/drivers/iio/industrialio-core.c
@@ -182,6 +182,7 @@ static const char * const iio_chan_info_postfix[] = {
 	[IIO_CHAN_INFO_THERMOCOUPLE_TYPE] = "thermocouple_type",
 	[IIO_CHAN_INFO_CALIBAMBIENT] = "calibambient",
 	[IIO_CHAN_INFO_ZEROPOINT] = "zeropoint",
+	[IIO_CHAN_INFO_TROUGH] = "trough_raw",
 };
 /**
  * iio_device_id() - query the unique ID for the device
diff --git a/include/linux/iio/types.h b/include/linux/iio/types.h
index 117bde7d6ad7..d89982c98368 100644
--- a/include/linux/iio/types.h
+++ b/include/linux/iio/types.h
@@ -68,6 +68,7 @@ enum iio_chan_info_enum {
 	IIO_CHAN_INFO_THERMOCOUPLE_TYPE,
 	IIO_CHAN_INFO_CALIBAMBIENT,
 	IIO_CHAN_INFO_ZEROPOINT,
+	IIO_CHAN_INFO_TROUGH,
 };
 
 #endif /* _IIO_TYPES_H_ */
-- 
2.34.1


  reply	other threads:[~2023-12-06 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 13:46 [PATCH v4 0/4] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2023-12-06 13:48 ` Li peiyu [this message]
2023-12-06 17:52   ` [PATCH v4 1/4] iio: core: introduce trough modifier for minimum values Jonathan Cameron
2023-12-06 13:49 ` [PATCH v4 2/4] iio: ABI: document temperature and humidity peak/trough raw attributes Li peiyu
2023-12-06 13:51 ` [PATCH v4 3/4] iio: humidity: Add driver for ti HDC302x humidity sensors Li peiyu
2023-12-06 18:00   ` Jonathan Cameron
2023-12-06 13:51 ` [PATCH v4 4/4] iio: humidity: Add TI HDC302x support Li peiyu
2023-12-06 14:53   ` Conor Dooley
2023-12-06 18:42   ` Krzysztof Kozlowski
2023-12-11 10:37     ` peiyu li
2023-12-11 10:46       ` Krzysztof Kozlowski

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=20231206134819.559496-1-579lpy@gmail.com \
    --to=579lpy@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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).