Lines Matching refs:it

43 it is possible that the interrupt may arrive before all the data has
75 and it may depend on some other options also being set.  For example,
104 If this function returns a positive number it indicates the number of
107 updates dev->irq to be the lowest of the new interrupts assigned to it.
113 If this function returns a negative number, it indicates an error and
153 interrupts it could request a particular number of interrupts by passing
190 If this function returns a negative number, it indicates an error and
203 Calling it restores dev->irq to the pin-based interrupt number and frees
208 on any interrupt for which it previously called request_irq().
221 If this function returns a negative number, it indicates the device is
224 If this function returns a positive number, it indicates the maximum
240 for example, it could use interrupts 3 and 1027 and yet allocate only a
243 should assign interrupts; it is invalid to fill in two entries with the
260 the driver should then call request_irq() for each 'vector' that it
262 interrupts assigned to the MSI-X vectors so it can free them again later.
266 If this function returns a negative number, it indicates an error and
283 four vectors per each queue it provides.  Therefore, a number of MSI-X
286 (since it can allocate any number within the range, without any notion of
316 interrupts it could request a particular number of interrupts by passing
385 If this function returns a negative number, it indicates an error and
444 on any interrupt for which it previously called request_irq().
453 mask or unmask an interrupt, it should call disable_irq() / enable_irq().
462 If this function returns a negative number, it indicates the device is
465 If this function returns a positive number, it indicates the maximum
470 If a device implements both MSI and MSI-X capabilities, it can
472 This is a requirement of the PCI spec, and it is enforced by the
476 and MSI-X at runtime, it must first quiesce the device, then switch
477 it back to pin-interrupt mode, before calling pci_enable_msi_range()
492 as many vectors for MSI as it could for MSI-X.  On some platforms, MSI
499 interrupt handler.  With pin-based interrupts or a single MSI, it is not
528 lucky, the manufacturer knows this and has indicated it in the ACPI
547 Linux mostly knows about them and automatically enables MSIs if it can.
558 done with caution as it could break interrupt handling for all devices
567 is handled in the individual device driver, but occasionally it's necessary
570 it is not good practice, and should not be emulated.
585 It is also worth checking the device driver to see whether it supports MSIs.
586 For example, it may contain calls to pci_enable_msi_range() or