Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: "Girish" <girishsg@ti.com>
To: 'Felipe Balbi' <me@felipebalbi.com>, felipe.balbi@nokia.com
Cc: 'Linux OMAP Mailing List' <linux-omap@vger.kernel.org>
Subject: RE: TWL4030 keypad timeout interrupt
Date: Wed, 14 May 2008 10:38:09 +0530	[thread overview]
Message-ID: <023e01c8b580$8242db00$7f8818ac@ent.ti.com> (raw)
In-Reply-To: <3d1886c4eeb5320b5d443df10b6bed87@felipebalbi.com>

 
>
>
>On Tue, 13 May 2008 16:54:17 +0300, Felipe Balbi 
><felipe.balbi@nokia.com>
>wrote:
>> Hi all,
>> 
>> I noted whenever we release a key in omap-twl4030.c driver it 
>> generates two interrupts: one for release event and one for 
>a timeout event.
>> 
>> Is that expected or is that a bug somewhere in the driver ?
>> 
>> It's easily noted by cat /proc/interrupts ;-)
>
>Replying to myself as I found some more clues.
>
>By checking the code I could see that only rising edge of 
>timeout interrupt is being enabled. Also timeout register is 
>at 0xd6, but code is writing 0x04...
>

No, the code is writing to 0x00D2 + 0x04 (the t2keypad base address: 0x00D2). 

>So if i read it correctly, we might have 0 set as our timeout.
>
>which might explain why we only see the timeout interrupt when 
>releasing the key.
>
>Am I right ?

Well, the timeout is here to help the controller come out of hangs, if any. 

>
>I might be completely wrong here, but that extra interrupt 
>happening all the time is just bugging me :-p




Regards,
Girish



  reply	other threads:[~2008-05-14  5:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 13:54 TWL4030 keypad timeout interrupt Felipe Balbi
2008-05-13 14:28 ` Felipe Balbi
2008-05-14  5:08   ` Girish [this message]
2008-05-14  8:16     ` Felipe Balbi
2008-05-14  8:57       ` Girish
2008-05-14  9:52         ` Gopinath, Thara
2008-05-14 10:08           ` Felipe Balbi

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='023e01c8b580$8242db00$7f8818ac@ent.ti.com' \
    --to=girishsg@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    /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