My customer has the following issue by using the NDK in OMAPL138.
From the call tree of our NDK (see table below) we can see that at the end MDIO_timerTick is invoked. Customer is having some issue if the link is not available and this will generate a long wait (in the range of 3 msec up).
STACK | NIMU | ETHDRV | CSL OMAPL138 |
NetScheduler |
|
|
|
EmacPoll |
|
| |
| _HwPktPoll |
| |
|
| llEnter |
|
|
| disableInterrupts |
|
|
| MDIO_timerTick | |
|
| restoreInterrupts |
|
|
| llExit |
|
NIMU = NETWORK INTERFACE MANAGEMENT UNIT
ETHDRV = ETHERNET DRIVER
CSL OMAPL138 = CHIP SUPPORT LIBRARY PER OMAPL138
**************************
It seems that this is related to the MDIO_timerTick that sounds as blocker and the interrupt disabled: since they have an application task running @ 5msec, this long delay is introducing some problem.
Why are we disabling the interrupt? Is there any other driver they can use?
How can they skip this problem?
Thanks
Silvio