From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: intel-gpio interrupts stop firing with Focaltech I2C-HID touchpad Date: Fri, 17 Nov 2017 13:00:57 +0200 Message-ID: <20171117110057.GD17200@lahna.fi.intel.com> References: <20171116115244.GQ17200@lahna.fi.intel.com> <20171116130743.GT17200@lahna.fi.intel.com> <20171117091134.GB17200@lahna.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mga07.intel.com ([134.134.136.100]:48484 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753151AbdKQLBJ (ORCPT ); Fri, 17 Nov 2017 06:01:09 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: Chris Chiu Cc: Daniel Drake , heikki.krogerus@linux.intel.com, linux-gpio@vger.kernel.org, Linux Kernel , Endless Linux Upstreaming Team , Jarkko Nikula 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