Looks like you already figured out your issue but this was how I did mine when
I wrote a simple kernel module:
void init_interrupt(void)
{
.
.
.
request_irq( DAVINCI_GPIO_IRQ(1),
(irq_handler_t)my_handler,
IRQF_DISABLED | IRQF_TRIGGER_FALLING,
"gpio1intr",
NULL
);
.
.
.
}
static irqreturn_t my_handler( int irq, void *dev_id, struct pt_regs *regs )
{
// We're called with interrupts disabled.
DEBUG( Trace, "my_handler called\n" );
// do something
return IRQ_HANDLED;
}
Regards,
Andy
----- Original Message ----
From: Lorenzo Lutti <[EMAIL PROTECTED]>
To: davinci-linux-open-source <davinci-linux-open-source@linux.davincidsp.com>
Sent: Friday, May 4, 2007 6:33:14 AM
Subject: Re: GPIO interrupts in kernel 2.6.10
Constantine Shulyupin ha scritto:
> __raw_writel(gpio_mask(gpio), &g->set_rising);
Thank you, this (SET_RIS_TRIG01, in my case SET_FAL_TRIG01) was the register
that I missed in my setup! Not it works fine.
Cheers, Lorenzo
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
