RE: [microblaze-uclinux] Interrupt issue

["Duy-Ky Nguyen" <duykynguyen@xxxxxxxxxxx>]

Hi Benny,

Now I have interrupt work fine for me using "char_driver"

It seems to me that "input_driver" employs link list and the "garbish"
results from a dangling pointer when a node is removed by RMMOD. In addtion,
it's impoosible to re-insert that module back in by INSMOD.

So, in my opinion, leave input_driver as it is, use char_driver for frequent
load/unload module.

Your prompt response to my first email regarding this issue realy realy help
me, Benny.

Big thanks and Best wishes to you, Benny ;-)

Duy-Ky

-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Duy-Ky Nguyen
Sent: Monday, October 22, 2007 9:25 PM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: RE: [microblaze-uclinux] Interrupt issue

Hi Benny,

I set the module "keypaddev" is a loadable one to prevent the kernel load
it.

When I load the module (INSMOD) and I'm able to see its IRQ shows up in
/proc/interrupts as expected.

But, when I remove the module (RMMOD) and do "cat /proc/interrupts", now it
display some old content and a lot of UNPRINTABLE char !!! I have to reboot
the target to get rid of them

Do you any idea ?

Thanks so much, Benny,

Duy-Ky

-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Benny Chen
Sent: Monday, October 22, 2007 3:49 PM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] Interrupt issue

Hi Duy-Ky,

> I wrote a simple driver, loaded it, I was able to see it successfully 
> hooked to interrupt IRQ4 I wanted.
> This interrupt is associated with Press Button on Spartan 3E-1600 eva 
> board.
> But there's no response when I pressed the buttons. 
What did your /proc/interrupts say?  Did it associate your driver to irq 4?
Did the interrupt count increase when you press the button?

Regards,
Benny Chen

Duy-Ky Nguyen wrote:
> Hi,
>
> I'm using the latest Petalinux release and kernel 2.4 I'm trying to 
> test GPIO interrupt, but have failed so far.
> There's no response at all when I loaded keypaddev.o come with the 
> package.
>
> I wrote a simple driver, loaded it, I was able to see it successfully 
> hooked to interrupt IRQ4 I wanted.
> This interrupt is associated with Press Button on Spartan 3E-1600 eva 
> board.
> But there's no response when I pressed the buttons.
>
> I'm sure the board works fine with interrupt button as I tested with 
> Windows EDK code in standalone mode, ie no OS at all.
>
> Compare all relevant regosters in these 2 cases, all ENABLE regsiters 
> are the same. T the only differences are the STATUS ones because 
> there's no response to IRQ using Petalinux, but responding from 
> standalone one.
>
> I'd really appreciate your help
>
> Duy-Ky
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : 
> http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/