Since GPIOlib-based IRQ-chip interface is now utilized there is no need in
setting up a custom GPIO-to-IRQ mapping method. GPIO-lib defines the
standard mapping method - gpiochip_to_irq(), which will be used anyway no
matter whether the custom to_irq callback is specified or not.
Signed-off-by: Serge Semin <sergey.se...@baikalelectronics.ru>
Reviewed-by: Andy Shevchenko <andy.shevche...@gmail.com>
---
Changelog v2:
- This is a new patch detached from commit
"gpio: dwapb: Convert driver to using the GPIO-lib-based IRQ-chip".
---
drivers/gpio/gpio-dwapb.c | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/drivers/gpio/gpio-dwapb.c b/drivers/gpio/gpio-dwapb.c
index eb3a6da453ff..b6affe7161b0 100644
--- a/drivers/gpio/gpio-dwapb.c
+++ b/drivers/gpio/gpio-dwapb.c
@@ -154,14 +154,6 @@ static inline void dwapb_write(struct dwapb_gpio *gpio,
unsigned int offset,
gc->write_reg(reg_base + gpio_reg_convert(gpio, offset), val);
}
-static int dwapb_gpio_to_irq(struct gpio_chip *gc, unsigned offset)
-{
- struct dwapb_gpio_port *port = gpiochip_get_data(gc);
- struct dwapb_gpio *gpio = port->gpio;
-
- return irq_find_mapping(gpio->domain, offset);
-}
-
static struct dwapb_gpio_port *dwapb_offs_to_port(struct dwapb_gpio *gpio,
unsigned int offs)
{
struct dwapb_gpio_port *port;
@@ -476,8 +468,6 @@ static void dwapb_configure_irqs(struct dwapb_gpio *gpio,
girq->chip = &pirq->irqchip;
- port->gc.to_irq = dwapb_gpio_to_irq;
-
return;
err_kfree_pirq:
--
2.27.0
