From: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-kernel@vger.kernel.org, qi.wang@intel.com,
yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com, toshiharu-linux@dsn.okisemi.com
Subject: Re: [PATCH v3] pch_gpio: Support interrupt function
Date: Wed, 22 Jun 2011 17:14:10 +0900 [thread overview]
Message-ID: <4E01A452.8060801@dsn.okisemi.com> (raw)
In-Reply-To: <201106220828.30516.alexander.stein@systec-electronic.com>
(2011/06/22 15:28), Alexander Stein wrote:
> On Wednesday 22 June 2011 02:10:28 Tomoya MORINAGA wrote:
>> (2011/06/21 18:10), Alexander Stein wrote:
>>> I wrote a small program which use poll(2) on value, after edge hase been
>>> configured from shell. I cannot test the edge detection appropriately due
>>> to debouncing using jumpers.
>>
>> Really ?
>> In out test environment, my test program could detect edge interrupt
>> correctly.
>
> My test program used poll/select on edge successfully. But I could not test
> the raising or falling feature actually, as my input is bouncing. So, it
> doesn't matter if I set both/raising/falling in edge, due to my inputs the
> effect is the same. Any input event will end in several raising and falling
> interrupts events.
> I hope I could make this more clear.
Our test program also uses poll (We don't use select().)
BTW, is the above your saying related to your patch "[PATCH] pch_gpio:
transform mutex into spinlock" ?
--
tomoya
OKI SEMICONDUCTOR CO., LTD.
next prev parent reply other threads:[~2011-06-22 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 4:44 Tomoya MORINAGA
2011-06-21 9:10 ` Alexander Stein
2011-06-22 0:10 ` Tomoya MORINAGA
2011-06-22 6:28 ` Alexander Stein
2011-06-22 8:14 ` Tomoya MORINAGA [this message]
2011-06-22 9:15 ` Alexander Stein
2011-06-27 10:03 ` Alexander Stein
2011-06-30 2:07 ` Tomoya MORINAGA
2011-06-30 7:53 ` Alexander Stein
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=4E01A452.8060801@dsn.okisemi.com \
--to=tomoya-linux@dsn.okisemi.com \
--cc=alexander.stein@systec-electronic.com \
--cc=grant.likely@secretlab.ca \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=yong.y.wang@intel.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
all inboxes | Powered by JetHome®