On Mon, Jan 9, 2017 at 8:44 PM, David Daney <ddaney@xxxxxxxxxxxxxxxxxx> wrote: > On 01/09/2017 11:36 AM, Linus Walleij wrote: >>> +Optional Properties: >>> +- compatible: "cavium,thunder-8890-gpio", unused as PCI driver binding >>> is used. >>> +- interrupt-controller: Marks the device node as an interrupt >>> controller. >>> +- #interrupt-cells: Must be present and have value of 2 if >>> + "interrupt-controller" is present. >>> + - First cell is the GPIO pin number relative to the controller. >>> + - Second cell is triggering flags as defined in interrupts.txt. >> >> >> AFAICT this device has an optional list of interrupts as well? >> One per pin even? > > I'm not sure I understand your question. > > The GPIO hardware supports an interrupt on each pin. The underlying > interrupt mechanism is via PCI MSI-X, which are fully discoverable by the > driver, so lack of device tree binding for the these underlying MSI-X is > fully appropriate. Sorry I guess I'm just ignorant about how PCI works, that has never been my strongest subject admittedly. So what you're saying is that PCI devices do not need specifying interrupts not interrupt parents in the device tree? That's fine then. 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
