From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sven Neumann <s.neumann@raumfeld.com>,
Olof Johansson <olof@lixom.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Eric Miao <eric.y.miao@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Emulating level IRQs (was: Re: [PATCH] Input: eeti_ts: Mark as CONFIG_BROKEN)
Date: Tue, 24 Jul 2012 19:58:26 +0100 [thread overview]
Message-ID: <20120724185825.GA32169@sirena.org.uk> (raw)
In-Reply-To: <500EE314.7040708@gmail.com>
On Tue, Jul 24, 2012 at 08:01:56PM +0200, Daniel Mack wrote:
> On 23.07.2012 18:51, Dmitry Torokhov wrote:
> > Hmm, but that would mean we need to restore reading the data in open()
> > to make sure we re-arm IRQ in case somebody touched the screen before it
> > was opened by userspace...
> I had another look at this and don't really know what to do here. We
> definitely need level interrupts for this device as the interrupt line's
> level is the only that tells us when we can stop reading from the
> device. So it's not just the start condition that bites us here.
> I copied some people that might help find a solution.
I've raised the same issue myself, it's fairly common.
> So it boils down to the question: Is there any easy and generic way to
> emulate level irq on chips that don't support that natively?
Nothing in core. The nearest thing is to poll until you run out of work
(which is rude but survivable for threaded IRQs that don't assert too
much), ideally just reusing the level IRQ if it can report IRQ_NONE.
next prev parent reply other threads:[~2012-07-24 18:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 5:40 [PATCH] Input: eeti_ts: Mark as CONFIG_BROKEN Olof Johansson
2012-04-07 7:02 ` Dmitry Torokhov
2012-04-07 18:38 ` Sven Neumann
2012-04-07 20:32 ` Olof Johansson
2012-04-07 21:04 ` Joachim Eastwood
2012-04-09 2:28 ` Haojian Zhuang
2012-04-10 10:10 ` Russell King - ARM Linux
2012-04-10 16:01 ` Dmitry Torokhov
2012-05-03 4:36 ` Dmitry Torokhov
2012-07-13 7:01 ` Dmitry Torokhov
2012-07-15 18:21 ` Daniel Mack
2012-07-17 12:59 ` Daniel Mack
2012-07-19 15:36 ` Daniel Mack
2012-07-23 16:51 ` Dmitry Torokhov
2012-07-23 17:58 ` Daniel Mack
2012-07-24 18:01 ` Emulating level IRQs (was: Re: [PATCH] Input: eeti_ts: Mark as CONFIG_BROKEN) Daniel Mack
2012-07-24 18:58 ` Mark Brown [this message]
2012-08-05 16:22 ` Emulating level IRQs Daniel Mack
2012-08-05 16:56 ` Haojian Zhuang
2012-08-05 17:56 ` Daniel Mack
2012-08-06 1:45 ` Eric Miao
2012-08-06 16:36 ` Mark Brown
2012-08-07 15:19 ` Daniel Mack
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=20120724185825.GA32169@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=s.neumann@raumfeld.com \
--cc=tglx@linutronix.de \
--cc=zonque@gmail.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
Powered by JetHome