From: Pavel Machek <pavel@ucw.cz>
To: Mike Rapoport <mike@compulab.co.il>
Cc: Eric Miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
kernel list <linux-kernel@vger.kernel.org>,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] [ARM] pxa/em-x270: add synaptics_i2c touchpad
Date: Fri, 21 Aug 2009 16:16:14 +0200 [thread overview]
Message-ID: <20090821141614.GC1456@ucw.cz> (raw)
In-Reply-To: <4A792913.8040006@compulab.co.il>
Hi!
> >>>>> This patch set adds synaptics_i2c touchpad device registration for the exeda
> >>>>> platform together with voltage reulator glue needed to enable the touchpad
> >>>>> controller.
> >>>>>
> >>> Hmm, t-mobile g1 uses synaptics touchpad connected over i2c, too... Is
> >>> there chance they are compatible or at least similar?
> >> The touchpad controller I have uses the same RMI protocol that g1 does, but it
> >> supports different register set. Besides, g1 has a *touchscreen* and exeda has
> >> 1.5cm x 1.5cm *touchpad*.
> >
> > Can we get some code shared? It still looks similar enough.
>
> The controller detection and basic initialization (report rate, filtering, Z
> Clip) seems to be the same. But afterwards things begin to diverge. For
> instance, g1 reads and parses 15 bytes of data, whilst my touchpad has only 9
> data registers.
> It seems to me that it should be possible to share initialization and basic
> register access, and have different work functions and input events reporting.
>
> Probably if we had full implementation of Synaptics RMI protocol we could have
> single driver for all RMI-compatible Synaptics devices. RMI states that device
> can report what functionality it supports and based on that it should be
> possible to provide appropriate event parsing and reporting.
Thanks for info. It seems like merging them is project far ahead...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-08-21 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1245156138.git.mike@compulab.co.il>
[not found] ` <4A65207A.8070909@gmail.com>
[not found] ` <20090729150859.GK1534@ucw.cz>
[not found] ` <4A7071CD.9020303@compulab.co.il>
2009-08-04 13:14 ` [PATCH] [ARM] pxa/em-x270: add synaptics_i2c touchpad Pavel Machek
2009-08-05 6:39 ` Mike Rapoport
2009-08-21 14:16 ` Pavel Machek [this message]
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=20090821141614.GC1456@ucw.cz \
--to=pavel@ucw.cz \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@compulab.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.