mbox series

[v1,0/2] gpio: mlxbf2: Introduce proper interrupt handling

Message ID 20210915222847.10239-1-asmaa@nvidia.com
Headers show
Series gpio: mlxbf2: Introduce proper interrupt handling | expand

Message

Asmaa Mnebhi Sept. 15, 2021, 10:28 p.m. UTC
This is a follow up on a discussion regarding
proper handling of GPIO interrupts within the
gpio-mlxbf2.c driver.

Link to discussion:
https://lore.kernel.org/netdev/20210816115953.72533-7-andriy.shevchenko@linux.intel.com/T/

Patch 1 adds support to a GPIO IRQ handler in gpio-mlxbf2.c.
Patch 2 is a follow up removal of custom GPIO IRQ handling
from the mlxbf_gige driver and replacing it with a simple
IRQ request. The ACPI table for the mlxbf_gige driver is
responsible for instantiating the PHY GPIO interrupt via
GpioInt.

Andy Shevchenko, could you please review this patch series.
David Miller, could you please ack the changes in the
mlxbf_gige driver.

Asmaa Mnebhi (2):
  gpio: mlxbf2: Introduce IRQ support
  net: mellanox: mlxbf_gige: Replace non-standard interrupt handling

 drivers/gpio/gpio-mlxbf2.c                    | 181 ++++++++++++++-
 .../net/ethernet/mellanox/mlxbf_gige/Makefile |   1 -
 .../ethernet/mellanox/mlxbf_gige/mlxbf_gige.h |  12 -
 .../mellanox/mlxbf_gige/mlxbf_gige_gpio.c     | 212 ------------------
 .../mellanox/mlxbf_gige/mlxbf_gige_main.c     |  22 +-
 5 files changed, 188 insertions(+), 240 deletions(-)
 delete mode 100644 drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_gpio.c

Comments

Andrew Lunn Sept. 16, 2021, 2:05 p.m. UTC | #1
> +static void mlxbf2_gpio_irq_enable(struct irq_data *irqd)

> +{

> +	struct gpio_chip *gc = irq_data_get_irq_chip_data(irqd);

> +	struct mlxbf2_gpio_context *gs = gpiochip_get_data(gc);

> +	int offset = irqd_to_hwirq(irqd);

> +	unsigned long flags;

> +	u32 val;

> +

> +	spin_lock_irqsave(&gs->gc.bgpio_lock, flags);

> +	val = readl(gs->gpio_io + YU_GPIO_CAUSE_OR_CLRCAUSE);

> +	val |= BIT(offset);

> +	writel(val, gs->gpio_io + YU_GPIO_CAUSE_OR_CLRCAUSE);

> +

> +	/* Enable PHY interrupt by setting the priority level */


This should be an abstract driver for a collection of GPIO lines.
Yes, one of these GPIOs is used for the PHY, but the GPIO driver does
not care. So please remove this comment.

> +	val = readl(gs->gpio_io + YU_GPIO_CAUSE_OR_EVTEN0);

> +	val |= BIT(offset);

> +	writel(val, gs->gpio_io + YU_GPIO_CAUSE_OR_EVTEN0);


What exactly does this do? It appears to clear the interrupt, if i
understand mlxbf2_gpio_irq_handler(). I don't know the GPIO framework
well enough to know if this is correct. It does mean if the interrupt
signal is active but masked, and you enable it, you appear to loose
the interrupt? Maybe you want the interrupt to fire as soon as it is
enabled?

> +static irqreturn_t mlxbf2_gpio_irq_handler(int irq, void *ptr)

> +{

> +	struct mlxbf2_gpio_context *gs = ptr;

> +	struct gpio_chip *gc = &gs->gc;

> +	unsigned long pending;

> +	u32 level;

> +

> +	pending = readl(gs->gpio_io + YU_GPIO_CAUSE_OR_CAUSE_EVTEN0);

> +	writel(pending, gs->gpio_io + YU_GPIO_CAUSE_OR_CLRCAUSE);

> +

> +	for_each_set_bit(level, &pending, gc->ngpio) {

> +		int gpio_irq = irq_find_mapping(gc->irq.domain, level);

> +		generic_handle_irq(gpio_irq);

> +	}

> +

> +	return IRQ_RETVAL(pending);

> +}

> +

> +static void mlxbf2_gpio_irq_mask(struct irq_data *irqd) {

> +	mlxbf2_gpio_irq_disable(irqd);

> +}

> +

> +static void mlxbf2_gpio_irq_unmask(struct irq_data *irqd) {

> +	mlxbf2_gpio_irq_enable(irqd);

> +}


Do these two functions have any value?

> +static int

> +mlxbf2_gpio_irq_set_type(struct irq_data *irqd, unsigned int type)

> +{

> +	struct gpio_chip *gc = irq_data_get_irq_chip_data(irqd);

> +	struct mlxbf2_gpio_context *gs = gpiochip_get_data(gc);

> +	int offset = irqd_to_hwirq(irqd);

> +	unsigned long flags;

> +	bool fall = false;

> +	bool rise = false;

> +	u32 val;

> +

> +	switch (type & IRQ_TYPE_SENSE_MASK) {

> +	case IRQ_TYPE_EDGE_BOTH:

> +	case IRQ_TYPE_LEVEL_MASK:

> +		fall = true;

> +		rise = true;

> +		break;

> +	case IRQ_TYPE_EDGE_RISING:

> +	case IRQ_TYPE_LEVEL_HIGH:

> +		rise = true;

> +		break;

> +	case IRQ_TYPE_EDGE_FALLING:

> +	case IRQ_TYPE_LEVEL_LOW:

> +		fall = true;

> +		break;


This looks wrong. You cannot map a level interrupt into an edge. It
looks like your hardware only supports edges. If asked to do level,
return -EINVAL.

> +	default:

> +		break;

> +	}

> +

> +	/* The INT_N interrupt level is active low.

> +	 * So enable cause fall bit to detect when GPIO

> +	 * state goes low.

> +	 */


I don't understand this comment.

  Andrew