| Message ID | 20180312164530.215524-1-djkurtz@chromium.org |
|---|---|
| State | New |
| Headers | show |
| Series | pinctrl/amd: poll InterruptEnable bits in enable_irq | expand |
On Mon, Mar 12, 2018 at 5:45 PM, Daniel Kurtz <djkurtz@chromium.org> wrote: > In certain cases interrupt enablement will be delayed relative to when > the InterruptEnable bits are written. One example of this is when > a GPIO's "debounce" logice is first enabled. After enabling debounce, > there is a 900 us "warm up" period during which InterruptEnable[0] > (bit 11) will read as 0 despite being written 1. During this time > InterruptSts will not be updated, nor will interrupts be delivered, even > if the GPIO's interrupt configuration has been written to the register. > > To work around this delay, poll the InterruptEnable bits after setting > them to ensure interrupts have truly been enabled in hardware before > returning from the irq_enable handler. > > Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> Patch applied. I see the AMD people were not on CC so adding them here so they can say if there is any problem with the approach. Daniel: maybe you should consider listing yourself as comaintainer of this driver? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi On 3/26/2018 2:42 PM, Linus Walleij wrote: > On Mon, Mar 12, 2018 at 5:45 PM, Daniel Kurtz <djkurtz@chromium.org> wrote: > >> In certain cases interrupt enablement will be delayed relative to when >> the InterruptEnable bits are written. One example of this is when >> a GPIO's "debounce" logice is first enabled. After enabling debounce, >> there is a 900 us "warm up" period during which InterruptEnable[0] >> (bit 11) will read as 0 despite being written 1. During this time >> InterruptSts will not be updated, nor will interrupts be delivered, even >> if the GPIO's interrupt configuration has been written to the register. >> >> To work around this delay, poll the InterruptEnable bits after setting >> them to ensure interrupts have truly been enabled in hardware before >> returning from the irq_enable handler. >> >> Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> > > Patch applied. > > I see the AMD people were not on CC so adding them here so they can > say if there is any problem with the approach. > > Daniel: maybe you should consider listing yourself as comaintainer of this > driver? > > Yours, > Linus Walleij > Looks good. Regards Nehal Shah -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/pinctrl/pinctrl-amd.c b/drivers/pinctrl/pinctrl-amd.c index dae184c4b962..af8ef485fbe7 100644 --- a/drivers/pinctrl/pinctrl-amd.c +++ b/drivers/pinctrl/pinctrl-amd.c @@ -348,12 +348,21 @@ static void amd_gpio_irq_enable(struct irq_data *d) unsigned long flags; struct gpio_chip *gc = irq_data_get_irq_chip_data(d); struct amd_gpio *gpio_dev = gpiochip_get_data(gc); + u32 mask = BIT(INTERRUPT_ENABLE_OFF) | BIT(INTERRUPT_MASK_OFF); raw_spin_lock_irqsave(&gpio_dev->lock, flags); pin_reg = readl(gpio_dev->base + (d->hwirq)*4); pin_reg |= BIT(INTERRUPT_ENABLE_OFF); pin_reg |= BIT(INTERRUPT_MASK_OFF); writel(pin_reg, gpio_dev->base + (d->hwirq)*4); + /* + * When debounce logic is enabled it takes ~900 us before interrupts + * can be enabled. During this "debounce warm up" period the + * "INTERRUPT_ENABLE" bit will read as 0. Poll the bit here until it + * reads back as 1, signaling that interrupts are now enabled. + */ + while ((readl(gpio_dev->base + (d->hwirq)*4) & mask) != mask) + continue; raw_spin_unlock_irqrestore(&gpio_dev->lock, flags); }
In certain cases interrupt enablement will be delayed relative to when the InterruptEnable bits are written. One example of this is when a GPIO's "debounce" logice is first enabled. After enabling debounce, there is a 900 us "warm up" period during which InterruptEnable[0] (bit 11) will read as 0 despite being written 1. During this time InterruptSts will not be updated, nor will interrupts be delivered, even if the GPIO's interrupt configuration has been written to the register. To work around this delay, poll the InterruptEnable bits after setting them to ensure interrupts have truly been enabled in hardware before returning from the irq_enable handler. Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> --- drivers/pinctrl/pinctrl-amd.c | 9 +++++++++ 1 file changed, 9 insertions(+)