before making some source code,
I am wondering about interrupt and polling also thread...
my question is....
if I use unique irq number, I could use ..
Code:
int irq_unique=UNIQIRQ;
ret = request_irq(irq_uniqe, unique_interrupt,
irq_flags, "unique", i);
static irqreturn_t unique_interrupt(int irq, void *dev_id)
{
do { iir = inb(up, IIR);)}
printk("interrupt\n");
msleep(1000);
} while (1);
In my opinion , in this case, Do I use do -while structure ?
I think, if I use unique irq, it is almost same "not use do-while". right?
Code:
int irq_unique=UNIQIRQ;
ret = request_irq(irq_uniqe, unique_interrupt,
static irqreturn_t unique_interrupt(int irq, void *dev_id)
{
printk("interrupt UNIQ\n");
irq_flags, "unique", i);
}
It is same.whenver UNIQIRQ happen, Could I see the "interrupt UNIQ" message? Am I right?
Q2)
If then.
HOWEVER, In case of SHARED-IRQ,
Do I have to make interrupt function using "double-linked list" like 8250.c??
If I use same function like "unique irq thing...above function..." , what happen ?, Can I even see the printk message ? or not ?
Actually, I don't know how I make the double-linked list.....
and also, why do I need to use {do-while} structure......
I think do -while is not a interrupt......
Can Somebody explain this structure or urls for this ?
by the way, I'm sorry about my stupid english, English is not mothers languge..forgive me...
But, I want to understand this whole mechanism.....
also, between "do-while" and "thread" or polling
do-while ....looks like thread or polling......
I don't understand.....do-while structure in the shared interrupt...
I have to make some device driver using "Shared IRQ -UART1"
please..if somebody understand what I'm saying.let me know..."
"
