Re: 2 questions about interrupts
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
>>
>> 2) How do I change irq_desc[my_irq].action->handler
?
>>
is there a clean interface to update it?
>Why do you want to do this? Is request_irq()
not sufficient?
I am using the intel ia32 performance
counters to fire a overflow interrupt. (2.4.21 kernel)
I use request_irq to register the handler
(and it works), but I get
the default behavior of printing the
"unexpected IRQ trap at vector xx"
on every interrupt before the ack.
The only way that I have found to "fix"
this problem is to replace the
default irq_desc[#]->handler->ack
routine.
I can do this by using the map to get
the address of irq_desc[] and then
replacing the default handler, but isn't
there a better way to do this?
I used "request_irq(0xd0,my_handler,SA_INTERRUPT,"My
Interrupt",NULL);
[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]