• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 500 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP4460 GPIO_WK8 - Wake and interrupt functionality

Ryan Mazur
Prodigy 175 points

Can I use GPIO_WK_8 to wake the device from a standby state and also as a normal GPIO to act as an interrupt when the device is in normal operation?

I want to tie the INT output from a navigation button to GPIO_WK_8 but I am not sure if I should tie it to an additional GPIO for the interrupt capability.

Thanks,

Ryan

  • 0
    TI__Guru**** 161600 points

    Hello Ryan,

    It is ok to use GPIO_WK_8 to wake the device from standby/idle state. In addition GPIO_WK_8 has I/O capabilities and can be used as a direct wake-up path and as a normal GPIO.

    You shouldn't tie the INT output from the navigation button to an additional GPIO.  According to OMAP4 TRM asynchronous wake-up requests from input channels are merged to issue one wake-up signal to the system per each GPIO. When the system is awakened the interface clock is restarted and synchronously set to 1 based on the input GPIO pin triggering the wake-up request and the corresponding bit in the IRQ registers. IRQ lines (1 and 2) are active on the following internal clock cycle, when the corresponding bits in IRQ enable registers are set.

    For more information see 25.4.2 General-Purpose Interface Interrupt and Wake-Up Features in OMAP4 TRM.

    Best Regards,

    Yordan