Lines Matching refs:this

10 1. About this guide
38 To support this, the kernel must call each interrupt handler associated
40 a whole.  MSIs are never shared, so this problem cannot arise.
44 arrived in memory (this becomes more likely with devices behind PCI-PCI
49 Using MSIs avoids this problem as the interrupt-generating write cannot
82 has to request that the PCI layer set up the MSI capability for this
93 consequently, this function should be called before the driver calls
104 If this function returns a positive number it indicates the number of
105 MSI interrupts that have been successfully allocated.  In this case
113 If this function returns a negative number, it indicates an error and
115 this device.
143 In this case the function could look like this:
190 If this function returns a negative number, it indicates an error and
192 this device.
207 Before calling this function, a device driver must always call free_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
231 independently.  To support this flexibility, drivers must use an array of
251 Calling this function asks the PCI subsystem to allocate any number of
258 allocated.  In this case the 'vector' member in entries numbered from
266 If this function returns a negative number, it indicates an error and
268 this device.
271 dev->irq.  The device will not generate interrupts for this interrupt
274 Device drivers should normally call this function once per device
284 interrupts allocated should be a multiple of four.  In this case interface
305 In this case the function could look like this:
336 two.  A routine that enables MSI-X mode for such device might look like this:
385 If this function returns a negative number, it indicates an error and
387 this device.
394 specific requirements described in chapter 4.3.1.3 might look like this:
443 Before calling this function, a device driver must always call free_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
528 lucky, the manufacturer knows this and has indicated it in the ACPI
529 FADT table.  In this case, Linux automatically disables MSIs.
530 Some boards don't include this information in the table and so we have
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
559 below this bridge.
566 Some devices are known to have faulty MSI implementations.  Usually this
568 to handle this with a quirk.  Some drivers have an option to disable use
569 of MSI.  While this is a convenient workaround for the driver author,