On Wed, Jun 8, 2016 at 3:41 PM, Pantelis Antoniou <pantelis.antoniou@xxxxxxxxxxxx> wrote: > Devices that use interrupts usually convert the GPIO to an interrupt and use it. > Since the xlat op will return the real GPIO spec the interrupt conversion will work. > > Bare interrupt lines are sort-of out of fashion nowadays I think. I’m eager to be > proven wrong though with a recent portable expansion board that uses them. No. We have established since several years back that gpiochip and interrupt chip use cases are orthogonal, and there is absolutely *NO* requirement that a consumer call .to_irq() on a GPIO line before using it as an interrupt, if the driver exposes an interrupt chip. It is true that external interrupt lines are out-of-fashion and usually replaced with GPIOs that can trigger IRQs. However the latter have two interfaces independent of each other. A practical usecase is the SMSC911x ethernet drivers that have their IRQ wired to both external interrupt lines and GPIO lines used as IRQ in different use cases. It should not need to know whether the interrupt provider is a "real" IRQ line or a GPIO line providing an IRQ. It just wants "some IRQ", and this should be hidden from the driver and the hardware's DT bindings. 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
