Re: Shared Interrupt handling.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/4/07, k b <k_bisla@xxxxxxxxxxx> wrote:
hmm... so then how does the int handler know if it needs to service an
interrupt.

I mean it could be that the handler was invoked by the kernel when it walked
through all the int handlers.
so how does the handler know if there is actually an interrupt to be
serviced if there's not hardware reg on the device to tell that.


Hi KB,

What Mike is getting at is this: It is upon the handler to determine
whether the device it services, has actually generated this interrupt.
How the ISR enquires the IRQ status from the device is device
specific. In most of the situations, the device has a register which
says so.

However, I could not understand your reasoning behind the statement
that a device generating seldom interrupts should not be sharing the
IRQ line with a device device generic IRQs often. Can you please
elaborate?

Thanks,

Rajat

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux