Hi Joe,

I will push a patch to tf.org external gerrit for public review shortly. I appreciate your feedback.

Thanks, Madhukar ________________________________ From: Yang Joe magicse7en@outlook.com Sent: Thursday, July 31, 2025 9:14 PM To: Madhukar Pappireddy Madhukar.Pappireddy@arm.com; tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org Subject: Re: Does spmd_group0_interrupt_handler_nwd() need to take into account handling of special INTIDs?

Hi Madhukar,

May I ask if community will release an offical patch to handle the spurious ID (1023) ?

Thanks, Joe Yang ________________________________ From: Madhukar Pappireddy Madhukar.Pappireddy@arm.com Sent: Thursday, July 31, 2025 4:39 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org; YANG Jun magicse7en@outlook.com Subject: Re: Does spmd_group0_interrupt_handler_nwd() need to take into account handling of special INTIDs?

Hi Joe,

I believe we may have to account for special INTIDs. Do you see a spurious ID (1023) after acknowledging the highest pending interrupt?

Thanks, Madhukar ________________________________ From: YANG Jun via TF-A tf-a@lists.trustedfirmware.org Sent: Wednesday, July 30, 2025 7:18 AM To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org Subject: [TF-A] Does spmd_group0_interrupt_handler_nwd() need to take into account handling of special INTIDs?

Hi there,

Do spmd_group0_interrupt_handler_nwd() and spmd_handle_group0_intr_swd() need to take into account handling of special INTIDs? Like ehf_el3_interrupt_handler(): /* * Acknowledge interrupt. Proceed with handling only for valid interrupt * IDs. This situation may arise because of Interrupt Management * Framework identifying an EL3 interrupt, but before it's been * acknowledged here, the interrupt was either deasserted, or there was * a higher-priority interrupt of another type. */ intr_raw = plat_ic_acknowledge_interrupt(); intr = plat_ic_get_interrupt_id(intr_raw); if (intr == INTR_ID_UNAVAILABLE) return 0;

Best Regards, Joe Yang