Re: de2104x: interrupts before interrupt handler is registered

["linux-os \(Dick Johnson\)" <linux-os@analogic.com>]

On Wed, 8 Mar 2006, Robert Hancock wrote:

> linux-os (Dick Johnson) wrote:
>> You don't bother to read. The reported interrupt is WRONG, INVALID,
>> INCORRECT, BROKEN, until __after__ the device is enabled. That means
>> that one CANNOT put an interrupt handler in place before the
>> device is enabled.
>
> And my point is, even if you COULD put an interrupt handler into place
> before enabling the device, if the device can be in an unstable state
> such that the interrupt can't be acknowledged reliably, how can you
> handle it without causing an interrupt storm?
>

Easy. Mask off the interrupts in the device. Software should
certainly "know" if the device has been initialized to a stable
state. Until it has been initialized, the ISR will simply
clear and mask the device.

> --
> Robert Hancock      Saskatoon, SK, Canada
> To email, remove "nospam" from hancockr@nospamshaw.ca
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.15.4 on an i686 machine (5589.50 BogoMips).
Warning : 98.36% of all statistics are fiction, book release in April.
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/