50
edits
Changes
mLine 9:
Line 9: − + − + − + − + + Line 27:
Line 28: − + + + + + + + +
no edit summary
|-
|-
| 1
| 1
| param0
| Interrupt
|-
|-
| 2
| 2
| param1
| Channel
|-
|-
| 3
| 3
| 0?
| 0x0
|-
|-
| 4
| 4
| Event Handle
| Event handle (0 = unregister the event that was previous registered)
|}
|}
=Response=
=Response=
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
| 0
| 0
| Header code
| Header code [0x00150040]
|-
|-
| 1
| 1
| Result code
| Result code
|}
|}
=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.