On AMD ISP4 platforms the amd_isp4 platform driver creates the sensor's
I2C client by name ("ov13b10"), with a software node and no ACPI
companion. The driver only has an ACPI match table, so the I2C core
does not bind it to that client.Add an I2C device ID table so the driver can bind to clients created by name. Nothing changes for ACPI-enumerated sensors. Signed-off-by: Seifelden Abdelmonem <[email protected]> --- drivers/media/i2c/ov13b10.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/drivers/media/i2c/ov13b10.c b/drivers/media/i2c/ov13b10.c index 242a95834..d33fb7032 100644 --- a/drivers/media/i2c/ov13b10.c +++ b/drivers/media/i2c/ov13b10.c @@ -1706,6 +1706,12 @@ static const struct acpi_device_id ov13b10_acpi_ids[] = { MODULE_DEVICE_TABLE(acpi, ov13b10_acpi_ids); #endif +static const struct i2c_device_id ov13b10_i2c_ids[] = { + { "ov13b10" }, + { } +}; +MODULE_DEVICE_TABLE(i2c, ov13b10_i2c_ids); + static struct i2c_driver ov13b10_i2c_driver = { .driver = { .name = "ov13b10", @@ -1715,6 +1721,7 @@ static struct i2c_driver ov13b10_i2c_driver = { .probe = ov13b10_probe, .remove = ov13b10_remove, .flags = I2C_DRV_ACPI_WAIVE_D0_PROBE, + .id_table = ov13b10_i2c_ids, }; module_i2c_driver(ov13b10_i2c_driver); -- 2.56.0
