From: Stelian Pop <stelian@popies.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Frank Arnold <frank@scirocco-5v-turbo.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Andrew Morton <akpm@osdl.org>,
Peter Osterlund <petero2@telia.com>
Subject: Re: [PATCH] Apple USB Touchpad driver (new)
Date: Mon, 11 Jul 2005 14:47:53 +0200 [thread overview]
Message-ID: <1121086073.5021.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20050711112121.GA24345@ucw.cz>
Le lundi 11 juillet 2005 à 13:21 +0200, Vojtech Pavlik a écrit :
> On Mon, Jul 11, 2005 at 01:08:35PM +0200, Stelian Pop wrote:
>
> > Possible. The 'fuzz' parameter in input core serves too many usages
> > ihmo. Let me try removing the quick motion compensation and see...
>
> It was designed for joysticks and works very well for them. Usefulness
> for other device types may vary. And I'll gladly accept patches to
> improve it.
Ok, I understand now what is happenning, but I'm not sure how to solve
the problem. As I suspected, it is caused by 'fuzz' being a bit abused
by the input core.
The fuzz parameter in the input core is used today to say:
* any change in the -fuzz/2 / +fuzz/2 range is ignored
* any change in the -fuzz / +fuzz range is smoothed using x_old * 3 +
x) / 4;
* any change in the -fuzz*2 / +fuzz/2 range is smoothed using x_old
+x) / 2;
My driver needs to ignore changes in the -8 / +8 range (that's why I set
FUZZ to 16 in the first place), but it needs to smooth the movement when
much larger changes occur (I would need to set FUZZ to 64 for smoothing
to work correctly here).
How to make it work ? Obviously I could implement either fuzz
elimination or smoothing in the driver, and leave the other
transformation to the input core (today it is the smoothing which is in
the driver, but doing it the other way around would result in much less
code).
The other (proper ?) solution would be to change the input core and
separate fuzz and smoothing. This would however require an API addition,
and I'm not sure you want to do that. If you do, I could work on a patch
implementing an inputdev->abssmooth[] table, etc).
> > I thought the hardware is capable of calculating real pressure...
>
> Since the sensor is just a multi-layer PCB with a clever trace layout,
> it can't.
>
> > > > I don't think this value is reliable enough to be reported to the
> > > > userspace as ABS_PRESSURE...
> > >
> > > I believe it'd still be more useful than a two-value (0 and 100) output.
> >
> > Ok, I'll do it.
>
> Thanks. Should I wait for that or apply the patch you just sent?
Well, it depends on what we do with smoothing.
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2005-07-11 12:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 10:17 [PATCH] Apple USB Touchpad driver (new) Stelian Pop
2005-07-08 11:18 ` Johannes Berg
2005-07-08 12:10 ` Stelian Pop
2005-07-09 19:13 ` Vojtech Pavlik
2005-07-09 22:48 ` Peter Osterlund
2005-07-10 12:04 ` Vojtech Pavlik
2005-07-11 0:15 ` Peter Osterlund
2005-07-11 10:39 ` Stelian Pop
2005-07-11 11:00 ` Vojtech Pavlik
2005-07-11 11:08 ` Stelian Pop
2005-07-11 11:21 ` Vojtech Pavlik
2005-07-11 12:47 ` Stelian Pop [this message]
2005-07-11 13:35 ` Stelian Pop
2005-07-12 9:05 ` Stelian Pop
2005-07-12 14:13 ` Dmitry Torokhov
2005-07-12 14:33 ` Stelian Pop
2005-07-12 14:47 ` Dmitry Torokhov
2005-07-12 18:13 ` Vojtech Pavlik
2005-07-12 19:21 ` Stelian Pop
[not found] ` <20050711035244.115067ac.akpm@osdl.org>
2005-07-11 11:04 ` Stelian Pop
2005-07-11 13:25 ` Peter Osterlund
2005-07-11 20:44 ` Lee Revell
2005-07-11 20:54 ` Stelian Pop
2005-07-11 13:48 ` Peter Osterlund
2005-07-11 10:47 ` Vojtech Pavlik
2005-07-09 22:32 ` Peter Osterlund
2005-07-10 11:58 ` Vojtech Pavlik
2005-07-11 10:06 ` Stelian Pop
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=1121086073.5021.16.camel@localhost.localdomain \
--to=stelian@popies.net \
--cc=akpm@osdl.org \
--cc=frank@scirocco-5v-turbo.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=vojtech@suse.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