mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Chris Chiu <chiu@endlessm.com>
Cc: Daniel Drake <drake@endlessm.com>,
	heikki.krogerus@linux.intel.com, linux-gpio@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Endless Linux Upstreaming Team <linux@endlessm.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: intel-gpio interrupts stop firing with Focaltech I2C-HID touchpad
Date: Fri, 17 Nov 2017 11:11:34 +0200	[thread overview]
Message-ID: <20171117091134.GB17200@lahna.fi.intel.com> (raw)
In-Reply-To: <CAB4CAwcqxBJNnaS9q7S7dy_1GoR5m1VHY89y+8g-G7rXBBJ1hg@mail.gmail.com>

On Fri, Nov 17, 2017 at 04:27:39PM +0800, Chris Chiu wrote:
> On Thu, Nov 16, 2017 at 9:07 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > On Thu, Nov 16, 2017 at 12:01:24PM +0000, Daniel Drake wrote:
> >> On Thu, Nov 16, 2017 at 11:52 AM, Mika Westerberg
> >> <mika.westerberg@linux.intel.com> wrote:
> >> > Please first check the signal with some analyzator if it works as
> >> > expected and let's then figure out what needs to be fixed and where ;-)
> >>
> >> It works fine under Windows, so I think it's already clear that there
> >> is a Linux bug to be solved here.
> >
> > Can you remove all the "debugging" patches and hacks and then add
> > "i2c_hid.debug=1" to the kernel command line.
> >
> > Then reproduce the issue and send me full dmesg and acpidump of the
> > system. Thanks.
> 
> Hi Mika,
>     Here's the dmesg log which stops at 214th seconds and no more
> further output and archive of "acpidump -b" output files FYI.

Thanks!

The dmesg is not complete, I wonder if you can make the buffer a bit
bigger by increasing CONFIG_LOG_BUF_SHIFT (or get it from
/var/log/messages or so). I would like to see i2c-hid init and related
messages.

>From the acpidump related to the i2c-hid device, the system provides
custom I2C timings via FMCN ACPI method but it misses one value
(sda_hold). Not sure if if has anything to do with the problem, though.
Adding Jarkko in case he has any ideas.

BTW, is this the same machine which has problems in S3 suspend/resume?

  parent reply	other threads:[~2017-11-17  9:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 11:38 Daniel Drake
2017-11-16 11:52 ` Mika Westerberg
2017-11-16 12:01   ` Daniel Drake
2017-11-16 13:07     ` Mika Westerberg
2017-11-17  8:27       ` Chris Chiu
2017-11-17  8:50         ` Chris Chiu
2017-11-17  9:11         ` Mika Westerberg [this message]
2017-11-17  9:13           ` Chris Chiu
2017-11-17 10:01             ` Chris Chiu
2017-11-17 11:00               ` Mika Westerberg
2017-11-17 13:21                 ` Chris Chiu
2017-11-17 13:35                   ` Mika Westerberg
2017-11-17 13:52                     ` Mika Westerberg
2017-11-20  5:18                       ` Chris Chiu
2017-11-20 10:32                         ` Mika Westerberg

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=20171117091134.GB17200@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=chiu@endlessm.com \
    --cc=drake@endlessm.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@endlessm.com \
    /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

all inboxes | Powered by JetHome®