aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/scsi/ncr53c8xx.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/scsi/ncr53c8xx.txt')
-rw-r--r--Documentation/scsi/ncr53c8xx.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/scsi/ncr53c8xx.txt b/Documentation/scsi/ncr53c8xx.txt
index 39d409a8efe5..230e30846ef2 100644
--- a/Documentation/scsi/ncr53c8xx.txt
+++ b/Documentation/scsi/ncr53c8xx.txt
@@ -785,8 +785,8 @@ port address 0x1400.
785 irqm:0 always open drain 785 irqm:0 always open drain
786 irqm:1 same as initial settings (assumed BIOS settings) 786 irqm:1 same as initial settings (assumed BIOS settings)
787 irqm:2 always totem pole 787 irqm:2 always totem pole
788 irqm:0x10 driver will not use SA_SHIRQ flag when requesting irq 788 irqm:0x10 driver will not use IRQF_SHARED flag when requesting irq
789 irqm:0x20 driver will not use SA_INTERRUPT flag when requesting irq 789 irqm:0x20 driver will not use IRQF_DISABLED flag when requesting irq
790 790
791 (Bits 0x10 and 0x20 can be combined with hardware irq mode option) 791 (Bits 0x10 and 0x20 can be combined with hardware irq mode option)
792 792
@@ -1236,15 +1236,15 @@ when the SCSI DATA IN phase is reentered after a phase mismatch.
1236When an IRQ is shared by devices that are handled by different drivers, it 1236When an IRQ is shared by devices that are handled by different drivers, it
1237may happen that one driver complains about the request of the IRQ having 1237may happen that one driver complains about the request of the IRQ having
1238failed. Inder Linux-2.0, this may be due to one driver having requested the 1238failed. Inder Linux-2.0, this may be due to one driver having requested the
1239IRQ using the SA_INTERRUPT flag but some other having requested the same IRQ 1239IRQ using the IRQF_DISABLED flag but some other having requested the same IRQ
1240without this flag. Under both Linux-2.0 and linux-2.2, this may be caused by 1240without this flag. Under both Linux-2.0 and linux-2.2, this may be caused by
1241one driver not having requested the IRQ with the SA_SHIRQ flag. 1241one driver not having requested the IRQ with the IRQF_SHARED flag.
1242 1242
1243By default, the ncr53c8xx and sym53c8xx drivers request IRQs with both the 1243By default, the ncr53c8xx and sym53c8xx drivers request IRQs with both the
1244SA_INTERRUPT and the SA_SHIRQ flag under Linux-2.0 and with only the SA_SHIRQ 1244IRQF_DISABLED and the IRQF_SHARED flag under Linux-2.0 and with only the IRQF_SHARED
1245flag under Linux-2.2. 1245flag under Linux-2.2.
1246 1246
1247Under Linux-2.0, you can disable use of SA_INTERRUPT flag from the boot 1247Under Linux-2.0, you can disable use of IRQF_DISABLED flag from the boot
1248command line by using the following option: 1248command line by using the following option:
1249 1249
1250 ncr53c8xx=irqm:0x20 (for the generic ncr53c8xx driver) 1250 ncr53c8xx=irqm:0x20 (for the generic ncr53c8xx driver)
@@ -1252,7 +1252,7 @@ command line by using the following option:
1252 1252
1253If this does not fix the problem, then you may want to check how all other 1253If this does not fix the problem, then you may want to check how all other
1254drivers are requesting the IRQ and report the problem. Note that if at least 1254drivers are requesting the IRQ and report the problem. Note that if at least
1255a single driver does not request the IRQ with the SA_SHIRQ flag (share IRQ), 1255a single driver does not request the IRQ with the IRQF_SHARED flag (share IRQ),
1256then the request of the IRQ obviously will not succeed for all the drivers. 1256then the request of the IRQ obviously will not succeed for all the drivers.
1257 1257
125815. SCSI problem troubleshooting 125815. SCSI problem troubleshooting