From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: radu.sabau@analog.com
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@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-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: imu: Add driver for the ADI ADIS16607
Date: Mon, 12 Oct 2026 13:12:09 +0200 [thread overview]
Message-ID: <aszAHLVf7MEqvht7@monoceros> (raw)
In-Reply-To: <20261001-adis16607-v1-2-9c89cee35d56@analog.com>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
On Thu, Oct 01, 2026 at 12:11:50PM +0300, Radu Sabau via B4 Relay wrote:
> +#include <linux/mod_devicetable.h>
> [...]
> +#include <linux/spi/spi.h>
Please don't use <linux/mod_devicetable.h>. <linux/spi/spi.h> is good
enough to provide spi_device_id and of_device_id already.
> +static const struct spi_device_id adis16607_id[] = {
> + { "adis16607-2", (kernel_ulong_t)&adis16607_2_chip_info },
> + { "adis16607-3", (kernel_ulong_t)&adis16607_3_chip_info },
> + { }
Please use named initializers, i.e.
{ .name = "adis16607-2", .driver_data = (kernel_ulong_t)&adis16607_2_chip_info },
> +};
> +MODULE_DEVICE_TABLE(spi, adis16607_id);
> +
> +static const struct of_device_id adis16607_of_match[] = {
> + { .compatible = "adi,adis16607-2", .data = &adis16607_2_chip_info },
> + { .compatible = "adi,adis16607-3", .data = &adis16607_3_chip_info },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, adis16607_of_match);
> +
> +static struct spi_driver adis16607_driver = {
> + .driver = {
> + .name = "adis16607",
> + .of_match_table = adis16607_of_match,
> + },
> + .probe = adis16607_probe,
> + .id_table = adis16607_id,
> +};
> +module_spi_driver(adis16607_driver);
> +
> +MODULE_AUTHOR("Radu Sabau <radu.sabau@analog.com>");
> +MODULE_DESCRIPTION("Analog Devices ADIS16607 IMU driver");
> +MODULE_IMPORT_NS("IIO_ADISLIB");
> +MODULE_LICENSE("GPL");
>
> --
> 2.43.0
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-10-12 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 9:11 [PATCH 0/2] iio: imu: Add support for the ADI ADIS16607 Radu Sabau via B4 Relay
2026-10-01 9:11 ` Radu Sabau
2026-10-01 9:11 ` [PATCH 1/2] dt-bindings: iio: imu: Add bindings for " Radu Sabau via B4 Relay
2026-10-01 9:11 ` Radu Sabau
2026-10-01 9:15 ` sashiko-bot
2026-10-01 9:16 ` Sabau, Radu bogdan
2026-10-01 19:04 ` Conor Dooley
2026-10-05 12:53 ` Sabau, Radu bogdan
2026-10-01 9:11 ` [PATCH 2/2] iio: imu: Add driver for the " Radu Sabau via B4 Relay
2026-10-01 9:11 ` Radu Sabau
2026-10-01 9:26 ` sashiko-bot
2026-10-02 10:38 ` Andy Shevchenko
2026-10-02 11:05 ` Nuno Sá
2026-10-12 11:12 ` Uwe Kleine-König [this message]
2026-10-12 11:15 ` 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=aszAHLVf7MEqvht7@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=radu.sabau@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 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.