path: root/drivers/input
diff options
authorJavier Martinez Canillas <javier@osg.samsung.com>2017-03-23 13:33:12 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2017-03-23 14:46:33 -0700
commitcf5cd9d4480a87da78768718cac194a71079b5cb (patch)
tree0f5d9b9ad8b64e62a2be6b5df326fbeb729cc296 /drivers/input
parentInput: synaptics_i2c - add OF device ID table (diff)
Input: qt1070 - add OF device ID table
The driver doesn't have a struct of_device_id table but supported devices are registered via Device Trees. This is working on the assumption that a I2C device registered via OF will always match a legacy I2C device ID and that the MODALIAS reported will always be of the form i2c:<device>. But this could change in the future so the correct approach is to have an OF device ID table if the devices are registered via OF. The compatible strings don't have a vendor prefix because that's how it's used currently, and changing this will be a Device Tree ABI break. Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input')
1 files changed, 9 insertions, 0 deletions
diff --git a/drivers/input/keyboard/qt1070.c b/drivers/input/keyboard/qt1070.c
index 5a5778729e37..76bb51309a78 100644
--- a/drivers/input/keyboard/qt1070.c
+++ b/drivers/input/keyboard/qt1070.c
@@ -274,9 +274,18 @@ static const struct i2c_device_id qt1070_id[] = {
MODULE_DEVICE_TABLE(i2c, qt1070_id);
+#ifdef CONFIG_OF
+static const struct of_device_id qt1070_of_match[] = {
+ { .compatible = "qt1070", },
+ { },
+MODULE_DEVICE_TABLE(of, qt1070_of_match);
static struct i2c_driver qt1070_driver = {
.driver = {
.name = "qt1070",
+ .of_match_table = of_match_ptr(qt1070_of_match),
.pm = &qt1070_pm_ops,
.id_table = qt1070_id,