From: andy.shevchenko@gmail.com
To: inv.git-commit@tdk.com
Cc: jic23@kernel.org, linux-iio@vger.kernel.org, lars@metafoo.de,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH 3/4] iio: make invensense timestamp module generic
Date: Sat, 3 Jun 2023 14:19:54 +0300 [thread overview]
Message-ID: <ZHsh2npPOzPyFuAC@surfacebook> (raw)
In-Reply-To: <20230531142513.48507-4-inv.git-commit@tdk.com>
Wed, May 31, 2023 at 02:25:12PM +0000, inv.git-commit@tdk.com kirjoitti:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> Rename common module to inv_sensors_timestamp, add configuration
> at init (chip internal clock, acceptable jitter, ...) and update
> inv_icm42600 driver integration.
...
> /* check that period is acceptable */
> - period_min = INV_ICM42600_TIMESTAMP_MIN_PERIOD(chip_period) * mult;
> - period_max = INV_ICM42600_TIMESTAMP_MAX_PERIOD(chip_period) * mult;
> + period_min = ts->min_period * mult;
> + period_max = ts->max_period * mult;
Side note: wondering if linear_range.h APIs can somehow help with this.
> if (period > period_min && period < period_max)
> return true;
> else
> return false;
Another side note: this can be simplified in a follow up at some point.
...
> - /* if interrupt interval is valid, sync with interrupt timestamp */
> + /* if interrupt interval is valid, align with interrupt timestamp */
Not sure why this change, but probably it's inline with the rest of the
changes.
...
> --- /dev/null
> +++ b/include/linux/iio/common/inv_sensors_timestamp.h
Have you used -M -C for `git-format-patch`?
...
> +#ifndef INV_SENSORS_TIMESTAMP_H_
> +#define INV_SENSORS_TIMESTAMP_H_
> +#include <linux/kernel.h>
While I see this in the original code, I have found no evidence this header
is used here in any possible way.
Actually kernel.h in the _headers_ is quite discouraged.
> +#endif
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-03 11:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 14:25 [PATCH 0/4] Factorize timestamp module inv.git-commit
2023-05-31 14:25 ` [PATCH 1/4] iio: imu: inv_icm42600: make timestamp module chip independant inv.git-commit
2023-06-03 11:10 ` andy.shevchenko
2023-05-31 14:25 ` [PATCH 2/4] iio: move inv_icm42600 timestamp module in common inv.git-commit
2023-06-03 11:13 ` andy.shevchenko
2023-06-04 10:58 ` Jonathan Cameron
2023-06-05 19:07 ` Jean-Baptiste Maneyrol
2023-06-05 19:25 ` Jonathan Cameron
2023-05-31 14:25 ` [PATCH 3/4] iio: make invensense timestamp module generic inv.git-commit
2023-06-03 11:19 ` andy.shevchenko [this message]
2023-06-04 11:06 ` Jonathan Cameron
2023-05-31 14:25 ` [PATCH 4/4] iio: imu: inv_mpu6050: use the common inv_sensors timestamp module inv.git-commit
2023-06-03 11:23 ` andy.shevchenko
2023-06-04 11:08 ` Jonathan Cameron
2023-06-05 19:09 ` Jean-Baptiste Maneyrol
2023-06-05 19:25 ` Jonathan Cameron
2023-06-03 11:24 ` [PATCH 0/4] Factorize " 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=ZHsh2npPOzPyFuAC@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=inv.git-commit@tdk.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@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