From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: "Shen, Voice" <Voice.Shen@atmel.com>,
Jean Delvare <khali@linux-fr.org>, "Wu, Josh" <Josh.wu@atmel.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Axel Lin <axel.lin@gmail.com>
Subject: Re: qt1070: Why IRQF_TRIGGER_NONE?
Date: Fri, 4 May 2012 00:56:06 -0700 [thread overview]
Message-ID: <20120504075606.GA4675@core.coreip.homeip.net> (raw)
In-Reply-To: <CACKLOr1hJ5HMfN12ukrNMa3NB_d8u7-VAyJ_D4d6jOb=mB4n_w@mail.gmail.com>
Hi Javier,
On Fri, May 04, 2012 at 09:06:16AM +0200, javier Martin wrote:
> Hi all,
> thank you for your comments.
>
> On 4 May 2012 04:07, Shen, Voice <Voice.Shen@atmel.com> wrote:
> > Hi Jean,
> > Thank you for your information. Although the irq_flag can not be added into "struct i2c_board_info" till now, I will try to find other solution.
> >
> > Thanks again.
> >
> > Hi Javier,
> > As to the IRQ flag depends on SOC. We try to find other solution. Please describe you issue in detail. And what's the mode does your SOC support.
>
> As I stated, with the current 'IRQF_TRIGGER_NONE' flag, this driver
> doesn't work in i.MX27. Furthermore, I don't think it works on any
> platform since as you previously pointed according to the datasheet of
> qt1070, we can use either IRQF_TRIGGER_FALLING or IRQF_TRIGGER_LOW.
> But I don't know what is the sense of using 'IRQF_TRIGGER_NONE' here.
IRQF_TRIGGER_NONE == 0, i.e. "use whatever method board code set up".
--
Dmitry
prev parent reply other threads:[~2012-05-04 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 8:35 qt1070: Why IRQF_TRIGGER_NONE? javier Martin
2012-05-03 1:41 ` Josh Wu
2012-05-03 5:15 ` Shen, Voice
2012-05-03 6:14 ` Jean Delvare
2012-05-04 2:07 ` Shen, Voice
2012-05-04 7:06 ` javier Martin
2012-05-04 7:56 ` Dmitry Torokhov [this message]
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=20120504075606.GA4675@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Josh.wu@atmel.com \
--cc=Voice.Shen@atmel.com \
--cc=axel.lin@gmail.com \
--cc=javier.martin@vista-silicon.com \
--cc=khali@linux-fr.org \
--cc=linux-input@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.