From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, Andy Shevchenko <andy@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Mike Looijmans" <mike.looijmans@topic.nl>,
"Liam Beguin" <liambeguin@gmail.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Ibrahim Tilki" <Ibrahim.Tilki@analog.com>,
"Cosmin Tanislav" <cosmin.tanislav@analog.com>,
"Alisa-Dariana Roman" <alisadariana@gmail.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: [PATCH 06/11] iio: adc: max11410: Improve relevance of includes
Date: Mon, 19 Jan 2026 21:21:05 +0000 [thread overview]
Message-ID: <20260119212110.726941-7-jic23@kernel.org> (raw)
In-Reply-To: <20260119212110.726941-1-jic23@kernel.org>
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Drop kernel.h in favor of more specific headers and add other headers that
were previously only indirectly included. Also add a forwards definition
of struct regulator as it is only used as an opaque pointer type in this
file.
Justification for new headers from iwyu:
#include <linux/array_size.h> // for ARRAY_SIZE
#include <linux/bitops.h> // for BIT, GENMASK, __clear_bit
#include <linux/cleanup.h> // for guard
#include <linux/compiler.h> // for __aligned
#include <linux/completion.h> // for complete, init_completion
#include <linux/iio/iio.h> // for iio_chan_spec, iio_chan_info...
#include <linux/iopoll.h> // for read_poll_timeout
#include <linux/jiffies.h> // for msecs_to_jiffies
#include <linux/kstrtox.h> // for kstrtobool
#include <linux/log2.h> // for order_base_2
#include <linux/math.h> // for DIV_ROUND_CLOSEST
#include <linux/minmax.h> // for clamp_val, __cmp_op_max
#include <linux/mod_devicetable.h> // for of_device_id, spi_device_id
#include <linux/mutex.h> // for class_mutex_constructor, mut...
#include <linux/property.h> // for fwnode_property_read_u32
#include <linux/stddef.h> // for NULL, true
#include <linux/sysfs.h> // for sysfs_emit, attribute_group
#include <linux/types.h> // for u32, u8, bool, ssize_t, alig...
struct regulator;
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Ibrahim Tilki <Ibrahim.Tilki@analog.com>
---
drivers/iio/adc/max11410.c | 22 ++++++++++++++++++++--
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/adc/max11410.c b/drivers/iio/adc/max11410.c
index 511b2f14dfaf..c8a9718c4e4b 100644
--- a/drivers/iio/adc/max11410.c
+++ b/drivers/iio/adc/max11410.c
@@ -4,20 +4,36 @@
*
* Copyright 2022 Analog Devices Inc.
*/
+#include <linux/array_size.h>
+#include <linux/bitops.h>
#include <linux/bitfield.h>
+#include <linux/cleanup.h>
+#include <linux/compiler.h>
+#include <linux/completion.h>
#include <linux/delay.h>
#include <linux/device.h>
#include <linux/err.h>
#include <linux/interrupt.h>
-#include <linux/kernel.h>
+#include <linux/iopoll.h>
+#include <linux/jiffies.h>
+#include <linux/kstrtox.h>
+#include <linux/log2.h>
+#include <linux/math.h>
+#include <linux/minmax.h>
#include <linux/module.h>
+#include <linux/mod_devicetable.h>
+#include <linux/mutex.h>
+#include <linux/property.h>
#include <linux/regmap.h>
#include <linux/regulator/consumer.h>
#include <linux/spi/spi.h>
-
+#include <linux/stddef.h>
+#include <linux/sysfs.h>
+#include <linux/types.h>
#include <linux/unaligned.h>
#include <linux/iio/buffer.h>
+#include <linux/iio/iio.h>
#include <linux/iio/sysfs.h>
#include <linux/iio/trigger.h>
#include <linux/iio/trigger_consumer.h>
@@ -130,6 +146,8 @@ struct max11410_channel_config {
bool buffered_vrefn;
};
+struct regulator;
+
struct max11410_state {
struct spi_device *spi_dev;
struct iio_trigger *trig;
--
2.52.0
next prev parent reply other threads:[~2026-01-19 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 21:20 [PATCH 00/11] iio: adc: Improve include relevance for some ADCs Jonathan Cameron
2026-01-19 21:21 ` [PATCH 01/11] iio: adc: ltc2471: Improve include relevance Jonathan Cameron
2026-01-20 7:51 ` Andy Shevchenko
2026-01-19 21:21 ` [PATCH 02/11] iio: adc: ltc2309: " Jonathan Cameron
2026-01-20 7:52 ` Andy Shevchenko
2026-01-19 21:21 ` [PATCH 03/11] iio: adc: max1027: Reorder headers into alphabetical order Jonathan Cameron
2026-01-20 7:53 ` Andy Shevchenko
2026-01-19 21:21 ` [PATCH 04/11] iio: adc: max1027: Improve include relevance Jonathan Cameron
2026-01-20 7:56 ` Andy Shevchenko
2026-01-20 22:10 ` Jonathan Cameron
2026-01-20 22:52 ` Andy Shevchenko
2026-01-21 9:37 ` Nuno Sá
2026-01-19 21:21 ` [PATCH 05/11] iio: adc: max11100: " Jonathan Cameron
2026-01-19 21:21 ` Jonathan Cameron [this message]
2026-01-19 21:21 ` [PATCH 07/11] iio: adc: ad4130: " Jonathan Cameron
2026-01-19 21:21 ` [PATCH 08/11] iio: adc: ad7124: " Jonathan Cameron
2026-01-19 21:21 ` [PATCH 09/11] iio: adc: ad7124: Replace device.h with more specific includes Jonathan Cameron
2026-01-19 21:21 ` [PATCH 10/11] iio: adc: ad7192: Put headers in alphabetical order Jonathan Cameron
2026-01-19 21:21 ` [PATCH 11/11] iio: adc: ad7192: Improve include relevance Jonathan Cameron
2026-01-20 7:58 ` [PATCH 00/11] iio: adc: Improve include relevance for some ADCs Andy Shevchenko
2026-01-21 9:41 ` Nuno Sá
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=20260119212110.726941-7-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Ibrahim.Tilki@analog.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alisadariana@gmail.com \
--cc=andy@kernel.org \
--cc=cosmin.tanislav@analog.com \
--cc=dlechner@baylibre.com \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=miquel.raynal@bootlin.com \
--cc=nuno.sa@analog.com \
/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.