raspberrypi
ISR versions of mutex_try_enter and mutex_exit
#1453 Extends mutex API to support holding the spin lock. This can be used to prevent deadlock from competing core.
Note this does cause possible priority inversion, if used incorrectly.
Does disabling interrupts on core 1, disable them on core 0? This patch does not cover the case of core 0 ISR and core 1 ISR racing against each other. In which case the patch is not worth much. (Even though this is horrible practice.) This would be new behavior and is capable of creating an issue like 1453. Perhaps documentation could describe the differences between the ISR and non ISR version and which is correct for certain contexts.
Note the ISR version is capable of creating a slight blocking behavior in non ISR version, which may need to be documented. I do not believe this diminishes this request, however does ask a larger question about the SDK.