[PATCH 4/9] pinctrl: meson: allow gpio to request irq
From: Linus Walleij <hidden>
Date: 2016-10-25 09:14:42
Also in:
linux-amlogic, linux-devicetree, linux-gpio, lkml
From: Linus Walleij <hidden>
Date: 2016-10-25 09:14:42
Also in:
linux-amlogic, linux-devicetree, linux-gpio, lkml
On Fri, Oct 21, 2016 at 11:06 AM, Jerome Brunet [off-list ref] wrote:
quoted
Isn't this usecase (also as described in the cover letter) a textbook example of when you should be using hierarchical irqdomain? Please check with Marc et al on hierarchical irqdomains.Linus, Do you mean I should create a new hierarchical irqdomains in each of the two pinctrl instances we have in these SoC, these domains being stacked on the one I just added for controller in irqchip ? I did not understand this is what you meant when I asked you the question at ELCE.
Honestly, I do not understand when and where to properly use hierarchical irqdomain, even after Marc's talk at ELC-E. Which is problematic since quite a few GPIO drivers now need to use them. I will review his slides, in the meantime I would say: whatever Marc ACKs is fine with me. I trust this guy 100%. So I guess I could ask that he ACK the entire chain of patches from GIC->specialchip->GPIO. Yours, Linus Walleij