From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: chase.douglas@canonical.com, rydberg@euromail.se,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
olofj@chromium.org, chris@cnpbagwell.com
Subject: Re: [PATCH 4/9 v4] Input: synaptics - add image sensor support
Date: Sun, 21 Aug 2011 21:28:22 -0700 [thread overview]
Message-ID: <20110822042822.GA23010@core.coreip.homeip.net> (raw)
In-Reply-To: <CAGS+omCZSjJoESSvimLEpj9Mwr3d9Vn78e1ZLk-NWEdgQbxNKw@mail.gmail.com>
On Sat, Aug 20, 2011 at 03:07:41PM +0800, Daniel Kurtz wrote:
> On Sat, Aug 20, 2011 at 6:22 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > Hi Daniel,
> >
> > On Thu, Aug 18, 2011 at 07:28:03PM +0800, Daniel Kurtz wrote:
> >> @@ -558,6 +626,11 @@ static void synaptics_process_packet(struct psmouse *psmouse)
> >> if (synaptics_parse_hw_state(psmouse->packet, priv, &hw))
> >> return;
> >>
> >> + if (SYN_CAP_IMAGE_SENSOR(priv->ext_cap_0c)) {
> >> + synaptics_image_sensor_process(psmouse, &hw);
> >> + return;
> >> + }
> >> +
> >
> > So what about the rest of the SYnaptics processing (wheel, additional
> > buttons, etc)? Are we sure that touchpads with image sensors will never
> > implement them?
> >
> > --
> > Dmitry
> >
>
> All image sensors that I am aware of are clickpads, with one button
> integrated under the pad, which is reported as the middle button.
>
> We could report right, middle, up, down, and ext_buttons (scroll is
> not possible, since w=2;buf[1] is used for x for devices that send agm
> packets).
> However, I have no way of knowing if this added complexity is
> necessary
I would prefer us supporting full protocol so if some vendor does add
additional buttons we have everything in place.
> , nor any way of testing it.
As long as your case still works I think it will be good enough.
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
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: chase.douglas@canonical.com, rydberg@euromail.se,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
olofj@chromium.org, chris@cnpbagwell.com
Subject: Re: [PATCH 4/9 v4] Input: synaptics - add image sensor support
Date: Sun, 21 Aug 2011 21:28:22 -0700 [thread overview]
Message-ID: <20110822042822.GA23010@core.coreip.homeip.net> (raw)
In-Reply-To: <CAGS+omCZSjJoESSvimLEpj9Mwr3d9Vn78e1ZLk-NWEdgQbxNKw@mail.gmail.com>
On Sat, Aug 20, 2011 at 03:07:41PM +0800, Daniel Kurtz wrote:
> On Sat, Aug 20, 2011 at 6:22 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > Hi Daniel,
> >
> > On Thu, Aug 18, 2011 at 07:28:03PM +0800, Daniel Kurtz wrote:
> >> @@ -558,6 +626,11 @@ static void synaptics_process_packet(struct psmouse *psmouse)
> >> if (synaptics_parse_hw_state(psmouse->packet, priv, &hw))
> >> return;
> >>
> >> + if (SYN_CAP_IMAGE_SENSOR(priv->ext_cap_0c)) {
> >> + synaptics_image_sensor_process(psmouse, &hw);
> >> + return;
> >> + }
> >> +
> >
> > So what about the rest of the SYnaptics processing (wheel, additional
> > buttons, etc)? Are we sure that touchpads with image sensors will never
> > implement them?
> >
> > --
> > Dmitry
> >
>
> All image sensors that I am aware of are clickpads, with one button
> integrated under the pad, which is reported as the middle button.
>
> We could report right, middle, up, down, and ext_buttons (scroll is
> not possible, since w=2;buf[1] is used for x for devices that send agm
> packets).
> However, I have no way of knowing if this added complexity is
> necessary
I would prefer us supporting full protocol so if some vendor does add
additional buttons we have everything in place.
> , nor any way of testing it.
As long as your case still works I think it will be good enough.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-08-22 4:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 11:27 [PATCH 0/9 v4] Synaptics image sensor support Daniel Kurtz
2011-08-18 11:28 ` [PATCH 1/9 v4] Input: synaptics - refactor y inversion Daniel Kurtz
2011-08-18 11:28 ` [PATCH 2/9 v4] Input: synaptics - refactor agm packet parsing Daniel Kurtz
2011-08-18 11:28 ` [PATCH 3/9 v4] Input: synaptics - refactor initialization of abs position axes Daniel Kurtz
2011-08-18 11:28 ` [PATCH 4/9 v4] Input: synaptics - add image sensor support Daniel Kurtz
2011-08-18 16:00 ` Chase Douglas
2011-08-19 22:22 ` Dmitry Torokhov
2011-08-20 7:07 ` Daniel Kurtz
2011-08-20 7:07 ` Daniel Kurtz
2011-08-22 4:28 ` Dmitry Torokhov [this message]
2011-08-22 4:28 ` Dmitry Torokhov
2011-08-18 11:28 ` [PATCH 5/9 v4] Input: synaptics - decode AGM packet types Daniel Kurtz
2011-08-18 11:28 ` [PATCH 6/9 v4] Input: mt - document devices reporting more touches than slots Daniel Kurtz
2011-08-18 16:01 ` Chase Douglas
2011-08-18 11:28 ` [PATCH 7/9 v4] Input: synaptics - process finger (<=3) transitions Daniel Kurtz
2011-08-18 16:02 ` Chase Douglas
2011-08-18 11:28 ` [PATCH 8/9 v4] Input: add BTN_TOOL_QUINTTAP for reporting 5 fingers on touchpad Daniel Kurtz
2011-08-18 11:28 ` [PATCH 9/9 v4] Input: synaptics - process finger (<=5) transitions Daniel Kurtz
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=20110822042822.GA23010@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=djkurtz@chromium.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=rydberg@euromail.se \
/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.