From: Jonathan Cameron <jic23@kernel.org>
To: Remi Buisson <Remi.Buisson@tdk.com>
Cc: "Remi Buisson via B4 Relay"
<devnull+remi.buisson.tdk.com@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v6 3/9] iio: imu: inv_icm45600: add buffer support in iio devices
Date: Sat, 4 Oct 2025 16:41:23 +0100 [thread overview]
Message-ID: <20251004164123.4faf4b45@jic23-huawei> (raw)
In-Reply-To: <FR2PPF4571F02BC2026559022A8291EC5DD8CE6A@FR2PPF4571F02BC.DEUP281.PROD.OUTLOOK.COM>
On Wed, 1 Oct 2025 12:07:40 +0000
Remi Buisson <Remi.Buisson@tdk.com> wrote:
> >
> >
> >From: Jonathan Cameron <jic23@kernel.org>
> >Sent: Sunday, September 28, 2025 10:45 AM
> >To: Remi Buisson via B4 Relay <devnull+remi.buisson.tdk.com@kernel.org>
> >Cc: Remi Buisson <Remi.Buisson@tdk.com>; David Lechner <dlechner@baylibre.com>; Nuno Sá <nuno.sa@analog.com>; Andy Shevchenko <andy@kernel.org>; Rob Herring <robh@kernel.org>; Krzysztof Kozlowski <krzk+dt@kernel.org>; Conor Dooley <conor+dt@kernel.org>; linux-kernel@vger.kernel.org; linux-iio@vger.kernel.org; devicetree@vger.kernel.org
> >Subject: Re: [PATCH v6 3/9] iio: imu: inv_icm45600: add buffer support in iio devices
> >
> >On Wed, 24 Sep 2025 09:23:56 +0000
> >Remi Buisson via B4 Relay <devnull+remi.buisson.tdk.com@kernel.org> wrote:
> >
> >> From: Remi Buisson <remi.buisson@tdk.com>
> >>
> >> Add FIFO control functions.
> >> Support hwfifo watermark by multiplexing gyro and accel settings.
> >> Support hwfifo flush.
> >>
> >> Signed-off-by: Remi Buisson <remi.buisson@tdk.com>
> >Hi Remi,
> >
> >A few trivial things in here as well.
> >
> >Jonathan
> Thanks again for the review !
> Remi
> >
> >> diff --git a/drivers/iio/imu/inv_icm45600/inv_icm45600.h b/drivers/iio/imu/inv_icm45600/inv_icm45600.h
> >> index 5f637e2f2ec8f1537459459dbb7e8a796d0ef7a6..aac8cd852c12cfba5331f2b7c1ffbbb2ed23d1c7 100644
> >> --- a/drivers/iio/imu/inv_icm45600/inv_icm45600.h
> >> +++ b/drivers/iio/imu/inv_icm45600/inv_icm45600.h
> >> @@ -5,6 +5,7 @@
> >> #define INV_ICM45600_H_
> >>
> >> #include <linux/bits.h>
> >> +#include <linux/limits.h>
> >
> >Why this in the header? Should be only needed in some of the c files I think
> >so push the include down there.
> This is because the below line uses U8_MAX:
> #define INV_ICM45600_SENSOR_CONF_KEEP_VALUES { U8_MAX, U8_MAX, U8_MAX, U8_MAX }
> So I guess the header from where it comes from should be included.
> Please correct if I miss something.
Nope. Should indeed be there. I just missed that.
> >
> ...
> >
> >> diff --git a/drivers/iio/imu/inv_icm45600/inv_icm45600_buffer.h b/drivers/iio/imu/inv_icm45600/inv_icm45600_buffer.h
> >> new file mode 100644
> >> index 0000000000000000000000000000000000000000..0c8caa8287dd4373cf11bb6c7b913a6c49e9eee5
> >> --- /dev/null
> >> +++ b/drivers/iio/imu/inv_icm45600/inv_icm45600_buffer.h
> >
> >> +
> >> +/**
> >> + * struct inv_icm45600_fifo - FIFO state variables
> >> + * @on: reference counter for FIFO on.
> >> + * @en: bits field of INV_ICM45600_SENSOR_* for FIFO EN bits.
> >> + * @period: FIFO internal period.
> >> + * @watermark: watermark configuration values for accel and gyro.
> >Given the contents of this to me look like things to also document.e
> > * @watermark.gyro: ....
> >etc as well would be good to add
> >
> >> + * @count: number of bytes in the FIFO data buffer.
> >> + * @nb: gyro, accel and total samples in the FIFO data buffer.
> >
> >This is more obvious. Check if the kernel-doc script minds these subfields not
> >being defined. If it does, add a the trivial documentation just to squash warnings
> >and make it easier to spot real issues.
>
> With my setup "./scripts/kernel-doc.py -v -none drivers/iio/imu/inv_icm45600/*" does not catch anything, even with -Wall.
> I'll detail the gyro/accel watermark comment anyway.
I guess it doesn't mind not documenting nested structure elements
Jonathan
>
next prev parent reply other threads:[~2025-10-04 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 9:23 [PATCH v6 0/9] iio: imu: new inv_icm45600 driver Remi Buisson via B4 Relay
2025-09-24 9:23 ` [PATCH v6 1/9] dt-bindings: iio: imu: Add inv_icm45600 Remi Buisson via B4 Relay
2025-09-24 19:17 ` Conor Dooley
2025-09-24 9:23 ` [PATCH v6 2/9] iio: imu: inv_icm45600: add new inv_icm45600 driver Remi Buisson via B4 Relay
2025-09-28 8:30 ` Jonathan Cameron
2025-09-24 9:23 ` [PATCH v6 3/9] iio: imu: inv_icm45600: add buffer support in iio devices Remi Buisson via B4 Relay
2025-09-28 8:45 ` Jonathan Cameron
2025-10-01 12:07 ` Remi Buisson
2025-10-04 15:41 ` Jonathan Cameron [this message]
2025-09-24 9:23 ` [PATCH v6 4/9] iio: imu: inv_icm45600: add IMU IIO gyroscope device Remi Buisson via B4 Relay
2025-09-28 8:52 ` Jonathan Cameron
2025-09-24 9:23 ` [PATCH v6 5/9] iio: imu: inv_icm45600: add IMU IIO accelerometer device Remi Buisson via B4 Relay
2025-09-24 9:23 ` [PATCH v6 6/9] iio: imu: inv_icm45600: add I2C driver for inv_icm45600 driver Remi Buisson via B4 Relay
2025-09-24 9:24 ` [PATCH v6 7/9] iio: imu: inv_icm45600: add SPI " Remi Buisson via B4 Relay
2025-09-25 0:34 ` kernel test robot
2025-09-28 9:00 ` Jonathan Cameron
2025-09-24 9:24 ` [PATCH v6 8/9] iio: imu: inv_icm45600: add I3C " Remi Buisson via B4 Relay
2025-09-24 9:24 ` [PATCH v6 9/9] MAINTAINERS: add entry for inv_icm45600 6-axis imu sensor Remi Buisson via B4 Relay
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=20251004164123.4faf4b45@jic23-huawei \
--to=jic23@kernel.org \
--cc=Remi.Buisson@tdk.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+remi.buisson.tdk.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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