Hi Arun

I tried changing the flag to IRQF_TRIGGER_HIGH but then device is behaving
abnormally(Hangs and is dead after some time).
Flooding interrupts still observed. Problem not solved.

I want to know, are we supposed to change interrupt pin status or it is
done automatically when we return IRQ_HANDLED.




On Thu, Jun 14, 2012 at 12:21 PM, Sarbojit Ganguly <
unixman.linuxboy@gmail.com> wrote:

Hi Arun,

While I agree to your pointers but he is facing the problem of
"interrupt floods" even before he touches.
IMHO the culprit could be the flag.

On 14 June 2012 12:01, Arun KS [off-list ref] wrote:

quoted

Hello Siddharth,

On Thu, Jun 14, 2012 at 10:34 AM, siddharth saxena
[off-list ref] wrote:

quoted

Hi all

I need help with an issue.
I have written a touch driver for a device and used the flag
IRQF_TRIGGER_LOW to request irq.
Now, when I boot the device, the touch interrupts are coming already

without

quoted

quoted

touching the screen.
Continuous interrupts are occurring without any touch.

Probably the default state of the gpio pin(which you configured as
irq) is low. Check your HW schematic.

TSC should have interrupt polarity(Active High/Low), which you have to
choose depending on your schematic while initiallizing the TSC.
Also different modes like assert interrupt when finger moving, when
finger touch, or assert periodically.

Hope these pointer will help you.

Thanks,
Arun

quoted

--
Regards
Siddharth Saxena


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Regards,
Sarbojit

-- 
Regards
Siddharth Saxena
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120614/9153cb64/attachment.html