From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
linux-iio@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Subject: [PATCH v2 4/6] iio: cros_ec_sensors: Convert to use PI definition
Date: Fri, 7 Nov 2025 21:03:02 +0100 [thread overview]
Message-ID: <20251107201005.3156118-5-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20251107201005.3156118-1-andriy.shevchenko@linux.intel.com>
Convert to use PI definition instead of open coded value of it.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
index 82cef4a12442..e248ba1eb3f9 100644
--- a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
+++ b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
@@ -21,6 +21,7 @@
#include <linux/platform_data/cros_ec_commands.h>
#include <linux/platform_data/cros_ec_proto.h>
#include <linux/platform_device.h>
+#include <linux/units.h>
#include <linux/slab.h>
#define CROS_EC_SENSORS_MAX_CHANNELS 4
@@ -120,7 +121,7 @@ static int cros_ec_sensors_read(struct iio_dev *indio_dev,
* loss. Round to the nearest integer.
*/
*val = 0;
- *val2 = div_s64(val64 * 3141592653ULL,
+ *val2 = div_s64(val64 * DIV_ROUND_UP_ULL(PI_LL, GIGA),
180 << (CROS_EC_SENSOR_BITS - 1));
ret = IIO_VAL_INT_PLUS_NANO;
break;
--
2.50.1
next prev parent reply other threads:[~2025-11-07 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 20:02 [PATCH v2 0/6] iio: Introduce and use value of π Andy Shevchenko
2025-11-07 20:02 ` [PATCH v2 1/6] media: vidtv: Rename PI definition to PI_SAMPLES Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 2/6] units: Add 32- and 64-bit signed values of π Andy Shevchenko
2025-11-07 21:09 ` David Lechner
2025-11-07 21:14 ` David Lechner
[not found] ` <CAHp75VexvdYyjt1GkbfqOotkFpLeb=io6outJ5dpRqBv2qPNng@mail.gmail.com>
2025-11-09 17:00 ` Jonathan Cameron
2025-11-09 17:09 ` Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 3/6] media: dvb-frontends: atbm8830: Convert to use PI definition Andy Shevchenko
2025-11-07 20:03 ` Andy Shevchenko [this message]
2025-11-07 20:03 ` [PATCH v2 5/6] iio: frequency: ad9523: " Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 6/6] iio: position: iqs624-pos: " Andy Shevchenko
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=20251107201005.3156118-5-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dlechner@baylibre.com \
--cc=dwlsalmeida@gmail.com \
--cc=groeck@chromium.org \
--cc=hverkuil+cisco@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nuno.sa@analog.com \
/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).