From: Liam Beguin <liambeguin@gmail.com>
To: liambeguin@gmail.com, peda@axentia.se, jic23@kernel.org,
lars@metafoo.de, pmeerw@pmeerw.net
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org
Subject: [PATCH v5 05/10] iio: afe: rescale: add INT_PLUS_{MICRO,NANO} support
Date: Wed, 14 Jul 2021 23:12:10 -0400 [thread overview]
Message-ID: <20210715031215.1534938-6-liambeguin@gmail.com> (raw)
In-Reply-To: <20210715031215.1534938-1-liambeguin@gmail.com>
From: Liam Beguin <lvb@xiphos.com>
Some ADCs use IIO_VAL_INT_PLUS_{NANO,MICRO} scale types.
Add support for these to allow using the iio-rescaler with them.
Signed-off-by: Liam Beguin <lvb@xiphos.com>
---
drivers/iio/afe/iio-rescale.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/drivers/iio/afe/iio-rescale.c b/drivers/iio/afe/iio-rescale.c
index 4c3cfd4d5181..a2b220b5ba86 100644
--- a/drivers/iio/afe/iio-rescale.c
+++ b/drivers/iio/afe/iio-rescale.c
@@ -92,7 +92,22 @@ static int rescale_read_raw(struct iio_dev *indio_dev,
do_div(tmp, 1000000000LL);
*val = tmp;
return ret;
+ case IIO_VAL_INT_PLUS_NANO:
+ tmp = ((s64)*val * 1000000000LL + *val2) * rescale->numerator;
+ do_div(tmp, rescale->denominator);
+
+ *val = div_s64(tmp, 1000000000LL);
+ *val2 = tmp - *val * 1000000000LL;
+ return ret;
+ case IIO_VAL_INT_PLUS_MICRO:
+ tmp = ((s64)*val * 1000000LL + *val2) * rescale->numerator;
+ do_div(tmp, rescale->denominator);
+
+ *val = div_s64(tmp, 1000000LL);
+ *val2 = tmp - *val * 1000000LL;
+ return ret;
default:
+ dev_err(&indio_dev->dev, "unsupported type %d\n", ret);
return -EOPNOTSUPP;
}
default:
--
2.30.1.489.g328c10930387
next prev parent reply other threads:[~2021-07-15 3:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 3:12 [PATCH v5 00/10] iio: afe: add temperature rescaling support Liam Beguin
2021-07-15 3:12 ` [PATCH v5 01/10] iio: inkern: apply consumer scale on IIO_VAL_INT cases Liam Beguin
2021-07-15 3:12 ` [PATCH v5 02/10] iio: inkern: apply consumer scale when no channel scale is available Liam Beguin
2021-07-15 3:12 ` [PATCH v5 03/10] iio: inkern: make a best effort on offset calculation Liam Beguin
2021-07-15 3:12 ` [PATCH v5 04/10] iio: afe: rescale: reduce risk of integer overflow Liam Beguin
2021-07-15 10:23 ` Peter Rosin
2021-07-16 16:46 ` Liam Beguin
2021-07-15 3:12 ` Liam Beguin [this message]
2021-07-15 9:48 ` [PATCH v5 05/10] iio: afe: rescale: add INT_PLUS_{MICRO,NANO} support Peter Rosin
2021-07-16 19:18 ` Liam Beguin
2021-07-17 8:11 ` Peter Rosin
2021-07-17 16:55 ` Jonathan Cameron
2021-07-18 23:44 ` Liam Beguin
2021-07-19 8:31 ` Peter Rosin
2021-07-19 15:15 ` Liam Beguin
2021-07-15 3:12 ` [PATCH v5 06/10] iio: afe: rescale: add offset support Liam Beguin
2021-07-15 3:12 ` [PATCH v5 07/10] iio: afe: rescale: add RTD temperature sensor support Liam Beguin
2021-07-15 3:12 ` [PATCH v5 08/10] iio: afe: rescale: add temperature transducers Liam Beguin
2021-07-15 3:12 ` [PATCH v5 09/10] dt-bindings: iio: afe: add bindings for temperature-sense-rtd Liam Beguin
2021-07-15 3:12 ` [PATCH v5 10/10] dt-bindings: iio: afe: add bindings for temperature transducers Liam Beguin
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=20210715031215.1534938-6-liambeguin@gmail.com \
--to=liambeguin@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=pmeerw@pmeerw.net \
--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).