From: andy.shevchenko@gmail.com
To: Astrid Rost <astrid.rost@axis.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@axis.com,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Mathieu Othacehe" <m.othacehe@gmail.com>
Subject: Re: [PATCH v5 5/7] iio: light: vcnl4000: Add period for vcnl4040/4200
Date: Sat, 3 Jun 2023 16:51:03 +0300 [thread overview]
Message-ID: <ZHtFR6_jdi10bFdH@surfacebook> (raw)
In-Reply-To: <20230530142405.1679146-6-astrid.rost@axis.com>
Tue, May 30, 2023 at 04:24:03PM +0200, Astrid Rost kirjoitti:
> Add read/write attribute for proximity and illuminance period. The
> period is set in the interrupt persistence flags(PS_PERS and ALS_PERS).
> An interrupt will not be asserted if the raw value is not over (or lower)
> than the threshold for the set continued amount of measurements.
> The time in seconds is calculated by the number of continued refreshes
> multiplied with the integration time.
> It will always pick the next lower possible value. The period changes,
> if the integration time is changed.
...
> +static ssize_t vcnl4040_read_als_period(struct vcnl4000_data *data, int *val, int *val2)
> +{
> + int ret, ret_pers, ret_it;
> + int64_t val_c;
> +
> + ret = i2c_smbus_read_word_data(data->client, VCNL4200_AL_CONF);
> + if (ret < 0)
> + return ret;
> + ret_pers = FIELD_GET(VCNL4040_ALS_CONF_PERS, ret);
> +
Redundant blank line.
> + if (ret_pers >= ARRAY_SIZE(vcnl4040_als_persistence))
> + return -EINVAL;
> +
> + ret_it = FIELD_GET(VCNL4040_ALS_CONF_IT, ret);
> +
Ditto.
> + if (ret_it >= data->chip_spec->num_als_it_times)
> + return -EINVAL;
Also name them better, at least by dropping ret prefix.
> + val_c = mul_u32_u32((*data->chip_spec->als_it_times)[ret_it][1],
> + vcnl4040_als_persistence[ret_pers]);
> + *val = div_u64_rem(val_c, MICRO, val2);
> +
> + return IIO_VAL_INT_PLUS_MICRO;
> +}
...
> +static ssize_t vcnl4040_write_als_period(struct vcnl4000_data *data, int val, int val2)
> +{
> + unsigned int index;
> + int ret, ret_it;
Name variable better.
> + u16 regval;
> + int64_t val_n = mul_u32_u32(val, MICRO) + val2;
It is inconsistent to use uXX and intXX_t in the same module. Can you explain
the intention?
> +
> + ret = i2c_smbus_read_word_data(data->client, VCNL4200_AL_CONF);
> + if (ret < 0)
> + return ret;
> +
> + ret_it = FIELD_GET(VCNL4040_ALS_CONF_IT, ret);
> +
Redundant blank line.
> + if (ret_it >= data->chip_spec->num_als_it_times)
> + return -EINVAL;
> +
> + for (index = 0; index < ARRAY_SIZE(vcnl4040_als_persistence) - 1; index++)
In one case you use i, here index. Please, be consistent with your code.
> + if (val_n < mul_u32_u32(vcnl4040_als_persistence[index],
> + (*data->chip_spec->als_it_times)[ret_it][1]))
> + break;
It would be better to have
for (...) {
...
}
> + mutex_lock(&data->vcnl4000_lock);
> +
> + ret = i2c_smbus_read_word_data(data->client, VCNL4200_AL_CONF);
> + if (ret < 0)
> + goto out_unlock;
> +
> + regval = (ret & ~VCNL4040_ALS_CONF_PERS) |
> + FIELD_PREP(VCNL4040_ALS_CONF_PERS, index);
> + ret = i2c_smbus_write_word_data(data->client, VCNL4200_AL_CONF,
> + regval);
> +
> +out_unlock:
> + mutex_unlock(&data->vcnl4000_lock);
> + return ret;
> +}
...
All the same to the other functions applies.
I stopped here.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-03 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 14:23 [PATCH v5 0/7] iio: light: vcnl4000: Add features for vncl4040/4200 Astrid Rost
2023-05-30 14:23 ` [PATCH v5 1/7] iio: light: vcnl4000: Add proximity irq for vcnl4200 Astrid Rost
2023-06-03 12:08 ` andy.shevchenko
2023-05-30 14:24 ` [PATCH v5 2/7] iio: light: vcnl4000: Add proximity ps_it " Astrid Rost
2023-06-03 12:09 ` andy.shevchenko
2023-05-30 14:24 ` [PATCH v5 3/7] iio: light: vcnl4000: Add als_it for vcnl4040/4200 Astrid Rost
2023-06-03 12:15 ` andy.shevchenko
2023-05-30 14:24 ` [PATCH v5 4/7] iio: light: vcnl4000: add illuminance irq vcnl4040/4200 Astrid Rost
2023-06-03 13:46 ` andy.shevchenko
2023-06-04 11:16 ` Jonathan Cameron
2023-05-30 14:24 ` [PATCH v5 5/7] iio: light: vcnl4000: Add period for vcnl4040/4200 Astrid Rost
2023-06-03 13:51 ` andy.shevchenko [this message]
2023-05-30 14:24 ` [PATCH v5 6/7] iio: light: vcnl4000: Add oversampling_ratio for 4040/4200 Astrid Rost
2023-06-03 13:51 ` andy.shevchenko
2023-05-30 14:24 ` [PATCH v5 7/7] iio: light: vcnl4000: Add calibration bias " Astrid Rost
2023-06-03 13:52 ` andy.shevchenko
2023-06-03 13:54 ` [PATCH v5 0/7] iio: light: vcnl4000: Add features for vncl4040/4200 andy.shevchenko
2023-06-04 11:20 ` 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=ZHtFR6_jdi10bFdH@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=astrid.rost@axis.com \
--cc=jic23@kernel.org \
--cc=kernel@axis.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.