From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: "Linux Input" <linux-input@vger.kernel.org>,
"Richard Röjfors" <richard.rojfors.ext@mocean-labs.com>
Subject: Re: [RFC/RFT][PATCH] Input: tsc2007 - convert to threaded IRQ
Date: Thu, 25 Aug 2011 00:56:25 -0700 [thread overview]
Message-ID: <20110825075624.GC24739@core.coreip.homeip.net> (raw)
In-Reply-To: <20110825075253.GA10702@avionic-0098.adnet.avionic-design.de>
On Thu, Aug 25, 2011 at 09:52:54AM +0200, Thierry Reding wrote:
> * Dmitry Torokhov wrote:
> > On Thu, Aug 25, 2011 at 09:06:57AM +0200, Thierry Reding wrote:
> > > * Dmitry Torokhov wrote:
> > > > On Thu, Aug 25, 2011 at 08:21:59AM +0200, Thierry Reding wrote:
> > > > > * Dmitry Torokhov wrote:
> > > > > > This is completely untested but I believe it should work better than original
> > > > > > workqueue solution, especially when we do not have get_pendown_state method
> > > > > > available. I wonder if it will help Richard's issue with IRQ getting re-raised
> > > > > > after pen up event.
> > > > > >
> > > > > > Anyone who has hardware - please give it a spin.
> > > > >
> > > > > I can see no noticeable changes with this patch.
> > > > >
> > > >
> > > > That's the result I was aiming for ;) Thanks for testing.
> > > >
> > > > Oh, crap... Does it still work if you change IRQ flags in
> > > > request_threaded_irq() from 0 to IRQF_ONESHOT?
> > > >
> > > > Also, while we are at it would you ming trying out another patch
> > > > (below)?
> > >
> > > With both your patch applied and the change from 0 to IRQF_ONESHOT the driver
> > > oopses when loaded. I didn't have time to investigate further, but I think I
> > > could perhaps test a couple more patches if you provide them.
> >
> > Hmm, can't spot the problem... Where does it die?
>
> I'll see if I can track it down, but I have very limited time.
Don't worry, there is no rush whatsoever... I'll try to ponder the code
some more.
>
> > If you could try just IRFQ_ONESHOT change that would be helpful.
>
> With only just this change, things work okay.
Excellent, thanks.
--
Dmitry
next prev parent reply other threads:[~2011-08-25 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 6:17 [RFC/RFT][PATCH] Input: tsc2007 - convert to threaded IRQ Dmitry Torokhov
2011-08-25 6:21 ` Thierry Reding
2011-08-25 6:43 ` Dmitry Torokhov
2011-08-25 7:06 ` Thierry Reding
2011-08-25 7:34 ` Dmitry Torokhov
2011-08-25 7:52 ` Thierry Reding
2011-08-25 7:56 ` Dmitry Torokhov [this message]
2011-08-25 8:05 ` Dmitry Torokhov
2011-08-25 8:25 ` Thierry Reding
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=20110825075624.GC24739@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=richard.rojfors.ext@mocean-labs.com \
--cc=thierry.reding@avionic-design.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).