Hello,
Our application is looking to implement the GateMP module for access to shared data across multiple processors. We've tested the API and while it does function properly at providing System wide access protection, we are concerned about the internal functionality of the GateMP_enter() API. From the IPC Users Guide:
"GateMP_enter() enters the caller's local gate. The local gate (if supplied) blocks if entered on the local processor. If entered by the remote processor, GateMP_enter() spins until the remote processor has left the gate."
GateMP_enter() seems to either spin or block internally without providing any sort of status or timeout on how long it takes to acquire a gate. So without some sort of external implementation we can theoretically be locked waiting for a Gate indefinitely. Are there any examples of a way to implement such a feature, or plans by Texas Instruments to add it to the API?
Thanks,
Ryan
