From: Ondrej Zary <linux@rainbow-software.org>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] g_NCR5380: Test the IRQ before accepting it
Date: Mon, 31 Oct 2016 09:35:58 +0100 [thread overview]
Message-ID: <201610310935.58892.linux@rainbow-software.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1610311348110.32132@nippy.intranet>
On Monday 31 October 2016, Finn Thain wrote:
> On Sun, 30 Oct 2016, Ondrej Zary wrote:
> > Trigger an IRQ first with a test IRQ handler to find out if it really
> > works. Disable the IRQ if not.
> >
> > This prevents hang when incorrect IRQ was specified by user.
> >
> > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
> > ---
> > drivers/scsi/g_NCR5380.c | 32 ++++++++++++++++++++++++++++++--
> > 1 file changed, 30 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/scsi/g_NCR5380.c b/drivers/scsi/g_NCR5380.c
> > index 3790ed5..261e168 100644
> > --- a/drivers/scsi/g_NCR5380.c
> > +++ b/drivers/scsi/g_NCR5380.c
> > @@ -67,6 +67,14 @@
> > MODULE_ALIAS("g_NCR5380_mmio");
> > MODULE_LICENSE("GPL");
> >
> > +static bool irq_working;
> > +
> > +static irqreturn_t test_irq(int irq, void *dev_id)
> > +{
> > + irq_working = true;
> > + return IRQ_HANDLED;
> > +}
> > +
> > /*
> > * Configure I/O address of 53C400A or DTC436 by writing magic numbers
> > * to ports 0x779 and 0x379.
> > @@ -275,10 +283,30 @@ static int generic_NCR5380_init_one(struct
> > scsi_host_template *tpnt, /* set IRQ for HP C2502 */
> > if (board == BOARD_HP_C2502)
> > magic_configure(port_idx, instance->irq, magic);
> > - if (request_irq(instance->irq, generic_NCR5380_intr,
> > - 0, "NCR5380", instance)) {
> > + /* test if the IRQ is working */
> > + irq_working = false;
> > + if (request_irq(instance->irq, test_irq,
> > + 0, "NCR5380-irqtest", NULL)) {
> > printk(KERN_WARNING "scsi%d : IRQ%d not free, interrupts disabled\n",
> > instance->host_no, instance->irq); instance->irq = NO_IRQ;
> > + } else {
> > + NCR5380_trigger_irq(instance);
> > + NCR5380_read(RESET_PARITY_INTERRUPT_REG);
> > + free_irq(instance->irq, NULL);
> > + if (irq_working) {
> > + if (request_irq(instance->irq,
> > + generic_NCR5380_intr, 0,
> > + "NCR5380", instance)) {
> > + printk(KERN_WARNING "scsi%d : IRQ%d not free, interrupts
> > disabled\n", + instance->host_no,
> > + instance->irq);
> > + instance->irq = NO_IRQ;
> > + }
> > + } else {
> > + printk(KERN_WARNING "scsi%d : IRQ%d not working, interrupts
> > disabled\n", + instance->host_no, instance->irq);
> > + instance->irq = NO_IRQ;
> > + }
> > }
> > }
>
> If the user omits to specify an irq, you can just default to IRQ_AUTO.
> This might result in NO_IRQ, which gives the same result as this patch.
Looks like a good idea.
> And when the user does specify an IRQ, we should trust them. So this
> compexity doesn't add any value AFAICT. Thanks but no thanks.
This fixes a real problem: specifying wrong IRQ hangs the machine completely.
It's really easy - if the IRQ is free but configured in BIOS as PCI IRQ (not
ISA). Everything seems fine except the IRQ will never trigger.
--
Ondrej Zary
next prev parent reply other threads:[~2016-10-31 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 22:40 [PATCH 1/3] NCR5380: Use probe_irq_*() for IRQ probing Ondrej Zary
2016-10-30 22:40 ` [PATCH 2/3] g_NCR5380: Test the IRQ before accepting it Ondrej Zary
2016-10-31 3:09 ` Finn Thain
2016-10-31 8:35 ` Ondrej Zary [this message]
2016-10-31 9:46 ` Finn Thain
2016-10-30 22:40 ` [PATCH 3/3] NCR5380: Check for chip presence in NCR5380_init() Ondrej Zary
2016-10-31 3:12 ` Finn Thain
2016-10-31 7:59 ` Ondrej Zary
2016-10-31 9:35 ` Finn Thain
2016-10-31 3:29 ` Finn Thain
2016-10-31 3:07 ` [PATCH 1/3] NCR5380: Use probe_irq_*() for IRQ probing Finn Thain
2016-10-31 8:11 ` Ondrej Zary
2016-10-31 9:40 ` Finn Thain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201610310935.58892.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=fthain@telegraphics.com.au \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.