Line 9: |
Line 9: |
| |- | | |- |
| | 1 | | | 1 |
− | | param0 | + | | Interrupt |
| |- | | |- |
| | 2 | | | 2 |
− | | param1 | + | | Channel |
| |- | | |- |
| | 3 | | | 3 |
− | | 0 | + | | 0x0 |
| |- | | |- |
| | 4 | | | 4 |
− | | Event handle, 0 for unregister the event that was previous registered | + | | Event handle (0 = unregister the event that was previous registered) |
| |} | | |} |
| | | |
Line 34: |
Line 34: |
| |} | | |} |
| | | |
− | Application should unregister the event by setting handle to zero, if the session was closed before the event is unregisterd, it will cause a handle leak in dsp process. | + | =Description= |
| + | Application should unregister the event by setting handle to zero. If the session was closed before the event was unregistered, it will cause a handle leak in DSP process. |
| + | |
| + | DSP can hold up to 6 concurrent registrations. More than that will cause registration to fail. |
| + | |
| + | Interrupts with interupt=2 are related to [[DSP:WriteProcessPipe|pipes]]. The channel argument is the same as the pipe channel argument. The interrupt is signalled when data is available on the related pipe or when a related event occurs. |