Lines Matching refs:be

21 address which causes an interrupt to be received by the CPU.
24 in PCI 3.0 to allow each interrupt to be masked individually.  The MSI-X
26 per device than MSI and allows interrupts to be independently configured.
28 Devices may support both MSI and MSI-X, but only one can be enabled at
48 arrive in memory before the value may be returned from the register.
57 to be specialised to a different purpose.  One possible design gives
73 To support MSI or MSI-X, the kernel must be built with the CONFIG_PCI_MSI
93 consequently, this function should be called before the driver calls
107 updates dev->irq to be the lowest of the new interrupts assigned to it.
117 This function should be called before the driver calls request_irq(),
122 there are many reasons why the platform may not be able to provide the
125 There could be devices that can not operate with just any number of MSI
140 the value of 0 would be meaningless and could result in error.
162 Note, unlike pci_enable_msi_exact() function, which could be also used to
170 enabling the single MSI mode for a device.  It could be done by passing
178 Note, unlike pci_enable_msi() function, which could be also used to
202 This function should be used to undo the effect of pci_enable_msi_range().
204 the previously allocated MSIs.  The interrupts may subsequently be assigned
216 This function could be used to retrieve the number of MSI vectors the
218 specification only allows the returned value to be a power of two,
225 number of MSI interrupt vectors that could be allocated.
230 It supports up to 2048 interrupts, each of which can be controlled
254 which should be at least 'maxvec' entries in size.
278 there are many reasons why the platform may not be able to provide the
281 There could be devices that can not operate with just any number of MSI-X
284 interrupts allocated should be a multiple of four.  In this case interface
285 pci_enable_msix_range() can not be used alone to request MSI-X interrupts
302 the value of 0 would be meaningless and could result in error.
326 Note, unlike pci_enable_msix_exact() function, which could be also used to
333 As noted above, there could be devices that can not operate with just any
356 	 * -ENOSPC is the only error code allowed to be analyzed
375 be retried.
415 	 * -ENOSPC is the only error code allowed to be analyzed
438 This function should be used to undo the effect of pci_enable_msix_range().
440 subsequently be assigned to another device, so drivers should not cache
452 be accessed directly by the device driver.  If the driver wishes to
459 This function could be used to retrieve number of entries in the device
466 number of MSI-X interrupt vectors that could be allocated.
479 to be a common operation but may be useful for debugging or testing
490 must be a power of two).  In addition, the MSI interrupt vectors must
491 be allocated consecutively, so the system might not be able to allocate
493 interrupts must all be targeted at the same set of CPUs whereas MSI-X
494 interrupts can all be targeted at different CPUs.
501 not be re-entered).  If a device uses multiple interrupts, the driver
504 acquire the spinlock.  Such deadlocks can be avoided by using
535 on the kernel command line to disable MSIs on all devices.  It would be
542 In this case, MSIs must be disabled on all devices behind the bridge.
557 To disable MSIs, echo 0 instead of 1.  Changing this value should be
570 it is not good practice, and should not be emulated.
575 why MSIs may not be enabled for a given device.  Your first step should
576 be to examine your dmesg carefully to determine whether MSIs are enabled
577 for your machine.  You should also check your .config to be sure you