KUserBindableInterruptEvent: Difference between revisions

mNo edit summary
No edit summary
Line 8: Line 8:
It appears that semaphores were originally planned to be bindable by svcBindInterrupt (except for the FIQ abstraction interrupt, SGI #15). The sole reason preventing semaphores to be used with svcBindInterrupt is a type check.
It appears that semaphores were originally planned to be bindable by svcBindInterrupt (except for the FIQ abstraction interrupt, SGI #15). The sole reason preventing semaphores to be used with svcBindInterrupt is a type check.


For public interrupts (i.e. anything else than SGI #15 in this case), svcBindInterrupts sets the flag that indicates that the interrupt shall be masked after each time the interrupt is received.
For public interrupts (i.e. anything else than SGI #15 in this case), svcBindInterrupts sets the flag that indicates that the interrupt shall be disabled after each time the interrupt is received.


The second virtual function unmasks the interrupt (using the interrupt ID) and signals the parent object. In the case of KSemaphoreInterruptEvent this also increment the parent semaphore's count.
The second virtual function reenables the interrupt (using the interrupt ID) and signals the parent object. In the case of KSemaphoreInterruptEvent this also increment the parent semaphore's count.


{| class="wikitable" border="1"
{| class="wikitable" border="1"