On Thu, 2013-08-22 at 12:26 +0100, Mark Brown wrote: > On Thu, Aug 22, 2013 at 10:23:28AM +0100, Pawel Moll wrote: > > > If the platform data used to carry the (custom) irq data, the DT-powered > > driver could interrogate the DT on is own, couldn't it? Of course there > > should be some helper available, maybe something of that sort? (warning, > > untested) > > 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... Paweł -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
