MAME Interrupt Function Review: Difference between revisions

From MAMEDEV Wiki
(New page: The following refers to the MAME core IRQ handling functions (eg. cpunum_set_input_line). ASSERT_LINE - raise the interrupt line and hold it there indefinitely CLEAR_LINE - lower the int...)
 
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The following refers to the MAME core IRQ handling functions (eg. cpunum_set_input_line).
The following refers to the MAME core IRQ handling functions (eg. cpunum_set_input_line).


ASSERT_LINE - raise the interrupt line and hold it there indefinitely
* '''ASSERT_LINE''' - raise the interrupt line and hold it there indefinitely
* '''CLEAR_LINE''' - lower the interrupt line and hold it there indefinitely
* '''PULSE_LINE''' - instantaneously do an ASSERT_LINE followed by a CLEAR_LINE
* '''HOLD_LINE''' - raise the interrupt line and hold it there until the interrupt is acknowledged by the CPU (note that this really only applies to those few CPUs with a full acknowledge cycles; the Z80 is the primary one -- all other uses are cheating)


CLEAR_LINE - lower the interrupt line and hold it there indefinitely
PULSE_LINE - instantaneously do an ASSERT_LINE followed by a CLEAR_LINE
HOLD_LINE - raise the interrupt line and hold it there until the interrupt is acknowledged by the CPU (note that this really only applies to those few CPUs with a full acknowledge cycles; the Z80 is the primary one -- all other uses are cheating)
On most CPUs, most interrupt lines are level-sensitive, which means that they will continue to generate interrupts as long as they are asserted. This generally means that you can't use PULSE_LINE because pulsing an interrupt line is instantaneous. In real life, the CPU would never respond to such a pulse because it is too short.
On most CPUs, most interrupt lines are level-sensitive, which means that they will continue to generate interrupts as long as they are asserted. This generally means that you can't use PULSE_LINE because pulsing an interrupt line is instantaneous. In real life, the CPU would never respond to such a pulse because it is too short.
   
   

Latest revision as of 04:59, 21 February 2007

The following refers to the MAME core IRQ handling functions (eg. cpunum_set_input_line).

  • ASSERT_LINE - raise the interrupt line and hold it there indefinitely
  • CLEAR_LINE - lower the interrupt line and hold it there indefinitely
  • PULSE_LINE - instantaneously do an ASSERT_LINE followed by a CLEAR_LINE
  • HOLD_LINE - raise the interrupt line and hold it there until the interrupt is acknowledged by the CPU (note that this really only applies to those few CPUs with a full acknowledge cycles; the Z80 is the primary one -- all other uses are cheating)

On most CPUs, most interrupt lines are level-sensitive, which means that they will continue to generate interrupts as long as they are asserted. This generally means that you can't use PULSE_LINE because pulsing an interrupt line is instantaneous. In real life, the CPU would never respond to such a pulse because it is too short.

Some CPUs have interrupt lines that are edge-sensitive, which means they will detect a state change from CLEAR_LINE to ASSERT_LINE and latch that information internally. Then they will take the interrupt and clear the latch. These are the only types of interrupts that can be used with PULSE_LINE.

Some CPUs let you program the interrupt lines to be either edge or level sensitive.

There may be helper functions in the future that allow the driver author to assert a line for a set period of time.