From: "andrzej zaborowski" <balrogg@gmail.com>
To: Daniel Stone <daniel.stone@nokia.com>
Cc: Lauri Leukkunen <lauri.leukkunen@nokia.com>,
ext Felipe Balbi <me@felipebalbi.com>,
felipe.balbi@nokia.com, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
Eduardo Valentin <edubezval@gmail.com>
Subject: Re: [PATCH 1/5] I2C: LM8323: Introduce lm8323 keypad driver
Date: Thu, 10 Apr 2008 03:12:27 +0200 [thread overview]
Message-ID: <fb249edb0804091812g77b6fc84x3312ea09c845ea3a@mail.gmail.com> (raw)
In-Reply-To: <20080410001224.GD5897@intune.research.nokia.com>
On 10/04/2008, Daniel Stone <daniel.stone@nokia.com> wrote:
> On Thu, Apr 10, 2008 at 01:58:51AM +0200, ext andrzej zaborowski wrote:
> > On 09/04/2008, Lauri Leukkunen <lauri.leukkunen@nokia.com> wrote:
>
> > > In my opinion kernel should provide "correct" data to user-space, not
> > > some pseudo-random interference from the LCD.
> >
> > I think this is discutible. There's a number of userspace libraries
> > written to talk tightly to the kernel and make that data more
> > "correct", one of them is tslib. Distros that come with tslib often
> > have a set of device-specific config files for tslib which load tslib
> > plugins for things like averaging, smoothing, checking bounds on the
> > values.
> >
> > One of the arguments for doing that in userspace is that of avoiding
> > every touchscreen driver redoing the same averaging and/or limit
> > checking code. I agree thought that it may be better to sacrifice
> > that for performance.
>
>
> If everyone's doing the same thing, move it to drivers/input/, not to
> userspace. Why should we be forced to have _two_ drivers and
> essentially maintain a stable kernel/userspace ABI between them? Surely
> it's better to only have _one_ hardware-specific driver, rather than
> half in the kernel, and half hidden behind an abstraction layer that is
> meant to let you just deal with input events without knowing stupid
> details about the hardware?
For the ease of reconfiguration for one thing, tslib is quite
configurable with the plugins loaded by a config file. The ABI you
talk about is the same evdev ABI which is already stable.
Averaging doesn't just cancel the noise from LCD, just lessens it but
there may be better things to do with it and the userspace already
knows how to deal with that. So it expects the kernel driver to be
more like a ADC driver.
Of course doing it in drivers/input/ as configured by board files,
would also work if things were designed that way.
Cheers
next prev parent reply other threads:[~2008-04-10 1:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 12:03 [PATCH 0/5] n810 drivers, take #3 Felipe Balbi
2008-04-09 12:04 ` [PATCH 1/5] I2C: LM8323: Introduce lm8323 keypad driver Felipe Balbi
2008-04-09 12:04 ` [PATCH 2/5] I2C: TSL2563: Add support for Taos tsl2563 ambient light sensor Felipe Balbi
2008-04-09 12:04 ` [PATCH 3/5] INPUT: TOUCHSCREEN: Introduce tsc2005 driver Felipe Balbi
2008-04-09 12:04 ` [PATCH 4/5] I2C: LP5521: Introduce lp5521 LED driver Felipe Balbi
2008-04-09 12:04 ` [PATCH 5/5] ARM: N800: Update n800 defconfig Felipe Balbi
2008-04-09 12:11 ` [PATCH 1/5] I2C: LM8323: Introduce lm8323 keypad driver Felipe Balbi
2008-04-09 17:26 ` andrzej zaborowski
2008-04-09 18:05 ` Felipe Balbi
2008-04-09 18:28 ` Lauri Leukkunen
2008-04-09 23:58 ` andrzej zaborowski
2008-04-10 0:12 ` Daniel Stone
2008-04-10 1:12 ` andrzej zaborowski [this message]
2008-04-14 18:02 ` Tony Lindgren
2008-04-09 20:35 ` Daniel Stone
2008-04-10 13:18 ` andrzej zaborowski
2008-04-10 14:34 ` Felipe Balbi
2008-04-14 18:03 ` [PATCH 0/5] n810 drivers, take #3 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2008-04-09 10:09 [PATCH 0/5] resend n810 drivers Felipe Balbi
2008-04-09 10:09 ` [PATCH 1/5] I2C: LM8323: Introduce lm8323 keypad driver Felipe Balbi
2008-04-09 10:54 ` Eduardo Valentin
2008-04-09 11:02 ` Daniel Stone
2008-04-09 11:33 ` Eduardo Valentin
2008-04-09 10:04 [PATCH 0/5] n810 drivers Felipe Balbi
2008-04-09 10:04 ` [PATCH 1/5] I2C: LM8323: Introduce lm8323 keypad driver Felipe Balbi
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=fb249edb0804091812g77b6fc84x3312ea09c845ea3a@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=daniel.stone@nokia.com \
--cc=edubezval@gmail.com \
--cc=felipe.balbi@nokia.com \
--cc=lauri.leukkunen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=tony@atomide.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