From: Nelson Castillo <arhuaco@freaks-unidos.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
dtor@mail.ru, Shine Liu <shinel@foxmail.com>,
dmitry.torokhov@gmail.com,
Maurus Cuelenaere <mcuelenaere@gmail.com>,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] input/touchscreen: add S3C24XX SoC touchscreen input driver
Date: Fri, 23 Oct 2009 00:38:26 -0500 [thread overview]
Message-ID: <2accc2ff0910222238g31161deoe704a889df3c4b3a@mail.gmail.com> (raw)
In-Reply-To: <20091020094132.GA17240@sirena.org.uk>
On Tue, Oct 20, 2009 at 4:41 AM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Oct 20, 2009 at 03:21:17AM -0500, Nelson Castillo wrote:
>
>> Can the s3c driver send the events at full speed? (Maximum possible ADC rate?).
Yes, but in packets I think (The way I would know how to implement it).
We could try sending 2000 events per second to user-space and see what
happens :-) :-)
>> Even if it's possible I think we would monopolize the adc driver
>> needlessly because we don't need all that conversions when there is
>> not much noise. Please read on.
>
> There's currently no facility to push sample rate requests down into the
> kernel from userspace. However, this is a good idea in general - there
> was some recent (brief) discussion of doing this on the linux-input list.
I see. It makes sense.
ATM one big difference with the kernel approach is that in the kernel
you can request the adc conversions on demand.
> Since different use cases have different sample rate requirements (such
> as the difference between handwriting recognition which can need 200
> samples/second and a simple finger operated menu which may be happy with
> 10) there's value in being able to vary the sample rate at run time. I
> was intending to look at this shortly as part of some touchscreen driver
> development I need to do soon or perhaps someone else will pick up the
> idea, if it does get implemented then obviously tslib would also be able
> to use it here.
With a lot more points you can indeed do better filtering in users-pace.
--
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-10-23 5:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4020.1255949705.2256.linux-arm-kernel@lists.infradead.org>
2009-10-19 11:28 ` [PATCH] input/touchscreen: add S3C24XX SoC touchscreen input driver Maurus Cuelenaere
2009-10-19 12:07 ` Russell King - ARM Linux
2009-10-20 4:21 ` Nelson Castillo
2009-10-20 7:39 ` Russell King - ARM Linux
2009-10-20 8:21 ` Nelson Castillo
2009-10-20 9:41 ` Mark Brown
2009-10-23 5:38 ` Nelson Castillo [this message]
2009-10-20 10:09 ` Andy Green
2009-10-19 13:31 ` Shine Liu
2009-10-19 14:44 ` Arnaud Patard
2009-10-19 14:34 ` Juergen Beisert
2009-10-19 10:54 Shine Liu
2009-10-20 1:38 ` Dmitry Torokhov
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=2accc2ff0910222238g31161deoe704a889df3c4b3a@mail.gmail.com \
--to=arhuaco@freaks-unidos.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mcuelenaere@gmail.com \
--cc=shinel@foxmail.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).