From: Jonathan Cameron <jic23@kernel.org>
To: Abhash Jha <abhashkumarjha123@gmail.com>
Cc: linux-iio@vger.kernel.org, anshulusr@gmail.com, lars@metafoo.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] iio: light: ltr390: Calculate 'counts_per_uvi' dynamically
Date: Sat, 3 Aug 2024 15:13:27 +0100 [thread overview]
Message-ID: <20240803151327.6212d29b@jic23-huawei> (raw)
In-Reply-To: <20240731063706.25412-4-abhashkumarjha123@gmail.com>
On Wed, 31 Jul 2024 12:07:05 +0530
Abhash Jha <abhashkumarjha123@gmail.com> wrote:
> counts_per_uvi depends on the current value of gain and resolution.
> Hence, we cannot use the hardcoded value 96.
> The `counts_per_uvi` function gives the count based on the current gain
> and resolution (integration time).
>
> Signed-off-by: Abhash Jha <abhashkumarjha123@gmail.com>
A few additional minor comments inline as you are doing a v6 anyway.
Thanks,
Jonathan
> ---
> drivers/iio/light/ltr390.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/light/ltr390.c b/drivers/iio/light/ltr390.c
> index d3ce43f20..84c084bec 100644
> --- a/drivers/iio/light/ltr390.c
> +++ b/drivers/iio/light/ltr390.c
> @@ -46,6 +46,8 @@
> #define LTR390_UVS_MODE BIT(3)
> #define LTR390_SENSOR_ENABLE BIT(1)
>
> +#define LTR390_FRACTIONAL_PRECISION 100
> +
> /*
> * At 20-bit resolution (integration time: 400ms) and 18x gain, 2300 counts of
> * the sensor are equal to 1 UV Index [Datasheet Page#8].
> @@ -120,6 +122,16 @@ static int ltr390_set_mode(struct ltr390_data *data, enum ltr390_mode mode)
> return 0;
> }
>
> +static int ltr390_counts_per_uvi(struct ltr390_data *data)
> +{
> + int orig_gain = 18;
> + int orig_int_time = 400;
add const to these two.
> + int divisor = orig_gain * orig_int_time;
I'd use this orig_gain * orig_int_time inline.
> + int gain = data->gain;
Use this data->gain inline.
> +
> + return DIV_ROUND_CLOSEST(23 * gain * data->int_time_us, 10 * divisor);
> +}
> +
> static int ltr390_read_raw(struct iio_dev *iio_device,
> struct iio_chan_spec const *chan, int *val,
> int *val2, long mask)
> @@ -160,8 +172,8 @@ static int ltr390_read_raw(struct iio_dev *iio_device,
> if (ret < 0)
> return ret;
>
> - *val = LTR390_WINDOW_FACTOR;
> - *val2 = LTR390_COUNTS_PER_UVI;
> + *val = LTR390_WINDOW_FACTOR * LTR390_FRACTIONAL_PRECISION;
> + *val2 = ltr390_counts_per_uvi(data);
> return IIO_VAL_FRACTIONAL;
>
> case IIO_LIGHT:
next prev parent reply other threads:[~2024-08-03 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 6:37 [PATCH v5 0/3] Replaced IIO_INTENSITY channel with IIO_LIGHT Abhash Jha
2024-07-31 6:37 ` [PATCH v5 1/3] iio: light: ltr390: Add configurable gain and resolution Abhash Jha
2024-08-03 14:06 ` Jonathan Cameron
2024-07-31 6:37 ` [PATCH v5 2/3] iio: light: ltr390: Add ALS channel and support for " Abhash Jha
2024-08-03 14:10 ` Jonathan Cameron
2024-08-06 17:20 ` Abhash jha
2024-07-31 6:37 ` [PATCH v5 3/3] iio: light: ltr390: Calculate 'counts_per_uvi' dynamically Abhash Jha
2024-08-03 14:13 ` Jonathan Cameron [this message]
2024-08-03 13:59 ` [PATCH v5 0/3] Replaced IIO_INTENSITY channel with IIO_LIGHT Jonathan Cameron
2024-08-03 16:58 ` Abhash jha
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=20240803151327.6212d29b@jic23-huawei \
--to=jic23@kernel.org \
--cc=abhashkumarjha123@gmail.com \
--cc=anshulusr@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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