• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 759 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-L138 GPIO interrupt

A. Kirchhoff
Intellectual 535 points
Other Parts Discussed in Thread: OMAP-L138

I am developing code for the C674x DSP on the OMAP-L138.  I have setup GPIO bank 5 (event 59) to trigger HWI 4 using the BIOS dispatcher.  The interrupt fires just fine, but when I read the GPIO INTSTAT register for bank 5, I get all zeroes.  Did the dispatcher already clear the INTSTAT register for me?  How do I find out which pin on bank 5 triggered the interrupt?

Thanks,

abkirchhoff

  • 0
    TI__Guru*** 125430 points

    A. Kirchhoff said:
    The interrupt fires just fine, but when I read the GPIO INTSTAT register for bank 5, I get all zeroes. 

    Perhaps the ARM already got to it?

    Are you sure you're reading the correct register?  You should be reading the INTSTAT45 register at address 0x01E2 6084.

    A. Kirchhoff said:
    Did the dispatcher already clear the INTSTAT register for me?  How do I find out which pin on bank 5 triggered the interrupt?

    Definitely not.  BIOS knows nothing at all about the GPIO peripheral.

  • 0 in reply to Brad Griffis
    Intellectual 535 points

    Brad,

    Thanks for the reply.  I am looking at the correct register.  If BIOS is not to blame, I expect the problem is on the ARM.  I am running Embedded Linux on the ARM core and while I am not specifically using those pins, I expect that a interrupt handler is being setup for those pins.

     

    All,

    How do keep Linux from setting up or enabling an ISR for banks 4 and 5?

    abkirchhoff

  • 0 in reply to A. Kirchhoff
    TI__Guru*** 125430 points

    I was about to suggest posting to the Linux forum, but I see you already did!  Thanks.  :)  And it seems you figured out how to stop the ARM from servicing those interrupts!  Nice work!  :)