From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: linux-iio@vger.kernel.org, andy@kernel.org, nuno.sa@analog.com,
dlechner@baylibre.com, jic23@kernel.org,
jean-baptiste.maneyrol@tdk.com,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
heiko@sntech.de, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH V11 3/9] iio: imu: inv_icm42607: Add inv_icm42607 Core Driver
Date: Thu, 11 Jun 2026 10:35:49 +0300 [thread overview]
Message-ID: <aiplVZRI-0TCDnjL@ashevche-desk.local> (raw)
In-Reply-To: <20260610175455.19006-4-macroalpha82@gmail.com>
On Wed, Jun 10, 2026 at 12:54:47PM -0500, Chris Morgan wrote:
> Add the core component of a new inv_icm42607 driver. This includes
> a few setup functions and the full register definition in the
> header file.
...
> 2 files changed, 531 insertions(+)
> create mode 100644 drivers/iio/imu/inv_icm42607/inv_icm42607.h
> create mode 100644 drivers/iio/imu/inv_icm42607/inv_icm42607_core.c
I'm not sure this is correct split by files. These files are not:
- being build
- being mentioned in MAINTAINERS
...
> +#ifndef INV_ICM42607_H_
> +#define INV_ICM42607_H_
> +
> +#include <linux/bits.h>
> +#include <linux/iio/iio.h>
> +#include <linux/mutex.h>
mutex_types.h ?
> +#include <linux/regmap.h>
> +#include <linux/types.h>
Do you need forward declaration for regulator data type?
...
> +#define INV_ICM42607_POWER_UP_TIME_US 100000
100 * USEC_PER_MSEC (will require time.h)?
...
> +++ b/drivers/iio/imu/inv_icm42607/inv_icm42607_core.c
+ bitfields.h
> +#include <linux/delay.h>
> +#include <linux/dev_printk.h>
+ device/devres.h
+ err.h
> +#include <linux/iio/iio.h>
> +#include <linux/module.h>
> +#include <linux/mutex.h>
> +#include <linux/regmap.h>
> +#include <linux/regulator/consumer.h>
> +#include <linux/time.h>
Also check if you need types.h.
...
> + fsleep(INV_ICM42607_RESET_TIME_MS * USEC_PER_MSEC);
> +
> + /*
> + * No polling interval specified in datasheet, so use reset time as
> + * polling interval and 10x reset time as timeout period.
> + */
> + ret = regmap_read_poll_timeout(st->map, INV_ICM42607_REG_INT_STATUS,
> + val, val & INV_ICM42607_INT_STATUS_RESET_DONE,
> + (INV_ICM42607_RESET_TIME_MS * USEC_PER_MSEC),
> + (INV_ICM42607_RESET_TIME_MS * USEC_PER_MSEC * 10));
Besides too many parentheses, this can be switched to regular patter of "num * what".
Also, TBH, the plain values would be better here
fsleep(1 * USEC_PER_MSEC);
/*
* No polling interval specified in datasheet, so use reset time as
* polling interval and 10x reset time as timeout period.
*/
ret = regmap_read_poll_timeout(st->map, INV_ICM42607_REG_INT_STATUS,
val, val & INV_ICM42607_INT_STATUS_RESET_DONE,
1 * USEC_PER_MSEC, 10 * USEC_PER_MSEC);
And in the similar way in other fsleep() / _read_poll_timeout() cases.
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "reset error, reset done bit not set\n");
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-11 7:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 17:54 [PATCH V11 0/9] Add Invensense ICM42607 Chris Morgan
2026-06-10 17:54 ` [PATCH V11 1/9] dt-bindings: iio: imu: icm42600: Add mount-matrix to icm42600 Chris Morgan
2026-06-10 17:54 ` [PATCH V11 2/9] dt-bindings: iio: imu: icm42600: Add icm42607 Chris Morgan
2026-06-10 17:54 ` [PATCH V11 3/9] iio: imu: inv_icm42607: Add inv_icm42607 Core Driver Chris Morgan
2026-06-10 18:11 ` sashiko-bot
2026-06-11 7:35 ` Andy Shevchenko [this message]
2026-06-11 14:28 ` Chris Morgan
2026-06-11 11:09 ` Jonathan Cameron
2026-06-11 14:32 ` Chris Morgan
2026-06-11 16:20 ` Jonathan Cameron
2026-06-11 16:31 ` Chris Morgan
2026-06-12 10:42 ` Jonathan Cameron
2026-06-12 13:59 ` Chris Morgan
2026-06-10 17:54 ` [PATCH V11 4/9] iio: imu: inv_icm42607: Add I2C and SPI For icm42607 Chris Morgan
2026-06-10 18:25 ` sashiko-bot
2026-06-11 7:49 ` Andy Shevchenko
2026-06-11 10:52 ` Jonathan Cameron
2026-06-11 11:12 ` Jonathan Cameron
2026-06-19 13:54 ` Uwe Kleine-König
2026-06-10 17:54 ` [PATCH V11 5/9] iio: imu: inv_icm42607: Add PM support for icm42607 Chris Morgan
2026-06-11 8:00 ` Andy Shevchenko
2026-06-10 17:54 ` [PATCH V11 6/9] iio: imu: inv_icm42607: Add Temp Support in icm42607 Chris Morgan
2026-06-10 18:15 ` sashiko-bot
2026-06-11 11:22 ` Jonathan Cameron
2026-06-10 17:54 ` [PATCH V11 7/9] iio: imu: inv_icm42607: Add Accelerometer for icm42607 Chris Morgan
2026-06-10 18:10 ` sashiko-bot
2026-06-11 11:31 ` Jonathan Cameron
2026-06-10 17:54 ` [PATCH V11 8/9] iio: imu: inv_icm42607: Add Gyroscope to icm42607 Chris Morgan
2026-06-10 18:14 ` sashiko-bot
2026-06-10 17:54 ` [PATCH V11 9/9] arm64: dts: rockchip: Add icm42607p IMU for RG-DS Chris Morgan
2026-06-11 10:59 ` [PATCH V11 0/9] Add Invensense ICM42607 Jonathan Cameron
2026-06-11 14:36 ` Chris Morgan
2026-06-11 16:18 ` 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=aiplVZRI-0TCDnjL@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=heiko@sntech.de \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@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