Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 23 Apr 2014 09:31 AM by  Jason Krasnow
Stop omap3_l3_app_irq 10 fired and nobody cared
 0 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Jason Krasnow
New Member
New Member
Posts:5


--
23 Apr 2014 09:31 AM
    Product    
    DM3730 SOM-LV  (SOMDM3730-10-1782JFIR-B)
    Software OS    
    Linux
    Part Number    
    1022070

    Description  

     During USB teardown after powering down a USB device sometimes the Linux kernel will spit out:

    irq 10 nobody cared

    handlers:

    [] omap3_l3_app_irq

    Disabling IRQ 10

     

    It seems this IRQ fires on an OMAP peripheral error and the correct action the Linux driver takes is to determine the peripheral and clear the status thus clearing the interrupt.  During USB stack teardown it sometimes occurs with the status when reading the L3_SI_FLAG_STATUS_0 a value of 0x20000000.  From the way the 64 bit register  is accessed it appears this is bit 29 which is a reserved bit in the register.  Because of this the IRQ source cannot be cleared and it keeps firing until the Linux kernel decides that the IRQ needs to be turned off.  Bit 29 is right after a few bits relating to USB Host IA peripheral. 

    Question:  

    I am assuming in some TI documentation somewhere this Bit actually means something and may point to a USB Host peripheral of some type.  I would like to know what that is so the driver can be modified to stop the IRQ at the source and handle any necessary actions that need to take place on this error.  Thanks.

    You are not authorized to post a reply.