From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "João Paulo Rechi Vita" <jprvita@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"Duson Lin" <dusonlin@emc.com.tw>,
"João Paulo Rechi Vita" <jprvita@endlessm.com>
Subject: Re: [PATCH] elan_i2c: Add ACPI ID "ELAN1000"
Date: Thu, 3 Sep 2015 10:06:00 -0700 [thread overview]
Message-ID: <20150903170600.GB17498@dtor-ws> (raw)
In-Reply-To: <CA+A7VXUXnNghu5ZCJoWo=w1vBpx43hy5AeypxJtxOVfMkhtt5Q@mail.gmail.com>
On Tue, Sep 01, 2015 at 05:15:55PM -0400, João Paulo Rechi Vita wrote:
> Hello Dmitry, thanks for the feedback.
>
> On 1 September 2015 at 17:00, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > On Tue, Sep 1, 2015 at 12:53 PM, João Paulo Rechi Vita
> > <jprvita@gmail.com> wrote:
> >> This ACPI ID present in the DSDT of the ASUS E202SA laptop.
> >
> > Can it be driven buy the standard hid-multitouch by any chance?
> >
>
> Without this change on v4.2 it is driven by i2c_hid, but behaves as a
> regular mouse, so no absolute events, multitouch, tap to click etc. I
> have not tried to use hid-multitouch with this touchpad, as I thought
> hid-multitouch was a touchscreen driver. Is there any drawback in
> having this supported by elan_i2c? Should I try a different approach?
No, that is fine, I was just checking. Applied, thank you.
--
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:[~2015-09-03 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 19:53 [PATCH] elan_i2c: Add ACPI ID "ELAN1000" João Paulo Rechi Vita
2015-09-01 21:00 ` Dmitry Torokhov
2015-09-01 21:15 ` João Paulo Rechi Vita
2015-09-03 17:06 ` 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=20150903170600.GB17498@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=dusonlin@emc.com.tw \
--cc=jprvita@endlessm.com \
--cc=jprvita@gmail.com \
--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