From: Dirk Behme <dirk.behme@googlemail.com>
To: Arnold <abo_gwapo@yahoo.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Noise causes gpio interrupt
Date: Fri, 26 Jan 2007 15:15:22 +0100 [thread overview]
Message-ID: <45BA0CFA.5010409@googlemail.com> (raw)
In-Reply-To: <740992.7549.qm@web55304.mail.re4.yahoo.com>
Arnold wrote:
> ... However when the interupt comes from a
> device and the transition of rise to fall is 20ns it
> could not detect that an interrupt occured. I also
> tried to increase the transition to 20ms and it was
> able to detect the interrupt. ...
Maybe http://www.ti.com/litv/pdf/spru767a, section 1.6 or
page 28, can help:
"Because of the sample operation with the functional clock,
the minimum pulse
width on the input GPIO to trigger a synchronous interrupt
request is two times
the functional clock period. This minimum pulse width must
be met before and
after any expected level transition detection."
Best regards
Dirk
next prev parent reply other threads:[~2007-01-26 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 9:40 Noise causes gpio interrupt Arnold
2007-01-25 9:43 ` Syed Mohammed, Khasim
2007-01-25 15:01 ` Woodruff, Richard
2007-01-26 7:19 ` Arnold
2007-01-26 14:15 ` Dirk Behme [this message]
2007-01-29 21:01 ` Woodruff, Richard
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=45BA0CFA.5010409@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=abo_gwapo@yahoo.com \
--cc=linux-omap-open-source@linux.omap.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