Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34;
From:   Biju Das <biju.das.jz@bp.renesas.com>
To:     Thomas Gleixner <tglx@linutronix.de>, Marc Zyngier <maz@kernel.org>
Cc:     Biju Das <biju.das.jz@bp.renesas.com>,
        Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
        Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
        Geert Uytterhoeven <geert+renesas@glider.be>,
        Biju Das <biju.das.au@gmail.com>, linux-kernel@vger.kernel.org,
        linux-renesas-soc@vger.kernel.org
Subject: [PATCH 0/3] Fix IRQ storm with GPIO interrupts
Date:   Mon, 18 Sep 2023 13:24:08 +0100
Message-Id: <20230918122411.237635-1-biju.das.jz@bp.renesas.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

The following issues observed while adding IRQ support for RTC.
 * The irq_disable is not clearing interrupt source properly.
 * The driver is not following as per hardware manual for changing
   interrupt settings.
 * IRQ storm due to phantum interrupt, when we select the TINT source.
   Here IRQ handler disables  the interrupts using disable_irq_nosync()
   and scheduling a work queue and in the work queue, re-enabling the
   interrupt with enable_irq().

Biju Das (3):
  irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source
  irqchip: renesas-rzg2l: Mask interrupts for changing interrupt
    settings
  irqchip: renesas-rzg2l: Fix irq storm with edge trigger detection for
    TINT

 drivers/irqchip/irq-renesas-rzg2l.c | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

-- 
2.25.1