Re: [PATCH v5] nfc: nxp-nci: i2c: use rising-edge IRQ on ACPI systems

[Bartosz Golaszewski]

On Tue, May 19, 2026 at 11:47 AM Carl Lee via B4 Relay
<devnull+carl.lee.amd.com@xxxxxxxxxx> wrote:
>
> From: Carl Lee <carl.lee@xxxxxxx>
>
> Some ACPI-based platforms report incorrect IRQ trigger types (e.g.
> IRQF_TRIGGER_HIGH), which can lead to interrupt storms.
>
> Use the historically working rising-edge trigger on ACPI systems to
> avoid this regression.
>
> Device Tree-based systems continue to use the firmware-provided
> trigger type.
>
> Fixes: 57be33f85e36 ("nfc: nxp-nci: remove interrupt trigger type")
> Cc: stable@xxxxxxxxxxxxxxx
>
> Tested-by: Luca Stefani <luca.stefani.ge1@xxxxxxxxx>
> Tested-by: Mark Pearson <mpearson-lenovo@xxxxxxxxx>
> Tested-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxxxxxxxx>
> Reviewed-by: Mark Pearson <mpearson-lenovo@xxxxxxxxx>
> Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxxxxxxxx>
> Signed-off-by: Carl Lee <carl.lee@xxxxxxx>
> ---
> Some ACPI-based platforms report incorrect IRQ trigger types,
> which can lead to interrupt storms.
>
> Use rising-edge IRQ on ACPI systems to avoid this regression,
> while keeping firmware-provided trigger types on non-ACPI systems.
> ---

Hi!

Can this be queued yet? The problem is still present in stable branches.

Bart