On Tue, 5 Dec 2017 13:38:01 +0200 Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > On Tue, Dec 05, 2017 at 11:27:38AM +0000, Jonathan Cameron wrote: > > Why does it not make sense to just create them all from the ACPI/I2C core? > > How do you know in ACPI/I2C core what is the right thing to do? Is it a > single device, like EEPROM with multiple addresses, or is it multiple > completely separate devices like in case of many sensors? Fine, though this seems like a flaw in the ACPI description as it isn't possible to tell the difference. Why it allows on ACPI description for multiple devices in one ACPI device is beyond me... More ACPI specific driver code that may eventually end up in every driver. Goody. Perhaps we can define a helper function to at least make this trivial and minimize the burden. Ultimately if this happens enough we could probably figure out how to move it into the I2C core entirely - flag in the i2c_driver structure for example. Jonathan -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
