[lkml]   [2014]   [Apr]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/3] gpio: dwapb: do not create the irq mapping upfront.
On Tue, Mar 25, 2014 at 10:17 PM, Sebastian Andrzej Siewior
<> wrote:
> * Linus Walleij | 2014-03-25 21:43:49 [+0100]:
>>> I looked at
>>> those two links and you quote gpio_to_irq() which is not required.
>>In a *lot* of drivers it is implicitly required that gpio_to_irq()
>>is called first because they only call irq_create_mapping()
>>there. (And not in subsequent interrupt handlers etc.)
> so
> --- a/drivers/gpio/gpio-dwapb.c
> +++ b/drivers/gpio/gpio-dwapb.c
> @@ -68,7 +68,7 @@ static int dwapb_gpio_to_irq(struct gpio_chip *gc, unsigned offset)
> dwapb_gpio_port, bgc);
> struct dwapb_gpio *gpio = port->gpio;
> - return irq_find_mapping(gpio->domain, offset);
> + return irq_create_mapping(gpio->domain, offset);
> }
> static void dwapb_toggle_trigger(struct dwapb_gpio *gpio, unsigned int offs)
> would fix the problem then.


This only gets called if some GPIO consumer decides to call
gpio_to_irq() to find out the interrupt number before using the

There is no requirement that consumers do that!

It is perfectly legal for a GPIO irq comsumer to just use
some hard-coded IRQ number from a board file or similar,
or to just use an IRQ from a DT or ACPI entity without any
such translation.

So the mappings must be created in probe().

Linus Walleij

 \ /
  Last update: 2014-04-08 16:21    [W:0.061 / U:0.940 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site