• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 1092 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.

OMAP 4430 + GPIO_0 and GPIO_WK0

1258021
Genius 5120 points

Hi,

Processor: OMAP4430

Thank You for reading the post.

We have an external peripheral its IRQ is connected to GPIO_0.  Similarly we have a push button and it is also connected to GPIO_WK0 signal.

When the system is active, is it possible to configures OMAP4430 to receive the Interrupt from external peripheral and also from the push button simultaneously.

Also how the system software can differentiate between IRQ from external peripheral and push button press event. Or it is not possible to differentiate them?

Regards,

GSR

  • 0
    Intellectual 270 points

    Hi GSR,

    I talked to my co-worker for clarification on this issue. GPIO_0 and GPIO_WK0 are really the same GPIO.  The GPIO_WK0 can be used to wake up the system from suspend mode.

    In the longer term, I think it would be preferable to move one of the two signals onto a different GPIO.

    In the short term, you could modify the device driver for your external peripheral to also deal with button presses.  So when servicing the interrupt, it is common to check and/or clear the interrupt flag in the peripheral itself.  If you modify the code to check to see if the flag is set, then you can detect cases where the interrupt was generated by the peripheral.  If the flag was not set, then generate an input event (similar to what the gpio-keys driver does) because it was apparently a button press.

    Best regards,

    James