From: Daniel Stone <daniel.stone@nokia.com>
To: ext Felipe Balbi <me@felipebalbi.com>
Cc: andrzej zaborowski <balrogg@gmail.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: Wed, 9 Apr 2008 23:35:26 +0300 [thread overview]
Message-ID: <20080409203526.GY3842@intune.research.nokia.com> (raw)
In-Reply-To: <20080409180557.GA15913@kedavra.cpe.vivax.com.br>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Wed, Apr 09, 2008 at 09:05:58PM +0300, ext Felipe Balbi wrote:
> On Wed, Apr 09, 2008 at 07:26:31PM +0200, andrzej zaborowski wrote:
> > Question not really related to this patchset, but in the TSC2005
> > driver some averaging and limit checks are done to the ADC values.
> > Shouldn't that be done in userspace instead? (The ADS784x and TSC2301
> > drivers do the same evidently.)
>
> Now that's not really up to me, but if we move it now it probably won't
> provide the feature n810 needs. I mean, n810 is designed on top of the
> features provided by driver, the application probably expects the driver
> to do the averaging and limit checks so at least for tsc2005 I think
> it's not a good idea to change due to application requirements.
It's specific to the device (and device _build_): the actual
touchscreen, and how it's working in the device, so a combination of LCD
driver and board files sounds best to me.
Cheers,
Daniel
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-09 20:34 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
2008-04-14 18:02 ` Tony Lindgren
2008-04-09 20:35 ` Daniel Stone [this message]
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=20080409203526.GY3842@intune.research.nokia.com \
--to=daniel.stone@nokia.com \
--cc=balrogg@gmail.com \
--cc=edubezval@gmail.com \
--cc=felipe.balbi@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