DSP:RegisterInterruptEvents: Difference between revisions

Ichfly (talk | contribs)
Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00150082] |- | 1 | param0 |- | 2 | param1 |- | 3 | 0? |- | 4 | eventhandle |} =R..."
 
Merry (talk | contribs)
mNo edit summary
 
(9 intermediate revisions by 7 users not shown)
Line 9: Line 9:
|-
|-
| 1
| 1
| param0
| Interrupt
|-
|-
| 2
| 2
| param1
| Channel
|-
|-
| 3
| 3
| 0?
| 0x0
|-
|-
| 4
| 4
| eventhandle
| Event handle (0 = unregister the event that was previous registered)
|}
|}
=Response=
=Response=
{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 27: Line 28:
|-
|-
| 0
| 0
| Header code
| Header code [0x00150040]
|-
|-
| 1
| 1
| Resultcode
| 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.