From: Thierry Reding <thierry.reding@avionic-design.de>
To: "Richard Röjfors" <richard.rojfors.ext@mocean-labs.com>
Cc: Trilok Soni <soni.trilok@gmail.com>,
linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-omap@vger.kernel.org
Subject: Re: [RESEND][PATCH] input: Added TSC2003
Date: Tue, 16 Jun 2009 08:20:44 +0200 [thread overview]
Message-ID: <20090616062044.GA20209@avionic-design.de> (raw)
In-Reply-To: <4A36A1C2.2060805@mocean-labs.com>
* Richard Röjfors wrote:
> On 09-06-15 20.10, Trilok Soni wrote:
> > Hi,
> >
> > On Mon, Jun 15, 2009 at 8:39 PM, Richard
> > Röjfors<richard.rojfors.ext@mocean-labs.com> wrote:
> >> Supplied is a driver for the TSC2003. There is actually a driver for TSC2007 which can be used in some cases.
> >> The platform struct is reused from the TSC2007.
> >> There is a big difference in the implementation between the drivers, this one does not use HR timers.
> >> The TSC2007 driver performs synchronous I2C in the timer callback (SW IRQ context) which is bad when
> >> the I2C driver is interrupt driven.
> >>
> >
> > Meaning? I think I2C transaction can sleep.
>
> Yes that's what it means, and that's bad in a HR timer callback.
Note that my patch to the tsc2007 to support the tsc2003 exactly fixes this
problem. It moves the actual I2C transfers into a workqueue, so no sleeping
functions are called from the hrtimer callback.
Thierry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-16 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 15:09 [RESEND][PATCH] input: Added TSC2003 Richard Röjfors
2009-06-15 18:10 ` Trilok Soni
2009-06-15 19:32 ` Richard Röjfors
2009-06-16 6:20 ` Thierry Reding [this message]
2009-06-16 7:40 ` Richard Röjfors
2009-06-16 8:16 ` Thierry Reding
2009-06-19 0:50 ` Kwangwoo Lee
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=20090616062044.GA20209@avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=akpm@linux-foundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=richard.rojfors.ext@mocean-labs.com \
--cc=soni.trilok@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;
as well as URLs for NNTP newsgroup(s).