All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Chiu <chiu@endlessm.com>
To: 廖崇榮 <kt.liao@emc.com.tw>
Cc: "Kai-Heng Feng" <kai.heng.feng@canonical.com>,
	linux-input@vger.kernel.org, "黃世鵬 經理" <phoenix@emc.com.tw>
Subject: Re: ASUS G752VS Touchpad does not work
Date: Fri, 5 May 2017 14:41:00 +0800	[thread overview]
Message-ID: <CAB4CAwfJ9t1JF_AcBYmnfHYMDEzujZd93cFXYFbuYMiYJFZ=Vw@mail.gmail.com> (raw)
In-Reply-To: <005601d2c554$64578df0$2d06a9d0$@emc.com.tw>

Hi KT,
    We user kernel version 4.8 when test the G752VSK but it should
work at 4.10 too. I'll verify that later. And yes, there's no ELAN
interrupt at all from the bug report. I would suggest to have the DSDT
for further analysis.

Chris

On Fri, May 5, 2017 at 12:02 PM, 廖崇榮 <kt.liao@emc.com.tw> wrote:
> Hi Chris,
>
>
>
> Thanks, I remember this issue, it’s HID description issue for touchpad’s
> physical button. And it fixed after Benjamin ’s patch
>
> From below link, it seems the probe is ok, so I still guess interrupt maybe
> the problem
>
> https://bugs.launchpad.net/bugs/1653456
>
>
>
> which kernel version do you use for it?,
>
>
>
> Thanks             KT
>
>
>
> From: Chris Chiu [mailto:chiu@endlessm.com]
> Sent: Friday, May 05, 2017 11:45 AM
> To: 廖崇榮
> Cc: Kai-Heng Feng; linux-input@vger.kernel.org; 黃世鵬 經理
>
>
> Subject: Re: ASUS G752VS Touchpad does not work
>
>
>
> Hi KT,
>
>    We only encounter Asus G752VSK: Default touchpad left key and right are
> reversed issue. The touchpad works under hid-multitouch except the
> left/right key reversed. I still have G752VS in hand, please let me know if
> you need any.
>
>
>
> Chris
>
>
>
> On Fri, May 5, 2017 at 11:25 AM, 廖崇榮 <kt.liao@emc.com.tw> wrote:
>
> Add Endlessm's Chris in loop
>
> Hi Chris,
>
> Do you know ASUS G752VS's touchpad issue.
> It's MS PTP, I am not sure if it meet the same problem that interrupt pin
> configure issue?
>
> From your last Acer PTP experience, Your issue seems caused by inconsistent
> INT setting, right?
>
> Could you give some advice to Kai-Heng to check the issue
>
> Thanks  KT
>
>
>
> -----Original Message-----
> From: Kai-Heng Feng [mailto:kai.heng.feng@canonical.com]
> Sent: Thursday, May 04, 2017 5:54 PM
> To: 廖崇榮
> Cc: linux-input@vger.kernel.org
> Subject: Re: ASUS G752VS Touchpad does not work
>
> Hi, KT Liao,
>
> On Thu, May 4, 2017 at 5:47 PM, 廖崇榮 <kt.liao@emc.com.tw> wrote:
>> Hi Kai-Heng
>>
>> -----Original Message-----
>> From: Kai-Heng Feng [mailto:kai.heng.feng@canonical.com]
>> Sent: Thursday, May 04, 2017 3:59 PM
>> To: kt.liao@emc.com.tw; dusonlin@emc.com.tw
>> Cc: linux-input@vger.kernel.org
>> Subject: ASUS G752VS Touchpad does not work
>>
>> Hi KT Liao, Duson Lin,
>>
>> A user reported that the touchpad on ASUS G752VS does not work [1], it's
>> an ELAN touchapd.
>>
>> I did the following change, the touchpad correctly loads elan-i2c instead
>> of hid-multitouch, but it's still not working.
>>
>> [KT] I check the touchpad of this model, it's MS precision touchpad.
>> It must use "hid-multitouch", not "elan-i2c".
>
> Well, the touchpad does not work under hid-multitouch, either. That's why I
> tried to let it load elan-i2c instead.
> What information do you need to investigate this issue?
>
> Thanks.
>
>

  parent reply	other threads:[~2017-05-05  6:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  7:58 ASUS G752VS Touchpad does not work Kai-Heng Feng
2017-05-04  9:47 ` 廖崇榮
2017-05-04  9:54   ` Kai-Heng Feng
2017-05-05  3:25     ` 廖崇榮
     [not found]       ` <CAB4CAwdV0fUOARAZ13TY00s2kxVCw+QzOKd9k2P0m7fBPmhY0w@mail.gmail.com>
     [not found]         ` <005601d2c554$64578df0$2d06a9d0$@emc.com.tw>
2017-05-05  6:41           ` Chris Chiu [this message]
2017-05-05  7:42             ` Kai-Heng Feng
2017-05-05 13:05               ` Chris Chiu
2017-05-08  6:49                 ` Kai-Heng Feng
2017-05-23  9:31                   ` Aljoša
2017-05-29 11:04                   ` Aljoša
2017-06-01 12:22                     ` 廖崇榮
2017-06-01 12:58                       ` Chris Chiu
2017-06-01 16:42                         ` Aljoša
2017-06-05 10:39                         ` Aljoša
2017-06-06  1:59                           ` 廖崇榮
2017-06-07  9:30                             ` Chris Chiu
2017-06-08  8:55                               ` Kai-Heng Feng
2017-06-19 18:38                                 ` Aljoša
     [not found]                                 ` <ef1052e44792273269cd51f48e7f2c99@cromalternativemoney.org>
2017-06-20  4:07                                   ` Chris Chiu
     [not found]                                     ` <783da09eba0db262a9b57ccfef48a70e@cromalternativemoney.org>
2017-06-20 10:06                                       ` Kai-Heng Feng
2017-06-26  6:44                                         ` Aljoša
2017-07-03  9:03                                         ` Aljoša
2017-07-03 10:30                                           ` 廖崇榮
2017-07-04  9:06                                             ` Aljoša
2017-07-06  8:40                                             ` Aljoša
2017-07-11 15:35                                             ` Aljoša
2017-09-22 15:49                                         ` Aljoša

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='CAB4CAwfJ9t1JF_AcBYmnfHYMDEzujZd93cFXYFbuYMiYJFZ=Vw@mail.gmail.com' \
    --to=chiu@endlessm.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kt.liao@emc.com.tw \
    --cc=linux-input@vger.kernel.org \
    --cc=phoenix@emc.com.tw \
    /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.