> As mentioned in an earlier reply in this thread, the only alternative > to this patch-set which I see would be to duplicate the list of > ACPI HIDs found in the new drivers/i2c/i2c-multi-instantiate.c > inside code under drivers/acpi and make the acpi code not > skip enumerating devices with these HIDs as platform drivers. > > Then the i2c-multi-instantiate.c driver could become a > platform driver (*) and the I2C_CLIENT_IGNORE_BUSY > flag / hack can go away (at the price of duplicating > the HIDs in 2 places). What is the downside of duplicating the HID? My gut feeling is that it can't be worse than having two devices mapped to the same I2C address and work around that by I2C_CLIENT_IGNORE_BUSY. But I may be biased :) I mean this is broken firmware, and having that fixed in ACPI and platform/x86 code instead of I2C core sounds way more proper to me.
Attachment:
signature.asc
Description: PGP signature
