aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/PCI/MSI-HOWTO.txt
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-07-14 17:54:18 -0400
committerMichael Witten <mfwitten@gmail.com>2011-08-02 17:34:35 -0400
commit6457d9b350b3f4f2098984eee016c6c994b9c096 (patch)
tree9a3674624e313162c44eab3d4f55a15bf8df3bfb /Documentation/PCI/MSI-HOWTO.txt
parented737c1882c652f0b5a888df59895b5dc2d10cd7 (diff)
Docs: MSI-HOWTO: Move a sentence to another paragraph
Signed-off-by: Michael Witten <mfwitten@gmail.com> Acked-by: Matthew Wilcox <matthew.r.wilcox@intel.com> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Diffstat (limited to 'Documentation/PCI/MSI-HOWTO.txt')
-rw-r--r--Documentation/PCI/MSI-HOWTO.txt7
1 files changed, 3 insertions, 4 deletions
diff --git a/Documentation/PCI/MSI-HOWTO.txt b/Documentation/PCI/MSI-HOWTO.txt
index c504f12bcc61..28d1ceeea655 100644
--- a/Documentation/PCI/MSI-HOWTO.txt
+++ b/Documentation/PCI/MSI-HOWTO.txt
@@ -171,7 +171,8 @@ which should be at least 'nvec' entries in size. On success, the
171device is switched into MSI-X mode and the function returns 0. 171device is switched into MSI-X mode and the function returns 0.
172The 'vector' member in each entry is populated with the interrupt number; 172The 'vector' member in each entry is populated with the interrupt number;
173the driver should then call request_irq() for each 'vector' that it 173the driver should then call request_irq() for each 'vector' that it
174decides to use. 174decides to use. The device driver is responsible for keeping track of the
175interrupts assigned to the MSI-X vectors so it can free them again later.
175 176
176If this function returns a negative number, it indicates an error and 177If this function returns a negative number, it indicates an error and
177the driver should not attempt to allocate any more MSI-X interrupts for 178the driver should not attempt to allocate any more MSI-X interrupts for
@@ -181,9 +182,7 @@ below.
181 182
182This function, in contrast with pci_enable_msi(), does not adjust 183This function, in contrast with pci_enable_msi(), does not adjust
183dev->irq. The device will not generate interrupts for this interrupt 184dev->irq. The device will not generate interrupts for this interrupt
184number once MSI-X is enabled. The device driver is responsible for 185number once MSI-X is enabled.
185keeping track of the interrupts assigned to the MSI-X vectors so it can
186free them again later.
187 186
188Device drivers should normally call this function once per device 187Device drivers should normally call this function once per device
189during the initialization phase. 188during the initialization phase.