From: Darius Berghe <darius.berghe@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <jic23@kernel.org>, <robh@kernel.org>
Subject: [PATCH v3 1/3] ltc2471: add of_match_table for existing devices
Date: Mon, 27 Jul 2020 16:58:32 +0300 [thread overview]
Message-ID: <20200727135834.84093-2-darius.berghe@analog.com> (raw)
In-Reply-To: <20200727135834.84093-1-darius.berghe@analog.com>
OF style match table was missing, this commit adds it.
Signed-off-by: Darius Berghe <darius.berghe@analog.com>
---
drivers/iio/adc/ltc2471.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/iio/adc/ltc2471.c b/drivers/iio/adc/ltc2471.c
index b88102b751cf..e1c4e966524d 100644
--- a/drivers/iio/adc/ltc2471.c
+++ b/drivers/iio/adc/ltc2471.c
@@ -14,6 +14,7 @@
#include <linux/module.h>
#include <linux/iio/iio.h>
#include <linux/iio/sysfs.h>
+#include <linux/mod_devicetable.h>
enum ltc2471_chips {
ltc2471,
@@ -144,9 +145,17 @@ static const struct i2c_device_id ltc2471_i2c_id[] = {
};
MODULE_DEVICE_TABLE(i2c, ltc2471_i2c_id);
+static const struct of_device_id ltc2471_of_match[] = {
+ { .compatible = "adi,ltc2471" },
+ { .compatible = "adi,ltc2473" },
+ {}
+};
+MODULE_DEVICE_TABLE(of, ltc2471_of_match);
+
static struct i2c_driver ltc2471_i2c_driver = {
.driver = {
.name = "ltc2471",
+ .of_match_table = ltc2471_of_match
},
.probe = ltc2471_i2c_probe,
.id_table = ltc2471_i2c_id,
--
2.27.0
next prev parent reply other threads:[~2020-07-27 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:58 iio:adc:ltc2371: add support for ltc2361/ltc2363 Darius Berghe
2020-07-27 13:58 ` Darius Berghe [this message]
2020-07-27 13:58 ` [PATCH v3 2/3] ltc2471: ltc2461/ltc2463 compatible strings Darius Berghe
2020-07-27 17:26 ` Jonathan Cameron
2020-07-28 6:24 ` Berghe, Darius
2020-08-01 16:05 ` Jonathan Cameron
2020-07-27 13:58 ` [PATCH v3 3/3] ltc2471 driver yaml Darius Berghe
2020-07-27 17:24 ` Jonathan Cameron
2020-07-27 18:15 ` Rob Herring
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=20200727135834.84093-2-darius.berghe@analog.com \
--to=darius.berghe@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.