Lines Matching full:interrupt

8 ddi_add_intr, ddi_get_iblock_cookie, ddi_remove_intr \- hardware interrupt
43 interrupt interfaces referenced in \fBIntro\fR(9F). Refer to \fIWriting Device
64 Interrupt number.
73 Pointer to an interrupt block cookie.
94 Interrupt number.
103 Optional pointer to an interrupt block cookie where a returned interrupt block
113 Optional pointer to an interrupt device cookie where a returned interrupt
123 Pointer to interrupt handler.
132 Argument for interrupt handler.
153 Interrupt number.
162 Block cookie which identifies the interrupt handler to be removed.
169 \fBddi_get_iblock_cookie()\fR retrieves the interrupt block cookie associated
170 with a particular interrupt specification. This routine should be called before
171 \fBddi_add_intr()\fR to retrieve the interrupt block cookie needed to
172 initialize locks (\fBmutex\fR(9F), \fBrwlock\fR(9F)) used by the interrupt
173 routine. The interrupt number \fIinumber\fR determines for which interrupt
177 \fBdriver.conf\fR(4)). If only one interrupt is associated with the device,
182 initializing locks associated with the interrupt specification corresponding to
184 then initialize locks acquired by the interrupt routine before calling
186 driver's interrupt handler is called immediately \fBafter\fR the driver has
188 locks. This may happen when an interrupt for a different device occurs on the
189 same interrupt level. If the interrupt routine acquires the lock before the
194 \fBddi_add_intr()\fR adds an interrupt handler to the system. The interrupt
195 number \fIinumber\fR determines which interrupt the handler will be associated
200 initializing locks associated with this interrupt specification (see
201 \fBmutex_init\fR(9F) and \fBrw_init\fR(9F)). Note that the interrupt block
216 called upon receipt of the appropriate interrupt. The interrupt handler should
217 return \fBDDI_INTR_CLAIMED\fR if the interrupt was claimed,
221 If successful, \fBddi_add_intr()\fR returns \fBDDI_SUCCESS\fR. If the interrupt
224 sun4m architectures, if the interrupt information cannot be found,
229 \fBddi_remove_intr()\fR removes an interrupt handler from the system.
231 routine to remove their interrupt handler from the system.
234 The device interrupt routine for this instance of the device will not execute
236 for the device interrupt routine to complete before returning. Therefore, locks
237 acquired by the interrupt handler should not be held across the call to
243 high-interrupt context. These types include \fBISA\fR and SBus buses. See
264 On failure to find the interrupt.
273 On failure. \fBDDI_FAILURE\fR can also be returned on failure to find interrupt
312 interrupt handler for the interrupt specification corresponding to