kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: anish198519851985@gmail.com (anish singh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Continuous Interrupt Problem
Date: Thu, 14 Jun 2012 14:24:50 +0530	[thread overview]
Message-ID: <CAK7N6vq0rPho5BZcdQTsaaB973yWeM+-7B0egPdXm79Hbfq6jg@mail.gmail.com> (raw)
In-Reply-To: <CANUqjFEsF43f70L7TyN1m98A6BAhpgcXSt62_A2vQvcGbuMqqg@mail.gmail.com>

On Thu, Jun 14, 2012 at 2:11 PM, siddharth saxena
<siddharthsaxena1989@gmail.com> wrote:
> 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.
why don't you paste the code for your probe routine where you are
calling request_irq.
Are you using threaded irq?It would be difficult to diagnose the
problem without looking
at your TSP manual and your code to find out the problem.
>
>
>
>
> 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 <getarunks@gmail.com> wrote:
>> > Hello Siddharth,
>> >
>> > On Thu, Jun 14, 2012 at 10:34 AM, siddharth saxena
>> > <siddharthsaxena1989@gmail.com> wrote:
>> >> 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
>> >> 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
>> >
>> >>
>> >>
>> >>
>> >> --
>> >> 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
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

  reply	other threads:[~2012-06-14  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  5:04 Continuous Interrupt Problem siddharth saxena
2012-06-14  5:13 ` anish singh
2012-06-14  6:20   ` Sarbojit Ganguly
2012-06-14  6:31 ` Arun KS
2012-06-14  6:51   ` Sarbojit Ganguly
2012-06-14  8:41     ` siddharth saxena
2012-06-14  8:54       ` anish singh [this message]
2012-06-14  9:05         ` siddharth saxena
2012-06-14  9:29           ` Sarbojit Ganguly
2012-06-14  9:39             ` anish singh
2012-06-14 11:38               ` Sarbojit Ganguly
2012-06-15 10:22           ` Shaji Yusuf
2012-06-16 16:25             ` anish kumar
2012-06-14  9:02       ` Arun KS

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK7N6vq0rPho5BZcdQTsaaB973yWeM+-7B0egPdXm79Hbfq6jg@mail.gmail.com \
    --to=anish198519851985@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).