On Saturday, October 12, 2013 08:04:13 AM Mika Westerberg wrote: > On Sat, Oct 12, 2013 at 12:16:02AM +0200, Rafael J. Wysocki wrote: > > > I think that this is intentional. We don't want that the i2c modalias > > > matches with the ACPI device (like with the i2c:INTABCD). Instead use ACPI > > > IDs that are added to the driver to match with the ACPI device. > > > > Well, I'm not really sure this was intentional, but I wonder how other bus > > types work in that respect? > > We have the same for platform bus, if that's what you are asking. > > It probably doesn't hurt to have this patch applied but it might cause > inadvertent match if for some reason there is an I2C client driver that > happens to have INTABCD I2C id in its list. Well, if they have that id in their lists, they are supposed to be able to handle this device, aren't they? What other reason may be there for them to put that id into their lists? -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
