hwmon: (tmp102) 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. Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
This commit is contained in:
parent
1c1a7b75bf
commit
15390c610f
|
@ -323,8 +323,15 @@ static const struct i2c_device_id tmp102_id[] = {
|
|||
};
|
||||
MODULE_DEVICE_TABLE(i2c, tmp102_id);
|
||||
|
||||
static const struct of_device_id tmp102_of_match[] = {
|
||||
{ .compatible = "ti,tmp102" },
|
||||
{ },
|
||||
};
|
||||
MODULE_DEVICE_TABLE(of, tmp102_of_match);
|
||||
|
||||
static struct i2c_driver tmp102_driver = {
|
||||
.driver.name = DRIVER_NAME,
|
||||
.driver.of_match_table = of_match_ptr(tmp102_of_match),
|
||||
.driver.pm = &tmp102_dev_pm_ops,
|
||||
.probe = tmp102_probe,
|
||||
.id_table = tmp102_id,
|
||||
|
|
Loading…
Reference in New Issue