[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20201016185046.GA16022@ubuntu>
Date: Sat, 17 Oct 2020 00:21:25 +0530
From: Vaishnav M A <vaishnav@...gleboard.org>
To: songqiang1304521@...il.com, jic23@...nel.org, knaack.h@....de,
lars@...afoo.de, pmeerw@...erw.net, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: jkridner@...gleboard.org, drew@...gleboard.org,
robertcnelson@...gleboard.org, rajkovic@...roe.com
Subject: [PATCH] iio: proximity: vl53l0x-i2c add i2c_device_id
Hi,
This patch aims to add i2c_device_id for the vl53l0x-i2c driver.
will it be possible to consider this patch add the i2c_device_id,
so that the device can be instantiated using i2c_new_client_device
or say from the userspace?.This will be really helpful in cases
where the device tree based description is not possible now(Eg.
a device on a gbphy i2c adapter created by greybus).
The particular usecase here is described over this RFC Patch
for the mikroBUS driver:
https://lore.kernel.org/patchwork/patch/1290148/
Thanks and Regards,
Vaishnav M A
Signed-off-by: Vaishnav M A <vaishnav@...gleboard.org>
---
drivers/iio/proximity/vl53l0x-i2c.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c
index 5fbda9475ba9..7c29d4cae24a 100644
--- a/drivers/iio/proximity/vl53l0x-i2c.c
+++ b/drivers/iio/proximity/vl53l0x-i2c.c
@@ -143,6 +143,12 @@ static int vl53l0x_probe(struct i2c_client *client)
return devm_iio_device_register(&client->dev, indio_dev);
}
+static const struct i2c_device_id vl53l0x_id[] = {
+ { "vl53l0x", 0},
+ { }
+};
+MODULE_DEVICE_TABLE(i2c, vl53l0x_id);
+
static const struct of_device_id st_vl53l0x_dt_match[] = {
{ .compatible = "st,vl53l0x", },
{ }
@@ -155,6 +161,7 @@ static struct i2c_driver vl53l0x_driver = {
.of_match_table = st_vl53l0x_dt_match,
},
.probe_new = vl53l0x_probe,
+ .id_table = vl53l0x_id,
};
module_i2c_driver(vl53l0x_driver);
--
2.25.1
Powered by blists - more mailing lists