On Mon, Sep 11, 2017 at 02:16:49PM -0500, Alan Tull wrote: > Add new device tree binding for max1619. > > Signed-off-by: Alan Tull <[email protected]>
Technically that should already work, without explicit binding, or did the i2c core change lately ? Guenter > Cc: Jean Delvare <[email protected]> > Cc: Guenter Roeck <[email protected]> > Cc: Rob Herring <[email protected]> > Cc: Mark Rutland <[email protected]> > --- > drivers/hwmon/max1619.c | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/drivers/hwmon/max1619.c b/drivers/hwmon/max1619.c > index a182789..76d9669 100644 > --- a/drivers/hwmon/max1619.c > +++ b/drivers/hwmon/max1619.c > @@ -303,10 +303,20 @@ static const struct i2c_device_id max1619_id[] = { > }; > MODULE_DEVICE_TABLE(i2c, max1619_id); > > +#ifdef CONFIG_OF > +static const struct of_device_id max1619_of_match[] = { > + { .compatible = "maxim,max1619", }, > + {}, > +}; > + > +MODULE_DEVICE_TABLE(of, max1619_of_match); > +#endif > + > static struct i2c_driver max1619_driver = { > .class = I2C_CLASS_HWMON, > .driver = { > .name = "max1619", > + .of_match_table = of_match_ptr(max1619_of_match), > }, > .probe = max1619_probe, > .id_table = max1619_id, > -- > 2.7.4 >
