From: Josh Wu <josh.wu@atmel.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bo Shen <voice.shen@atmel.com>,
khali@linux-fr.org, w.sang@pengutronix.de, jm.lin@atmel.com,
linux-input@vger.kernel.org
Subject: Re: [RFC] QT1070: change the trigger mode of QT1070
Date: Fri, 11 May 2012 19:33:08 +0800 [thread overview]
Message-ID: <4FACF8F4.2090302@atmel.com> (raw)
In-Reply-To: <CACKLOr0_ztBXfTwa1R_yLzf6wEABENf=-MzYHd-J5YQtEmQt9w@mail.gmail.com>
Hi, Javier
On 5/11/2012 5:13 PM, javier Martin wrote:
> Hi all,
> let's take a chip which presents a similar issue like the pca953x [1].
> This chip has an IRQ line that is meant to be connected to a SoC input
> like the qt1070.
>
> The flags that are used for pca953x are: (IRQF_TRIGGER_LOW | IRQF_ONESHOT)
>
> Can't we do the same for qt1070?
I did a simple test in my board in 2.6.39, This flag doesn't work. But
IRQF_TRIGGER_FALLING works fine.
So the question is what is different between this flag with
IRQF_TRIGGER_FALLING?
> And even more important, can you give me an example of an architecture
> in mainline which cannot support these irq flags and still be able to
> detect a change from high to low in a GPIO as qt1070 requires?
For now, AT91SAM9M10 can only detect GPIO input change, it cannot tell
is falling or rising. So in theory it cannot support falling flags.
The strange thing is, currently we use IRQF_TRIGGER_NONE in 2.6.39
kernel for both AT91SAM9M10 and 9X5 chips, and they all work fine. So I
need check the code of GPIO part.
>
> Moreover, if you try a grep for IRQ_TRIGGER_NONE in the kernel tree
> you won't find any driver doing this strange thing.
>
> Do you agree at least that we must change IRQ_TRIGGER_NONE flag into a
> more sensible choice?
Yes. I agreed.
>
> Regards.
>
> [1] http://lxr.linux.no/#linux+v3.3.4/drivers/gpio/gpio-pca953x.c#L495
>
Best Regards,
Josh Wu
next prev parent reply other threads:[~2012-05-11 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 2:27 [RFC] QT1070: change the trigger mode of QT1070 Bo Shen
2012-05-07 7:04 ` Dmitry Torokhov
2012-05-07 7:09 ` javier Martin
2012-05-08 7:45 ` Shen, Voice
2012-05-11 8:28 ` Josh Wu
2012-05-11 9:13 ` javier Martin
2012-05-11 11:33 ` Josh Wu [this message]
2012-05-11 12:47 ` javier Martin
2012-05-14 2:57 ` Bo Shen
2012-05-14 6:59 ` javier Martin
2012-05-14 7:21 ` javier Martin
2012-05-11 16:06 ` Dmitry Torokhov
2012-05-11 16:08 ` Dmitry Torokhov
2012-05-14 2:54 ` Bo Shen
2012-05-11 8:07 ` Josh Wu
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=4FACF8F4.2090302@atmel.com \
--to=josh.wu@atmel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=javier.martin@vista-silicon.com \
--cc=jm.lin@atmel.com \
--cc=khali@linux-fr.org \
--cc=linux-input@vger.kernel.org \
--cc=voice.shen@atmel.com \
--cc=w.sang@pengutronix.de \
/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).