From: Tj <linux@iam.tj>
To: linux-input@vger.kernel.org
Subject: Re: HID: asus: Add T100CHI bluetooth keyboard dock touchpad support
Date: Tue, 14 Nov 2017 20:09:00 +0000 [thread overview]
Message-ID: <1ac0aab543099ef88f71b44193e1cf30@iam.tj> (raw)
With kernel v4.14 on an Asus T300CHI this appears to be working up to a
point but it causes the touchpad to FAIL to work on earlier kernels.
The touchpad seems to be in multitouch mode (two-finger scrolling is
the
only MT action I've confirmed so far) but there are some deficiencies.
For instance, single or double-tap on the touchpad, or tapping the
left/right 'button' regions doesn't work.
This touchpad is overlaid on a physical 'click' button surface (which I
suspect operates as the mouse). By this I mean instead of lightly
tapping the touchpad surface it needs a very firm downward movement
until a physical 'click' is heard. It resists quite strongly so
double-clicks in particular are difficult. There's a separate physical
'click' area for the right button.
So it works with these hard physical 'click' actions but not when
tapping the touchpad surface. To compare with the behaviour under
previous kernels (where I seem to recall it only needed touchpad taps) I
rebooted into an earlier kernel.
The disturbing FAILURE is that if the T300CHI is rebooted - even if
from a poweroff - into an earlier kernel version (than v4.14) the
touchpad no longer works.
Using hid-recorder I saw that the touchpad is still in multitouch mode
(event descriptor id 0x5D rather than 0x06 when doing multitouches).
So far I've not been able to find a way to workaround/fix this. On the
face of it the driver needs to put the touchpad back into 'mouse' mode
on shutdown.
next reply other threads:[~2017-11-14 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 20:09 Tj [this message]
2017-11-15 10:38 ` HID: asus: Add T100CHI bluetooth keyboard dock touchpad support Tj
2017-11-15 10:56 ` Hans de Goede
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=1ac0aab543099ef88f71b44193e1cf30@iam.tj \
--to=linux@iam.tj \
--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).