Hi KT,
Yes, I've hit the interrupt type setting issues in Acer laptops.
If the interrupt type setting is wrong in the BIOS, the touchpad will
stop working after a while (often ~10 seconds). The interrupt numbers
observed will be a lot more than expected when touchpad is still
working which cause i2c read lots of dummy data, then never increase
when the touchpad stop responding. I believe it's something very
similar. Please do "sudo cat
/sys/kernel/debug/hid/0018:04F3:3043.0007/events" before your touchpad
dead to see if there's still outputs even you never touch the
touchpad. If the data keeps coming, that means the interrupt type
setting should go wrong.
Chris
On Thu, Jun 1, 2017 at 8:22 PM, 廖崇榮 <kt.liao@xxxxxxxxxx> wrote:
> Hi Chris,
>
> His Interrupt is fasteoi, I guess it's kind of level trigger.
>
> I remember that you debug for an Acer PTP which cause touchpad no function sometimes.
> And it works fine after interrupt modified to edge trigger.
>
> What's your comment?
>
> Thanks KT
> -----Original Message-----
> From: Aljoša [mailto:aljosa@xxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Monday, May 29, 2017 7:04 PM
> To: Kai-Heng Feng
> Cc: Chris Chiu; 廖崇榮; linux-input@xxxxxxxxxxxxxxx; 黃世鵬 經理
> Subject: Re: ASUS G752VS Touchpad does not work
>
> Hello,just installed new kernel 4.12-rc3.
> ELAN touchpad is still completely dead on my ASUS G752VS.
> Complete dmesg output (comment #68) and complete output (comment #69) of ~$ cat /proc/interrupts attached here:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456
>
> ~$ dmesg
>
> [5.149761] i2c_hid i2c-ELAN1203:00: i2c-ELAN1203:00 supply vdd not found, using dummy regulator [5.191090] hid-multitouch 0018:04F3:3043.0007: Ignoring the extra HID_DG_INPUTMODE [5.191133] input: ELAN1203:00 04F3:3043 Touchpad as
> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input16
> [5.191230] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID
> v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00
>
> ~$ cat /proc/interrupts
>
> 16: 0 0 0 0 0 0
> 0 0 IR-IO-APIC 16-fasteoi idma64.0, i2c_designware.0
> 17: 709 9839 0 0 0 0
> 0 0 IR-IO-APIC 17-fasteoi idma64.1, i2c_designware.1
> 95: 1 552 0 0 0 0
> 0 0 IR-IO-APIC 95-fasteoi ELAN1203:00
>
> ~$ xinput list
> ⎡ Virtual core pointer id=2 [master pointer (3)]
> ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
> ⎜ ↳ G-SPY USB Gaming Mouse id=11 [slave pointer (2)]
> ⎜ ↳ Asus Keyboard id=14 [slave pointer (2)]
> ⎜ ↳ Asus Keyboard id=15 [slave pointer (2)]
> ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=16 [slave pointer (2)]
> ⎣ Virtual core keyboard id=3 [master keyboard (2)]
> ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
> ↳ Power Button id=6 [slave keyboard (3)]
> ↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
> ↳ Video Bus id=8 [slave keyboard (3)]
> ↳ Sleep Button id=9 [slave keyboard (3)]
> ↳ G-SPY USB Gaming Mouse id=10 [slave keyboard (3)]
> ↳ USB2.0 HD UVC WebCam id=12 [slave keyboard (3)]
> ↳ Asus Keyboard id=13 [slave keyboard (3)]
> ↳ Asus WMI hotkeys id=17 [slave keyboard (3)]
> ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)]
> ↳ G-SPY USB Gaming Mouse id=19 [slave keyboard (3)]
> ↳ Asus Keyboard id=20 [slave keyboard (3)]
>
>
>
> On 2017-05-08 08:49, Kai-Heng Feng wrote:
>> Hi aljosa,
>>
>> On Fri, May 5, 2017 at 9:05 PM, Chris Chiu <chiu@xxxxxxxxxxxx> wrote:
>>> I read the whole threads. It's normal there's no interrupt observed
>>> if using elan_i2c driver. It should use hid-multitouch.
>>>
>>> I would like to know if there's any interrupts observed when it load
>>> hid-multitouch driver instead of elan_i2c driver.
>>>
>>> Something noted here, on my G752VSK the input device shows as
>>> ELAN1200 not ELAN1203. Although I think it should make no difference,
>>> just to note that my machine maybe a little different from the bug reporter's.
>>>
>>
>> Can you provide information Chris asked?
>> His G752 uses a slightly different touchpad so more information is
>> needed.
>>
>> Thanks!
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
