feiyang yun ha scritto:
Hi,I have read your ADS7846 driver
Please note that it isn't mine, I've just copied & pasted from the DaVinci
mailing list:
http://linux.omap.com/pipermail/davinci-linux-open-source/2007-April/003167.html
Now I'm modifying it (a lot of useful code was commented in th
NDLED;
}
Regards,
Andy
- Original Message
From: Lorenzo Lutti <[EMAIL PROTECTED]>
To: davinci-linux-open-source
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),
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-s
Hi,
I wrote and used this code on 2.6.10 with some simple porting from git
tree
(pay attention to set_rising):
int gpio_request_irq(unsigned int gpio, irqreturn_t (*handler)(int, void
*, struct pt_regs *),
unsigned long irq_flags, const char * devname, void
*dev_id)
{ FNST
Matthias Welwarsky ha scritto:
But the ISR is never called. Why? request_irq() returns succesfully
and the kernel doesn't complain (it just output the unbalanced irq
message, which is harmless as far as I know).
In 2.6.10, you need to set up the GPIO interrupt bank yourself, i.e.
enabling and
Lorenzo Lutti wrote:
> Question number 1: why enabling IRQ49 isn't enough? A code like this
> doesn't work:
>
> DAVINCI_PINMUX0 &= ~(1<<26);// just in case
> if( request_irq( 49,my_irq_handler, SA_INTERRUPT, "test", NULL))
> {
> ...
> }
> set_irq_type( 49, IRQT_FALLING);
> enable_irq( 49);
> .
Hi, I'm trying (until now, failing) to make the GPIO interrupts work with the
SDK's kernel (i.e. 2.6.10). Probably the best idea would be to backport this
functionality from the 2.6.19 kernel, but there have been a lot of changes and
I don't understand some of them. Let's say that that my objec
