linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shine Liu <shinel@foxmail.com>
To: Maurus Cuelenaere <mcuelenaere@gmail.com>
Cc: linux-input@vger.kernel.org, dtor@mail.ru,
	dmitry.torokhov@gmail.com, linux-arm-kernel@lists.infradead.org,
	Nelson Castillo <arhuaco@freaks-unidos.net>,
	linux@arm.linux.org.uk
Subject: Re: [PATCH] input/touchscreen: add S3C24XX SoC touchscreen input driver
Date: Mon, 19 Oct 2009 21:31:51 +0800	[thread overview]
Message-ID: <1255959111.3708.32.camel@sl> (raw)
In-Reply-To: <4ADC4D4D.5020508@gmail.com>

On Mon, 2009-10-19 at 13:28 +0200, Maurus Cuelenaere wrote:

> Do you know that there's another patch (at Openmoko) created by Nelson 
> Castillo that does the same, but also has support for kernel-space 
> touchscreen filters? (I think [1] is his latest version)
> I don't know how your patch performs, but according to [2] the filters 
> should help a lot avoiding jitter etc.
> 
> I'm not sure whether Nelson has submitted his patches for mainline 
> review yet and what the status is on the kernel filters, but IMHO doing 
> some filtering in kernel space (see the "Why are we doing filtering in 
> kernel space?" part of [2]) which results in a "cleaner" output is 
> preferred over reporting possible "jittery" data.

Yes, I do,  because part of my patch comes from source code of openmoko
project. I've also noticed there's 4 touchscreen filters in the openmoko
project used by s3c24xx touchscreen driver.

I think there should be a s3c24xx touchscreen driver in the mailine, but
I haven't found anyone submitted a s3c24xx touchscreen driver for the
mainline. So I wrote the driver myself and refered the openmoko
implementation.

I didn't use the kernel-space touchscreen filters, because I found tslib
is able to meet the common requirement.

I have read the mail of Russell King. I think we may add the s3c24xx ts
driver first, and the kernel-space touchscreen filters can be added
later if most of us think it is valuable or usefull. After all, I don't
think there is anyone like the mailine without s3c24xx ts driver
support.


Cheers,

Shine Liu


  parent reply	other threads:[~2009-10-19 13:32 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
2009-10-20 10:09           ` Andy Green
2009-10-19 13:31   ` Shine Liu [this message]
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=1255959111.3708.32.camel@sl \
    --to=shinel@foxmail.com \
    --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=linux@arm.linux.org.uk \
    --cc=mcuelenaere@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).