Lines Matching full:interrupt
84 * modified while being used by the actual interrupt dispatch code; see
91 * dmv_add_intr is called to add a databearing mondo interrupt handler
95 * Note that if a processor receives a databearing mondo interrupt
103 * dmv_inum interrupt number for the device.
105 * routine pointer to the device's vectored interrupt
146 * 6. The handler may read the Incoming Interrupt Vector Data
147 * registers, and the Interrupt Vector Receive register, but
173 * interrupt routine in order to do further processing at normal
174 * interrupt level. It is strongly advised that drivers do
177 * soft interrupt routine. (This is analogous to the DDI
178 * "high-level interrupt" concept, although a databearing mondo
180 * a high-level interrupt routine.)
182 * Soft interrupt routines should be registered by calling
183 * add_softintr(), which will return an interrupt number. This
184 * interrupt number should be saved in a driver-private data
188 * whether a soft interrupt routine will be called, as follows:
190 * If %g1 is less than zero, no interrupt will be queued.
192 * Otherwise, %g1 is assumed to be an interrupt number
193 * obtained from add_softintr. This interrupt routine
223 * dmv_add_softintr is called to add a databearing mondo interrupt
227 * routine pointer to the device's vectored interrupt
265 * dmv_rem_intr is called to remove a databearing interrupt handler
269 * dmv_inum interrupt number for the device.