SPRUIE9D May 2017 – May 2024 DRA74P , DRA75P , DRA76P , DRA77P
In phase A, only the synchronous path is enabled. A synchronous interrupt request (see Section 29.4.2.1, Synchronous Path: Interrupt Request Generation) activates the interrupt line(s) and prevents the GPIO from transitioning into IDLE state until the interrupt is cleared.
In phase B, the asynchronous path and synchronous path are enabled during the first five functional clock cycles of SLEEPTRANS state. During this period a synchronous interrupt request (see Section 29.4.2.1, Synchronous Path: Interrupt Request Generation) prevents the GPIO from transitioning into IDLE state. A shorter pulse puts the module into IDLE state but triggers a wakeup once in IDLE.
In phase C, only the asynchronous path is enabled. A wake-up request (see Section 29.4.2.2, Asynchronous Path: Wake-Up Request Generation) triggers a wake-up request from the GPIO and when the module is awakened an interrupt is generated. If debouncing is not enabled, there is no minimum input pulse width to trigger the wake-up request.
In phase D, eight open-core protocol (OCP) clock cycles occur until the module is in FUNCT state, the synchronous path is enabled, and an event that fulfills the pulse width requirements (see Section 29.4.2.1, Synchronous Path: Interrupt Request Generation) activates the interrupt line(s).
In phase E, only the synchronous path is enabled. A synchronous interrupt request (see Section 29.4.2.1, Synchronous Path: Interrupt Request Generation) activates the interrupt line(s).
Figure 29-11 shows the wake-up event conditions.
Figure 29-11 Wake-Up Event Conditions