[PATCH 4/9] pinctrl: meson: allow gpio to request irq
marc.zyngier at arm.com
Tue Oct 25 06:38:11 PDT 2016
On 25/10/16 14:08, Jerome Brunet wrote:
> On Tue, 2016-10-25 at 11:38 +0100, Marc Zyngier wrote:
>> On 25/10/16 10:14, Linus Walleij wrote:
>>> On Fri, Oct 21, 2016 at 11:06 AM, Jerome Brunet <jbrunet at baylibre.c
>>> om> wrote:
>>>>> Isn't this usecase (also as described in the cover letter) a
>>>>> example of when you should be using hierarchical irqdomain?
>>>>> Please check with Marc et al on hierarchical irqdomains.
>>>> Do you mean I should create a new hierarchical irqdomains in each
>>>> the two pinctrl instances we have in these SoC, these domains
>>>> 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.
>> I probably didn't do that good a job explaining it then. Let's try
>> again. You want to use hierarchical domains when you want to describe
>> interrupt whose path traverses multiple controllers without ever
>> multiplexed with other signals. As long as you have this 1:1
>> relationship between controllers, you can use them.
> Linus, Marc,
> The calculation is question here is meant to get the appropriate hwirq
> number from a particular gpio (and deal with the gpios that can't
> provide an irq at all).
> If I look at other gpio drivers, many are doing exactly this kind of
> calculation before calling 'irq_create_mapping' in the to_irq callback.
> For example:
> - pinctrl/nomadik/pinctrl-abx500.c
> - pinctrl/samsung/pinctrl-exynos5440.c
> Some can afford to create all the mappings in the probe and just call
> 'irq_find_mapping' (gpio/gpio_tegra.c) but this would not work here. We
> have only 8 upstream irqs for 130+ pins, so only 8 mappings possible at
> a time.
> My understanding is that irqdomain provide a way to map hwirq to linux
> virq (and back), not map gpio number to hwirq, right?
But why are those number different? Why don't you use the same
namespace? If gpio == hwirq, all your problems are already solved. If
you don't find the mapping in the irqdomain, then there is no irq, end
of story. What am I missing?
> Even if I implement an another irqdomain at the gpio level, I would
> still have to perform this kind of calculation, one way or the other.
>>> 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.
> Actually this discussion go me thinking about another issue we have
> with this hardware.
> We are looking for a way to implement support for IRQ_TYPE_EDGE_BOTH
> (needed for things like gpio-keys or mmc card detect).
> The controller can do each edge but not both at the same time.
> I'm thinking that implementing another irqdomain at the gpio level
> would allow to properly check the pad level in the EOI callback then
> set the next expected edge type accordingly (using
> Would it be acceptable ?
I really don't see what another irqdomain brings to the table. This is
not a separate piece of HW, so the hwirq:irq mapping is still the same.
I fail to see what the benefit is.
> It looks a few other drivers deal with IRQ_TYPE_EDGE_BOTH in a similar
> way (gpio/gpio-omap.c, gpio/gpio-dwapb.c)
Being already done doesn't make it reliable. If the line goes low
between latching the rising edge and reprogramming the trigger, you've
lost at least *two* interrupts (the falling edge and the following
Jazz is not dead. It just smells funny...
More information about the linux-amlogic