On 30/11/2020 23:21, Laurent Pinchart wrote: >>> Instead, I propose, that you add this as an option to the tps68470 driver >>> that figures out whether the ACPI device for the tps68470 device actually >>> describes something else, in a similar fashion you do with the cio2-bridge >>> driver. I think it may need a separate Kconfig option albeit this and >>> cio2-bridge cannot be used separately. >> It actually occurs to me that that may not work (I know I called that >> out as an option we considered, but that was a while ago actually). The >> reason I wasn't worried about the existing tps68470 driver binding to >> these devices is that it's an i2c driver, and these dummy devices don't >> have an I2cSerialBusV2, so no I2C device is created by them the kernel. >> >> Won't that mean the tps68470 driver won't ever be probed for these devices? > I think we can create a platform driver in that case. The same module > can register multiple drivers (platform and I2C). Ah, I follow. OK, that's an option then.
