From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Alexandru Ardelean <aardelean@deviqon.com>,
Robh+dt@kernel.org, Alexandru Ardelean <ardeleanalex@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH v2 20/24] staging:iio:cdc:ad7150: Add of_match_table
Date: Sun, 14 Mar 2021 18:15:07 +0000 [thread overview]
Message-ID: <20210314181511.531414-21-jic23@kernel.org> (raw)
In-Reply-To: <20210314181511.531414-1-jic23@kernel.org>
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Rather than using the fallback path in the i2c subsystem and hoping
for no clashes across vendors, lets put in an explicit table for
matching.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Link: https://lore.kernel.org/r/20210207154623.433442-21-jic23@kernel.org
---
drivers/staging/iio/cdc/ad7150.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/staging/iio/cdc/ad7150.c b/drivers/staging/iio/cdc/ad7150.c
index 30abfacda074..0afad49bcddc 100644
--- a/drivers/staging/iio/cdc/ad7150.c
+++ b/drivers/staging/iio/cdc/ad7150.c
@@ -12,6 +12,7 @@
#include <linux/i2c.h>
#include <linux/kernel.h>
#include <linux/module.h>
+#include <linux/mod_devicetable.h>
#include <linux/regulator/consumer.h>
#include <linux/slab.h>
@@ -655,9 +656,16 @@ static const struct i2c_device_id ad7150_id[] = {
MODULE_DEVICE_TABLE(i2c, ad7150_id);
+static const struct of_device_id ad7150_of_match[] = {
+ { "adi,ad7150" },
+ { "adi,ad7151" },
+ { "adi,ad7156" },
+ {}
+};
static struct i2c_driver ad7150_driver = {
.driver = {
.name = "ad7150",
+ .of_match_table = ad7150_of_match,
},
.probe = ad7150_probe,
.id_table = ad7150_id,
--
2.30.2
next prev parent reply other threads:[~2021-03-14 18:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 18:14 [PATCH v2 00/24] staging:iio:cdc:ad7150: cleanup / fixup / graduate Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 01/24] staging:iio:cdc:ad7150: use swapped reads for i2c rather than open coding Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 02/24] staging:iio:cdc:ad7150: Remove magnitude adaptive events Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 03/24] staging:iio:cdc:ad7150: Refactor event parameter update Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 04/24] staging:iio:cdc:ad7150: Timeout register covers both directions so both need updating Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 05/24] staging:iio:cdc:ad7150: Drop platform data support Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 06/24] staging:iio:cdc:ad7150: Handle variation in chan_spec across device and irq present or not Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 07/24] staging:iio:cdc:ad7150: Simplify event handling by only using rising direction Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 08/24] staging:iio:cdc:ad7150: Drop noisy print in probe Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 09/24] staging:iio:cdc:ad7150: Add sampling_frequency support Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 10/24] iio:event: Add timeout event info type Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 11/24] staging:iio:cdc:ad7150: Change timeout units to seconds and use core support Jonathan Cameron
2021-03-14 18:14 ` [PATCH v2 12/24] staging:iio:cdc:ad7150: Rework interrupt handling Jonathan Cameron
2021-03-31 7:29 ` Alexandru Ardelean
2021-03-31 12:05 ` Jonathan Cameron
2021-04-01 7:42 ` Alexandru Ardelean
2021-03-14 18:15 ` [PATCH v2 13/24] staging:iio:cdc:ad7150: More consistent register and field naming Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 14/24] staging:iio:cdc:ad7150: Reorganize headers Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 15/24] staging:iio:cdc:ad7150: Tidy up local variable positioning Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 16/24] staging:iio:cdc:ad7150: Drop unnecessary block comments Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 17/24] staging:iio:cdc:ad7150: Shift the _raw readings by 4 bits Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 18/24] staging:iio:cdc:ad7150: Add scale and offset to info_mask_shared_by_type Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 19/24] staging:iio:cdc:ad7150: Really basic regulator support Jonathan Cameron
2021-03-14 18:15 ` Jonathan Cameron [this message]
2021-03-31 6:42 ` [PATCH v2 20/24] staging:iio:cdc:ad7150: Add of_match_table Alexandru Ardelean
2021-03-14 18:15 ` [PATCH v2 21/24] iio:Documentation:ABI Add missing elements as used by the adi,ad7150 Jonathan Cameron
2021-03-31 6:45 ` Alexandru Ardelean
2021-03-14 18:15 ` [PATCH v2 22/24] staging:iio:cdc:ad7150: Add copyright notice given substantial changes Jonathan Cameron
2021-03-14 18:15 ` [PATCH v2 23/24] dt-bindings:iio:cdc:adi,ad7150 binding doc Jonathan Cameron
2021-03-24 17:13 ` Rob Herring
2021-03-14 18:15 ` [PATCH v2 24/24] iio:cdc:ad7150: Move driver out of staging Jonathan Cameron
2021-03-29 15:30 ` [PATCH v2 00/24] staging:iio:cdc:ad7150: cleanup / fixup / graduate Jonathan Cameron
2021-03-29 15:36 ` Jonathan Cameron
2021-03-30 21:23 ` Song Bao Hua (Barry Song)
2021-03-31 12:13 ` Jonathan Cameron
2021-04-01 10:15 ` Song Bao Hua (Barry Song)
2021-04-01 13:05 ` Jonathan Cameron
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=20210314181511.531414-21-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=Robh+dt@kernel.org \
--cc=aardelean@deviqon.com \
--cc=ardeleanalex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.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.