Switch from creating the IRQ domain mapping to finding it. In this case we know very well that the driver has created the apropriate mapping, we just need to locate it, no need to create any on-the-fly mappings.
Cc: Rob Herring <[email protected]> Cc: Grant Likely <[email protected]> Cc: Kuninori Morimoto <[email protected]> Signed-off-by: Linus Walleij <[email protected]> --- drivers/gpio/gpio-pcf857x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-pcf857x.c b/drivers/gpio/gpio-pcf857x.c index 16af35c..bf41cfc 100644 --- a/drivers/gpio/gpio-pcf857x.c +++ b/drivers/gpio/gpio-pcf857x.c @@ -164,7 +164,7 @@ static int pcf857x_to_irq(struct gpio_chip *chip, unsigned offset) { struct pcf857x *gpio = container_of(chip, struct pcf857x, chip); - return irq_create_mapping(gpio->irq_domain, offset); + return irq_find_mapping(gpio->irq_domain, offset); } static void pcf857x_irq_demux_work(struct work_struct *work) -- 1.7.11.7 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
