linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nelson Castillo <arhuaco@freaks-unidos.net>
Cc: Maurus Cuelenaere <mcuelenaere@gmail.com>,
	Shine Liu <shinel@foxmail.com>,
	dtor@mail.ru, dmitry.torokhov@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] input/touchscreen: add S3C24XX SoC touchscreen input driver
Date: Tue, 20 Oct 2009 08:39:46 +0100	[thread overview]
Message-ID: <20091020073946.GB723@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <2accc2ff0910192121t27387b90t9cfd5a5252aa00cc@mail.gmail.com>

On Mon, Oct 19, 2009 at 11:21:40PM -0500, Nelson Castillo wrote:
> There is one case where "whatever way" fails here. If you get a set of
> points and you notice they have noise you can schedule more
> conversions _right_away_ without latency to get new points from the
> ADC. That's what the "group filter" does and you can not do that from
> tslib and I say it after learning how to write tslib filters.

In which case people aren't implementing their kernel drivers correctly.
The kernel is supposed to produce a stream of samples when the pen is
touched, and those samples should be delivered to tslib.  tslib's filters
then has the responsibility to read groups of samples, and filter them
using whatever method that the user wants.

I also don't buy your comparison on your web page since there's almost
zero details of what you're comparing.  You don't give details of what
filters you're using with the userspace method - for all the reader
knows, you're not using tslib at all.

> Most people who hear about the filters blindly say "this should be
> done in user-space" without considering this fact.

I'm the original author of tslib.  Don't think for a moment that I haven't
any experience in this area.

  reply	other threads:[~2009-10-20  7:40 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 [this message]
2009-10-20  8:21         ` Nelson Castillo
2009-10-20  9:41           ` Mark Brown
2009-10-23  5:38             ` Nelson Castillo
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=20091020073946.GB723@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arhuaco@freaks-unidos.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dtor@mail.ru \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --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).