On Thu, Aug 22, 2013 at 1:10 AM, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: >> On Wednesday 21 of August 2013 15:38:54 Lars Poeschel wrote: >>> To solve this dilemma, perform an interrupt consistency check >>> when adding a GPIO chip: if the chip is both gpio-controller and >>> interrupt-controller, walk all children of the device tree, > > It seems a little odd to solve this only for DT. What about the non-DT case? DT is the hardware configuration system that lets you request the same resource in two ways, i.e. it allows one and the same node to be both gpio-controller and interrupt-controller, and start handing out the same line as both GPIO and IRQ independently. I asked if ACPI had this ambiguity, and the answer appears to be either "no" (which I suspect) or just "nobody knows" :-/ In either way, checking the consistency of ACPI IRQs vs GPIOs will be fundamentally different, should it have the same problem, and does it appear we can certainly refactor this to be shared, should there be something to gain from. Yours, Linus Walleij -- 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
