[PATCH] irq-flags: documentation: Use the new IRQF_ constants

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

authored by Thomas Gleixner and committed by Linus Torvalds 6ce6c7fa 65ca68b3

+6 -6
+1 -1
Documentation/DocBook/videobook.tmpl
··· 976 <title>Interrupt Handling</title> 977 <para> 978 Our example handler is for an ISA bus device. If it was PCI you would be 979 - able to share the interrupt and would have set SA_SHIRQ to indicate a 980 shared IRQ. We pass the device pointer as the interrupt routine argument. We 981 don't need to since we only support one card but doing this will make it 982 easier to upgrade the driver for multiple devices in the future.
··· 976 <title>Interrupt Handling</title> 977 <para> 978 Our example handler is for an ISA bus device. If it was PCI you would be 979 + able to share the interrupt and would have set IRQF_SHARED to indicate a 980 shared IRQ. We pass the device pointer as the interrupt routine argument. We 981 don't need to since we only support one card but doing this will make it 982 easier to upgrade the driver for multiple devices in the future.
+1 -1
Documentation/pci.txt
··· 225 Use these for address resources that are not described by "normal" PCI 226 interfaces (e.g. BAR). 227 228 - All interrupt handlers should be registered with SA_SHIRQ and use the devid 229 to map IRQs to devices (remember that all PCI interrupts are shared). 230 231
··· 225 Use these for address resources that are not described by "normal" PCI 226 interfaces (e.g. BAR). 227 228 + All interrupt handlers should be registered with IRQF_SHARED and use the devid 229 to map IRQs to devices (remember that all PCI interrupts are shared). 230 231
+1 -1
Documentation/scsi/tmscsim.txt
··· 109 110 If you want to share the IRQ with another device and the driver refuses to 111 do so, you might succeed with changing the DC390_IRQ type in tmscsim.c to 112 - SA_SHIRQ | SA_INTERRUPT. 113 114 115 3.Features
··· 109 110 If you want to share the IRQ with another device and the driver refuses to 111 do so, you might succeed with changing the DC390_IRQ type in tmscsim.c to 112 + IRQF_SHARED | IRQF_DISABLED. 113 114 115 3.Features
+3 -3
Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl
··· 1149 } 1150 chip->port = pci_resource_start(pci, 0); 1151 if (request_irq(pci->irq, snd_mychip_interrupt, 1152 - SA_INTERRUPT|SA_SHIRQ, "My Chip", chip)) { 1153 printk(KERN_ERR "cannot grab irq %d\n", pci->irq); 1154 snd_mychip_free(chip); 1155 return -EBUSY; ··· 1323 <programlisting> 1324 <![CDATA[ 1325 if (request_irq(pci->irq, snd_mychip_interrupt, 1326 - SA_INTERRUPT|SA_SHIRQ, "My Chip", chip)) { 1327 printk(KERN_ERR "cannot grab irq %d\n", pci->irq); 1328 snd_mychip_free(chip); 1329 return -EBUSY; ··· 1342 1343 <para> 1344 On the PCI bus, the interrupts can be shared. Thus, 1345 - <constant>SA_SHIRQ</constant> is given as the interrupt flag of 1346 <function>request_irq()</function>. 1347 </para> 1348
··· 1149 } 1150 chip->port = pci_resource_start(pci, 0); 1151 if (request_irq(pci->irq, snd_mychip_interrupt, 1152 + IRQF_DISABLED|IRQF_SHARED, "My Chip", chip)) { 1153 printk(KERN_ERR "cannot grab irq %d\n", pci->irq); 1154 snd_mychip_free(chip); 1155 return -EBUSY; ··· 1323 <programlisting> 1324 <![CDATA[ 1325 if (request_irq(pci->irq, snd_mychip_interrupt, 1326 + IRQF_DISABLED|IRQF_SHARED, "My Chip", chip)) { 1327 printk(KERN_ERR "cannot grab irq %d\n", pci->irq); 1328 snd_mychip_free(chip); 1329 return -EBUSY; ··· 1342 1343 <para> 1344 On the PCI bus, the interrupts can be shared. Thus, 1345 + <constant>IRQF_SHARED</constant> is given as the interrupt flag of 1346 <function>request_irq()</function>. 1347 </para> 1348