Hi Thomas, 2016-01-29 5:06 GMT+09:00 Thomas Gleixner <tglx@xxxxxxxxxxxxx>: > On Thu, 28 Jan 2016, Rob Herring wrote: >> On Thu, Jan 28, 2016 at 5:49 AM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: >> > I've cc'ed the author and the device tree folks. Perhaps are they able to >> > explain what this commit tries to 'fix'. >> >> It's certainly not clear what driver was being fixed. I think the >> intention was to provide the trigger flags from the DT to drivers in a >> standard, non-DT specific way. The implementation of it certainly >> seems convoluted. The usecase I can think of is drivers may need the >> trigger information for cases where the device can support different >> trigger modes/polarity. The DT says which trigger mode to use and the >> device and irqchip need to be programmed to match. IIRC, SMSC ethernet >> chips frequently used on ARM boards do this. > > I can see that the driver wants this information, but why would one feed that > back into request_irq() when the interrupt was already configured by DT. > I think Rob already explained the original intention of the patch in question I sent quite long time ago. To clarify, I have to add that passing interrupt trigger in resource flags is not something specific for DT, but it is the general way used for platform devices and dating times even before DT adoption on ARM (=== wide spread DT adoption). The key point here is that on pre-DT systems, the interrupt would not be already configured by DT code and that's why you have to pass the trigger flags to request_irq(). Best regards, Tomasz -- 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
