Lines Matching full:interrupt
121 The device driver participates in interrupt resource management. The device
122 driver may receive additional interrupt resources from the system, but only
125 attached. Interrupt availability varies based on the overall needs of the
159 For interrupt resource management, the driver has more available interrupts.
160 The driver can allocate more interrupt vectors and then set up more interrupt
170 For interrupt resource management, the driver has fewer available interrupts.
189 If a driver participates in interrupt resource management, it must register a
192 interrupt availability has changed. The callback handler should use the
193 interrupt functions \fBddi_intr_alloc\fR(9F) and \fBddi_intr_free\fR(9F)
263 These functions can be called from kernel, non-interrupt context.
274 * hardware, and sets up interrupt handling for the driver.
313 /* Select interrupt type */
328 /* Allocate interrupt handle array */
332 /* Allocate interrupt setup array */
336 /* Allocate interrupt vectors */
340 /* Configure interrupt handling */
343 /* Install and enable interrupt handlers */
373 * Stops the hardware, disables interrupt handling, unregisters
407 /* Free interrupt handle array */
410 /* Free interrupt setup array */
437 * Adapt interrupt usage when availability changes.
458 /* Tear down previous interrupt handling */
464 /* Adjust interrupt vector allocations */
467 /* Allocate additional interrupt vectors */
476 /* Free removed interrupt vectors */
486 /* Configure interrupt handling */
489 /* Install and enable interrupt handlers */
539 participants in interrupt resource management. With that participation comes a
540 responsibility to properly adjust interrupt usage. In the case of a
542 a total number of interrupt resources up to its new number of available
543 interrupts. The total number of interrupt resources is the sum of all resources
549 interrupt availability for other drivers in the system.
565 Participation in interrupt resource management ends when a driver uses the