Sometimes TXRX_PRINT is taking more time to process as some other printks' are already in progress. As this TXRX_PRINT is inside spinlock, so when some other core is also competing for this spinlock, that core keeps iterating in a loop. After some time spinlock bug is triggered as it is suspected that this core is locked on this spinlock. To fix this, move the TXRX_PRINT outside spinlock so that the other core don't have to wait to acquire spinlock due to this TXRX_PRINT. CRs-Fixed: 1107213 Change-Id: Ie6f8a7c8f9731883c2440641b8b9542f9d40c4a9 |
||
---|---|---|
.. | ||
htt | ||
ol/inc | ||
txrx |