From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Linux Input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] Input: synaptics - set minimum coordinates as reported by firmware
Date: Mon, 25 Jul 2011 01:37:52 -0700 [thread overview]
Message-ID: <20110725083752.GE22937@core.coreip.homeip.net> (raw)
In-Reply-To: <CAGS+omBkpcVU29e4mK-HK838EiGhjbicuUkE8+yY2auQ01ZibQ@mail.gmail.com>
On Wed, Jul 20, 2011 at 07:20:40PM +0800, Daniel Kurtz wrote:
> Sorry, I fear I am too late, but...
>
> On Thu, Jul 7, 2011 at 2:57 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> >
> > Newer Synaptics firmware allows to query minimum coordinates reported by
> > the device, let's use this data.
> >
> > Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> > ---
> >
> > drivers/input/mouse/synaptics.c | 56 ++++++++++++++++++++++++++-------------
> > drivers/input/mouse/synaptics.h | 8 ++++--
> > 2 files changed, 43 insertions(+), 21 deletions(-)
>
> [...snip...]
>
> > diff --git a/drivers/input/mouse/synaptics.h b/drivers/input/mouse/synaptics.h
> > index b8025b0..a4394e1 100644
> > --- a/drivers/input/mouse/synaptics.h
> > +++ b/drivers/input/mouse/synaptics.h
> > @@ -19,7 +19,8 @@
> > #define SYN_QUE_RESOLUTION 0x08
> > #define SYN_QUE_EXT_CAPAB 0x09
> > #define SYN_QUE_EXT_CAPAB_0C 0x0c
> > -#define SYN_QUE_EXT_DIMENSIONS 0x0d
> > +#define SYN_QUE_EXT_MAX_COORDS 0x0d
> > +#define SYN_QUE_EXT_MIN_COORDS 0x0f
> >
> > /* synatics modes */
> > #define SYN_BIT_ABSOLUTE_MODE (1 << 7)
> > @@ -73,10 +74,12 @@
> > * 2 0x04 reduced filtering firmware does less filtering on
> > * position data, driver should watch
> > * for noise.
> > + * 2 0x20 report min query 0x0f gives min coord reported
> > */
> > #define SYN_CAP_CLICKPAD(ex0c) ((ex0c) & 0x100000) /* 1-button ClickPad */
> > #define SYN_CAP_CLICKPAD2BTN(ex0c) ((ex0c) & 0x000100) /* 2-button ClickPad */
> > #define SYN_CAP_MAX_DIMENSIONS(ex0c) ((ex0c) & 0x020000)
> > +#define SYN_CAP_MIN_DIMENSIONS(ex0c) ((ex0c) & 0x000200)
>
> I believe "Byte 2, 0x20" is actually 0x002000, not 0x000200.
> It would appear that the documentation is inconsistent with
> implementation; and, the implementation conflicts with the heretofore
> unused "deluxe LED controls" bit.
>
You are right, thanks for noticing. Should be fixed now.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-07-25 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 6:57 [PATCH] Input: synaptics - set minimum coordinates as reported by firmware Dmitry Torokhov
2011-07-08 16:05 ` Chase Douglas
2011-07-08 17:34 ` Henrik Rydberg
2011-07-20 11:20 ` Daniel Kurtz
2011-07-25 8:37 ` Dmitry Torokhov [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=20110725083752.GE22937@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=djkurtz@chromium.org \
--cc=linux-input@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).