On Thu, Aug 22, 2013 at 12:44:04PM +0100, Pawel Moll wrote: > On Thu, 2013-08-22 at 12:26 +0100, Mark Brown wrote: > > Yes, that's probably the most straightforward thing - we'd need to > > either have the bindings specify which interrupt must be first for > > reading i2c->irq or just have the drivers always do a name based lookup > > if there's more than one interrupt. > ... or make sure that of_i2c_register_devices() does *not* set i2c->irq > (or rather: set it to 0) when there is more than one interrupt in the > tree... Yes, that'd be a really good idea if the drivers are always getting the interrupts by name, provides a backup.
Attachment:
signature.asc
Description: Digital signature
