From: Eric Miao <eric.y.miao@gmail.com>
To: Paul Parsons <lost.distance@yahoo.com>
Cc: pavel@ucw.cz, rpurdie@rpsys.net, lenz@cs.wisc.edu,
linux-kernel@vger.kernel.org, Dirk@opfer-online.de,
arminlitzel@web.de, metan@ucw.cz, thommycheck@gmail.com,
linux-arm-kernel@lists.infradead.org, dbaryshkov@gmail.com,
omegamoon@gmail.com, utx@penguin.cz
Subject: Re: [PATCH] hx4700: fix hx4700 touchscreen pressure values
Date: Wed, 18 Nov 2009 11:03:38 +0800 [thread overview]
Message-ID: <f17812d70911171903v230b1598mc8e5ff2a4b5195b8@mail.gmail.com> (raw)
In-Reply-To: <E1NAYJo-00016g-PW@pih-relay04.plus.net>
On Wed, Nov 18, 2009 at 8:22 AM, Paul Parsons <lost.distance@yahoo.com> wrote:
>> Does pressure actually work as expected -- that is not inverted?
>> Because I need this patch on spitz... but it may break your
>> machine...
>
> You are right, the pressure values were being inverted on my hx4700.
> Pressing hard generates somewhat lower Rt values than pressing lightly.
>
> Since typical hx4700 Rt values are close to (pressure_max/2) anyway,
> the inverted and non-inverted values were not very different.
> For example:
>
> Rt ts->pressure_max-Rt
> 599 425
> 562 462
> 588 436
> 570 454
>
> So by all means submit your ads7846.c patch; it will not break hx4700.
>
Is this generically true that the pressure is always inverted? Otherwise
a platform specific field indicating this would be the better way to go.
- eric
next prev parent reply other threads:[~2009-11-18 3:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 0:22 Paul Parsons
2009-11-18 3:03 ` Eric Miao [this message]
2009-11-18 17:28 ` Pavel Machek
2009-11-18 17:39 ` Dmitry Torokhov
2009-11-18 17:46 ` Pavel Machek
2009-11-18 17:46 ` Dmitry Torokhov
2009-11-20 18:24 ` Pavel Machek
[not found] <E1N9Lt7-0007mK-2t@relay07.plus.net>
2009-11-17 11:45 ` Pavel Machek
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=f17812d70911171903v230b1598mc8e5ff2a4b5195b8@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=Dirk@opfer-online.de \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lost.distance@yahoo.com \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
/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
all inboxes | Powered by JetHome®