[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171117110057.GD17200@lahna.fi.intel.com>
Date: Fri, 17 Nov 2017 13:00:57 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Chris Chiu <chiu@...lessm.com>
Cc: Daniel Drake <drake@...lessm.com>, heikki.krogerus@...ux.intel.com,
linux-gpio@...r.kernel.org,
Linux Kernel <linux-kernel@...r.kernel.org>,
Endless Linux Upstreaming Team <linux@...lessm.com>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Subject: Re: intel-gpio interrupts stop firing with Focaltech I2C-HID touchpad
On Fri, Nov 17, 2017 at 06:01:27PM +0800, Chris Chiu wrote:
> Hi Mika,
> Here's the full dmesg log you need. The touchpad stop reporting at
> the last of the log.
> https://gist.github.com/mschiu77/a0b8d24a586a228c55eca30c87c71d41
Thanks!
I did not spot anything suspicious in the i2c-hid initialization. When
the issue happens, can you check what the pin state is and if it changes
when you use the touchpad? If I read your ACPI tables right, something
like this:
# grep GPIO_18 /sys/kernel/debug/pinctrl/INT3452:00/pins
(it could be another INT3452:* device as well).
The GPIO line should be high and when the touchpad is pressed it should
go low.
Then another thing, if you unload i2c-hid and load it back, does it
start working again?
# modprobe -r i2c-hid
# modprobe i2c-hid
Powered by blists - more mailing lists