redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

mfd: retu: 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 a
OF device ID table if the devices are registered via OF.

Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>
Acked-by: Tony Lindgren <tony@atomide.com>
Reviewed-by: Wolfram Sang <wsa@the-dreams.de>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
hifive-unleashed-5.1
Javier Martinez Canillas 2017-06-15 20:49:23 +02:00 committed by Lee Jones
parent c05581d885
commit 46c20bdfd1
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
drivers/mfd/retu-mfd.c
View File

@ -308,9 +308,17 @@ static const struct i2c_device_id retu_id[] = {
};
MODULE_DEVICE_TABLE(i2c, retu_id);
static const struct of_device_id retu_of_match[] = {
{ .compatible = "nokia,retu" },
{ .compatible = "nokia,tahvo" },
{ }
};
MODULE_DEVICE_TABLE(of, retu_of_match);
static struct i2c_driver retu_driver = {
.driver = {
.name = "retu-mfd",
.of_match_table = retu_of_match,
},
.probe = retu_probe,
.remove = retu_remove,