* category than their parents, so it won't report false recursion.
         */
        irq_set_lockdep_class(irq, chip->lock_key);
-       irq_set_chip_and_handler(irq, chip->irq.chip, chip->irq_handler);
+       irq_set_chip_and_handler(irq, chip->irq.chip, chip->irq.handler);
        /* Chips that use nested thread handlers have them marked */
        if (chip->irq_nested)
                irq_set_nested_thread(irq, 1);
        }
 
        gpiochip->irq.chip = irqchip;
-       gpiochip->irq_handler = handler;
+       gpiochip->irq.handler = handler;
        gpiochip->irq_default_type = type;
        gpiochip->to_irq = gpiochip_to_irq;
        gpiochip->lock_key = lock_key;
 
         */
        const struct irq_domain_ops *domain_ops;
 
+       /**
+        * @handler:
+        *
+        * The IRQ handler to use (often a predefined IRQ core function) for
+        * GPIO IRQs, provided by GPIO driver.
+        */
+       irq_flow_handler_t handler;
+
        /**
         * @parent_handler:
         *
  *     safely.
  * @bgpio_dir: shadowed direction register for generic GPIO to clear/set
  *     direction safely.
- * @irq_handler: the irq handler to use (often a predefined irq core function)
- *     for GPIO IRQs, provided by GPIO driver
  * @irq_default_type: default IRQ triggering type applied during GPIO driver
  *     initialization, provided by GPIO driver
  * @irq_chained_parent: GPIO IRQ chip parent/bank linux irq number,
         * With CONFIG_GPIOLIB_IRQCHIP we get an irqchip inside the gpiolib
         * to handle IRQs for most practical cases.
         */
-       irq_flow_handler_t      irq_handler;
        unsigned int            irq_default_type;
        unsigned int            irq_chained_parent;
        bool                    irq_nested;