summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTim Small <tim@buttersideup.com>2014-07-22 14:28:00 +0100
committerTejun Heo <tj@kernel.org>2014-07-22 10:08:31 -0400
commit11838230da18cea5bc26a813b5425fe839248e93 (patch)
treeb4a9f65d01729f0b837c8ae9a223ee53fd8eaf1b
parentaf64dce4cb3a848ece2431e1a18feebdcf57f444 (diff)
downloadop-kernel-dev-11838230da18cea5bc26a813b5425fe839248e93.zip
op-kernel-dev-11838230da18cea5bc26a813b5425fe839248e93.tar.gz
sata_sil24: Identify which card suffered IRQ status error
In machines with multiple Silicon Image 3124 and/or 3132 cards, there is no way to tell which card is the culprit when the sata_sil24 interrupt handler gets a bad status. Tested-by: Tim Small <tim@seoss.co.uk> Signed-off-by: Tim Small <tim@seoss.co.uk> Signed-off-by: Tejun Heo <tj@kernel.org>
-rw-r--r--drivers/ata/sata_sil24.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/ata/sata_sil24.c b/drivers/ata/sata_sil24.c
index 0534890..d81b20d 100644
--- a/drivers/ata/sata_sil24.c
+++ b/drivers/ata/sata_sil24.c
@@ -1154,8 +1154,8 @@ static irqreturn_t sil24_interrupt(int irq, void *dev_instance)
status = readl(host_base + HOST_IRQ_STAT);
if (status == 0xffffffff) {
- printk(KERN_ERR DRV_NAME ": IRQ status == 0xffffffff, "
- "PCI fault or device removal?\n");
+ dev_err(host->dev, "IRQ status == 0xffffffff, "
+ "PCI fault or device removal?\n");
goto out;
}
OpenPOWER on IntegriCloud