'Technically' this table is still required for module autoloading, until some solution such as [0] is merged: [0] [PATCH RFC] modpost: Support I2C Aliases from OF tables https://lore.kernel.org/lkml/20190710193918.31135-1-kieran.bingham+renesas@xxxxxxxxxxxxxxxx/ However in practice, I think the only restriction that gets lost is device instantiation from sysfs, which wouldn't really work for this driver anyway, because it requires a description of connected endpoints. So - it should be quite safe to drop it. Signed-off-by: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx> --- drivers/media/i2c/max9286.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/drivers/media/i2c/max9286.c b/drivers/media/i2c/max9286.c index cdebee8a0a22..911323d6d3c4 100644 --- a/drivers/media/i2c/max9286.c +++ b/drivers/media/i2c/max9286.c @@ -1253,12 +1253,6 @@ static const struct of_device_id max9286_dt_ids[] = { }; MODULE_DEVICE_TABLE(of, max9286_dt_ids); -static const struct i2c_device_id max9286_id[] = { - { "max9286", 0 }, - { } -}; -MODULE_DEVICE_TABLE(i2c, max9286_id); - static struct i2c_driver max9286_i2c_driver = { .driver = { .name = "max9286", @@ -1266,7 +1260,6 @@ static struct i2c_driver max9286_i2c_driver = { }, .probe_new = max9286_probe, .remove = max9286_remove, - .id_table = max9286_id, }; module_i2c_driver(max9286_i2c_driver); -- 2.20.1
