How should I choose between TSK mode or SWI mode in the –DspTskMode option when I am trying to configure DSPLink?
A command line option is provided in dsplinkcfg.pl static configuration script to enable TSK mode instead SWI mode. To enable TSK mode, pass –DspTskMode = 1 option to dsplinkcfg.pl script during DSPLink build configuration. This is an optional argument. If not provided, the current default of DSP SWI mode is assumed. Whenever any of our modules use MPCS for multi-processor protection of shared structures, SWI_disable is called on the DSP-side to protect locally i.e. no other tasks or SWI’s are allowed to execute, and scheduler was disabled. While this would give better performance for DSPLink APIs (since you are making sure it runs to completion), it holds up any other tasks or SWI’s that may want to execute even non DSPLink work, till the MPCS lock is released. Also, the time for which the DSP keeps spinning to get the lock with scheduler disabled can become high if the ARM thread has taken the lock and got preempted. MSGQ and CHNL modules drivers on the DSP-side also used SWI’s for d
