From: "Pali Rohár" <pali.rohar@gmail.com>
To: Masaki Ota <masaki.ota@jp.alps.com>,
Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: John Preston <wcerfgba@riseup.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Unknown ALPS touchpad
Date: Tue, 21 Feb 2017 09:34:39 +0100 [thread overview]
Message-ID: <20170221083439.GA9795@pali> (raw)
In-Reply-To: <KAWPR01MB1092940E872BB3C233FE8033C7510@KAWPR01MB1092.jpnprd01.prod.outlook.com>
On Tuesday 21 February 2017 03:10:06 Masaki Ota wrote:
> Hi, Pali,
>
> I know these devices, and they are supported in new kernel.
> I'm not sure when they are supported from.
> In alps.c has below code.
>
> static int alps_identify(struct psmouse *psmouse, struct alps_data *priv)
> {...
> ...
> if (e7[0] == 0x73 && e7[1] == 0x03 && e7[2] == 0x50 &&
> ec[0] == 0x73 && (ec[1] == 0x01 || ec[1] == 0x02)) {
> protocol = &alps_v5_protocol_data;
> } else if (ec[0] == 0x88 &&
> ((ec[1] & 0xf0) == 0xb0 || (ec[1] & 0xf0) == 0xc0)) {
> protocol = &alps_v7_protocol_data;}
> }
Ou, sorry I have missed this checks for ec[0] == 0x88.
Marcos, so conclusion is that all those ALPS devices are already
supported by last mainline kernel. So you can close those bug reports.
If you need with git blame you can identify commit in which was support
added and then you can find in which kernel version was particular
commit first time.
>
> E7=73 03 50, EC=73 02 02 <- alps_v5_protocol_data
> E7=73 03 0a, EC=88 b3 22 <- alps_v7_protocol_data
> E7=73 03 0a, EC=88 b3 18 <- alps_v7_protocol_data
>
> Best Regards,
> Masaki Ota
> -----Original Message-----
> From: Pali Rohár [mailto:pali.rohar@gmail.com]
> Sent: Tuesday, February 21, 2017 12:51 AM
> To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>; 太田 真喜 Masaki Ota <masaki.ota@jp.alps.com>
> Cc: John Preston <wcerfgba@riseup.net>; Dmitry Torokhov <dmitry.torokhov@gmail.com>; linux-input@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Unknown ALPS touchpad
>
> Adding Masaki into discussion.
>
> On Sunday 19 February 2017 20:01:07 Marcos Paulo de Souza wrote:
> > There are other open bugs mentioning the same problem, with similar ALPS devices:
> > https://bugzilla.kernel.org/show_bug.cgi?id=57841
>
> Unknown ALPS touchpad: E7=73 03 50, EC=73 02 02
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=43931
>
> Unknown ALPS touchpad: E7=73 00 14, EC=10 00 64
>
> Should be supported since commit 95f75e91 which was introduced in Linux version v3.13-rc4.
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=80181
>
> Unknown ALPS touchpad: E7=73 03 0a, EC=88 b3 22
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=67941
>
> Unknown ALPS touchpad: E7=73 03 0a, EC=88 b3 18
>
> > This one without even a dmesg output:
> > https://bugzilla.kernel.org/show_bug.cgi?id=84081
>
> Sorry, this one does not contain any useful information.
>
> > Maybe they are related, or also need some touch to let them being discovered as proper devices?
>
> Masaki, can you look at those unknown ALPS touchpad identifiers and provide some information about protocol which they are using?
>
> Basically touchpads with these identifiers are unsupported by last kernel version:
>
> E7=73 03 50, EC=73 02 02
> E7=73 03 0a, EC=88 b3 22
> E7=73 03 0a, EC=88 b3 18
>
> --
> Pali Rohár
> pali.rohar@gmail.com
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-02-21 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 13:16 [PATCH] Add model data for Dell Precision 3510 trackpad John L. Preston
2017-02-19 13:35 ` Pali Rohár
2017-02-19 15:24 ` John Preston
2017-02-19 23:01 ` Marcos Paulo de Souza
2017-02-20 15:51 ` Unknown ALPS touchpad Pali Rohár
2017-02-21 3:10 ` Masaki Ota
2017-02-21 8:34 ` Pali Rohár [this message]
2017-02-21 11:05 ` Marcos Paulo de Souza
2017-02-20 15:38 ` [PATCH] Add model data for Dell Precision 3510 trackpad Pali Rohár
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=20170221083439.GA9795@pali \
--to=pali.rohar@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=masaki.ota@jp.alps.com \
--cc=wcerfgba@riseup.net \
/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