lkml.org 
[lkml]   [2020]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.19 104/125] irqchip/stm32-exti: Avoid losing interrupts due to clearing pending bits by mistake
    Date
    From: qiuguorui1 <qiuguorui1@huawei.com>

    commit e579076ac0a3bebb440fab101aef3c42c9f4c709 upstream.

    In the current code, when the eoi callback of the exti clears the pending
    bit of the current interrupt, it will first read the values of fpr and
    rpr, then logically OR the corresponding bit of the interrupt number,
    and finally write back to fpr and rpr.

    We found through experiments that if two exti interrupts,
    we call them int1/int2, arrive almost at the same time. in our scenario,
    the time difference is 30 microseconds, assuming int1 is triggered first.

    there will be an extreme scenario: both int's pending bit are set to 1,
    the irq handle of int1 is executed first, and eoi handle is then executed,
    at this moment, all pending bits are cleared, but the int 2 has not
    finally been reported to the cpu yet, which eventually lost int2.

    According to stm32's TRM description about rpr and fpr: Writing a 1 to this
    bit will trigger a rising edge event on event x, Writing 0 has no
    effect.

    Therefore, when clearing the pending bit, we only need to clear the
    pending bit of the irq.

    Fixes: 927abfc4461e7 ("irqchip/stm32: Add stm32mp1 support with hierarchy domain")
    Signed-off-by: qiuguorui1 <qiuguorui1@huawei.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Cc: stable@vger.kernel.org # v4.18+
    Link: https://lore.kernel.org/r/20200820031629.15582-1-qiuguorui1@huawei.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    drivers/irqchip/irq-stm32-exti.c | 14 ++++++++++++--
    1 file changed, 12 insertions(+), 2 deletions(-)

    --- a/drivers/irqchip/irq-stm32-exti.c
    +++ b/drivers/irqchip/irq-stm32-exti.c
    @@ -382,6 +382,16 @@ static void stm32_irq_ack(struct irq_dat
    irq_gc_unlock(gc);
    }

    +/* directly set the target bit without reading first. */
    +static inline void stm32_exti_write_bit(struct irq_data *d, u32 reg)
    +{
    + struct stm32_exti_chip_data *chip_data = irq_data_get_irq_chip_data(d);
    + void __iomem *base = chip_data->host_data->base;
    + u32 val = BIT(d->hwirq % IRQS_PER_BANK);
    +
    + writel_relaxed(val, base + reg);
    +}
    +
    static inline u32 stm32_exti_set_bit(struct irq_data *d, u32 reg)
    {
    struct stm32_exti_chip_data *chip_data = irq_data_get_irq_chip_data(d);
    @@ -415,9 +425,9 @@ static void stm32_exti_h_eoi(struct irq_

    raw_spin_lock(&chip_data->rlock);

    - stm32_exti_set_bit(d, stm32_bank->rpr_ofst);
    + stm32_exti_write_bit(d, stm32_bank->rpr_ofst);
    if (stm32_bank->fpr_ofst != UNDEF_REG)
    - stm32_exti_set_bit(d, stm32_bank->fpr_ofst);
    + stm32_exti_write_bit(d, stm32_bank->fpr_ofst);

    raw_spin_unlock(&chip_data->rlock);


    \
     
     \ /
      Last update: 2020-09-01 18:53    [W:4.103 / U:0.240 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site