From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Cc: Jason Liu <jasonliu10041728@gmail.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] iio/inv_icm42600: add inv_icm42600 id_table
Date: Mon, 26 Aug 2024 11:20:48 +0100 [thread overview]
Message-ID: <20240826111858.7824a811@jic23-huawei> (raw)
In-Reply-To: <FR3P281MB1757A595F22A1F9AE50B76B1CE8B2@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>
On Mon, 26 Aug 2024 08:22:11 +0000
Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com> wrote:
> Hello,
>
> I was believing that id tables weren't required anymore when using of tables.
>
> Jonathan,
> can you help on this subject?
>
> If we have to add id tables, then we need to add all supported chips (missing here icm42686 and icm42688).
There were some oddities around autoloading for some busses a while
back but I can't find the reference.
+CC Mark + Wolfram for input.
Do we currently need i2c_device_id and spi_device_id tables for
autoprobing on DT only platforms?
A few minor comments inline.
>
> Thanks,
> JB
>
> ________________________________________
> From: Jason Liu <jasonliu10041728@gmail.com>
> Sent: Sunday, August 25, 2024 08:39
> To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
> Cc: jic23@kernel.org <jic23@kernel.org>; lars@metafoo.de <lars@metafoo.de>; linux-iio@vger.kernel.org <linux-iio@vger.kernel.org>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; Jason Liu <jasonliu10041728@gmail.com>
> Subject: [PATCH] iio/inv_icm42600: add inv_icm42600 id_table
>
> This Message Is From an Untrusted Sender
> You have not previously corresponded with this sender.
>
> Add the id_table of inv_icm42600, so the device can probe correctly.
>
> Signed-off-by: Jason Liu <jasonliu10041728@gmail.com>
> ---
> drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c | 15 +++++++++++++++
> drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c | 15 +++++++++++++++
> 2 files changed, 30 insertions(+)
>
> diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> index ebb31b385881..8cc550b8cfc3 100644
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> @@ -71,6 +71,20 @@ static int inv_icm42600_probe(struct i2c_client *client)
> inv_icm42600_i2c_bus_setup);
> }
>
> +/*
> + * device id table is used to identify what device can be
> + * supported by this driver
> + */
> +static const struct i2c_device_id inv_icm42600_id[] = {
> + {"icm42600", INV_CHIP_ICM42600},
Spaces after { and before }
> + {"icm42602", INV_CHIP_ICM42602},
> + {"icm42605", INV_CHIP_ICM42605},
> + {"icm42622", INV_CHIP_ICM42622},
> + {"icm42631", INV_CHIP_ICM42631},
> + {}
{ }
I'm trying to standardize this in IIO.
> +};
> +MODULE_DEVICE_TABLE(i2c, inv_icm42600_id);
> +
> static const struct of_device_id inv_icm42600_of_matches[] = {
> {
> .compatible = "invensense,icm42600",
> @@ -104,6 +118,7 @@ static struct i2c_driver inv_icm42600_driver = {
> .of_match_table = inv_icm42600_of_matches,
> .pm = pm_ptr(&inv_icm42600_pm_ops),
> },
> + .id_table = inv_icm42600_id,
> .probe = inv_icm42600_probe,
> };
> module_i2c_driver(inv_icm42600_driver);
> diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c
> index eae5ff7a3cc1..5fe078ddc8a1 100644
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c
> @@ -67,6 +67,20 @@ static int inv_icm42600_probe(struct spi_device *spi)
> inv_icm42600_spi_bus_setup);
> }
>
> +/*
> + * device id table is used to identify what device can be
> + * supported by this driver
> + */
> +static const struct spi_device_id inv_icm42600_id[] = {
> + {"icm42600", INV_CHIP_ICM42600},
> + {"icm42602", INV_CHIP_ICM42602},
> + {"icm42605", INV_CHIP_ICM42605},
> + {"icm42622", INV_CHIP_ICM42622},
> + {"icm42631", INV_CHIP_ICM42631},
> + {}
> +};
> +MODULE_DEVICE_TABLE(spi, inv_icm42600_id);
> +
> static const struct of_device_id inv_icm42600_of_matches[] = {
> {
> .compatible = "invensense,icm42600",
> @@ -100,6 +114,7 @@ static struct spi_driver inv_icm42600_driver = {
> .of_match_table = inv_icm42600_of_matches,
> .pm = pm_ptr(&inv_icm42600_pm_ops),
> },
> + .id_table = inv_icm42600_id,
> .probe = inv_icm42600_probe,
> };
> module_spi_driver(inv_icm42600_driver);
next prev parent reply other threads:[~2024-08-26 10:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 6:39 [PATCH] iio/inv_icm42600: add inv_icm42600 id_table Jason Liu
2024-08-26 8:22 ` Jean-Baptiste Maneyrol
2024-08-26 10:20 ` Jonathan Cameron [this message]
[not found] ` <CAJci1vCztZAnmHrVn=4b9hnRmMCQE=6R7uQnznPQ0FSpFHQK5w@mail.gmail.com>
2024-09-01 14:23 ` Jonathan Cameron
2024-09-02 3:11 ` Jason Liu
2024-09-02 9:58 ` Jean-Baptiste Maneyrol
2024-09-02 11:31 ` Jason Liu
[not found] ` <CAJci1vC9pvdqEpA8sk+uB5jJGn_DKUruXFfY6tbG9mO07YxgHQ@mail.gmail.com>
2024-09-05 9:25 ` Jean-Baptiste Maneyrol
2024-09-07 13:48 ` Jonathan Cameron
[not found] ` <SI6PR01MB63197238674C8895885420D8F59E2@SI6PR01MB6319.apcprd01.prod.exchangelabs.com>
2024-09-08 10:51 ` 回复: " Jonathan Cameron
2024-09-09 6:43 ` 回复: " jason liu
2024-09-09 7:35 ` Jonathan Cameron
2024-09-09 7:39 ` 回复: " jason liu
[not found] <jic23@kernel.org>
2024-09-02 2:58 ` Jason Liu
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=20240826111858.7824a811@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jean-Baptiste.Maneyrol@tdk.com \
--cc=broonie@kernel.org \
--cc=jasonliu10041728@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox