diff options
| author | Javier Martinez Canillas <javier@osg.samsung.com> | 2017-03-03 11:29:14 -0300 |
|---|---|---|
| committer | Alexandre Belloni <alexandre.belloni@free-electrons.com> | 2017-03-09 01:29:17 +0100 |
| commit | 36138c70e69c9272bd7e0be517f1ac7ad0c4f0df (patch) | |
| tree | cc200a6f965c0f36432f12985593beef6a7088d9 /drivers/rtc | |
| parent | e696a1dd7e80ee64fd930982d9e1c6b152635534 (diff) | |
| download | linux-36138c70e69c9272bd7e0be517f1ac7ad0c4f0df.tar.gz linux-36138c70e69c9272bd7e0be517f1ac7ad0c4f0df.tar.bz2 linux-36138c70e69c9272bd7e0be517f1ac7ad0c4f0df.zip | |
rtc: bq32k: 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: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Diffstat (limited to 'drivers/rtc')
| -rw-r--r-- | drivers/rtc/rtc-bq32k.c | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/drivers/rtc/rtc-bq32k.c b/drivers/rtc/rtc-bq32k.c index 2b223935001f..98ac8d5c7901 100644 --- a/drivers/rtc/rtc-bq32k.c +++ b/drivers/rtc/rtc-bq32k.c @@ -310,9 +310,16 @@ static const struct i2c_device_id bq32k_id[] = { }; MODULE_DEVICE_TABLE(i2c, bq32k_id); +static const struct of_device_id bq32k_of_match[] = { + { .compatible = "ti,bq32000" }, + { } +}; +MODULE_DEVICE_TABLE(of, bq32k_of_match); + static struct i2c_driver bq32k_driver = { .driver = { .name = "bq32k", + .of_match_table = of_match_ptr(bq32k_of_match), }, .probe = bq32k_probe, .remove = bq32k_remove, |