Linux Input/HID development
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: kai.heng.feng@canonical.com, xiaojian.cao@cn.alps.com
Cc: masaki.ota@alpsalpine.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, naoki.saito@alpsalpine.com
Subject: RE: Alps touchpad generates IRQ storm after S3
Date: Wed, 28 Aug 2019 13:25:31 +0000	[thread overview]
Message-ID: <39b2e63e339447e8b09b2601abf3d1ba@AUSX13MPC101.AMER.DELL.COM> (raw)
In-Reply-To: <A118551C-A0D9-485F-91F7-44A5BE228B99@canonical.com>

KH,

Just make sure I understand details.

> Commit "HID: i2c-hid: Don't reset device upon system resume

If you revert this it's fixed on this system?

In that commit you had mentioned if this causes problems it might be worth
quirking just Raydium but commit afbb1169ed5b58cfca017e368b53e019cf285853
confirmed that it helped several other systems too.

If the conclusion from this investigation this is only fixable via touchpad FW update
it might be worth quirking this touchpad/touchpad FW/system combination.

> Also Cc Mario because this could relate to BIOS.

Also I assume this is on current stable BIOS/EC release, right?

Thanks,

> -----Original Message-----
> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Sent: Wednesday, August 28, 2019 1:58 AM
> To: Xiaojian Cao
> Cc: Masaki Ota; Limonciello, Mario; open list:HID CORE LAYER; Linux Kernel
> Mailing List; Naoki Saito
> Subject: Re: Alps touchpad generates IRQ storm after S3
> 
> 
> [EXTERNAL EMAIL]
> 
> Hi Xiaojian,
> 
> at 14:51, Xiaojian Cao <xiaojian.cao@cn.alps.com> wrote:
> 
> > Hi Ota-san,
> >
> > OK, we will look into it.
> >
> >
> > Hi Kai-Heng,
> >
> > We will try to reproduce this issue first, could you please tell me the
> > target Ubuntu version?
> 
> It’s distro-agnostic, any distro with mainline Linux can reproduce the issue.
> 
> Kai-Heng
> 
> >
> > Best regards,
> > Jason
> >
> > -----Original Message-----
> > From: 太田 真喜 Masaki Ota <masaki.ota@alpsalpine.com>
> > Sent: Wednesday, August 28, 2019 2:35 PM
> > To: 曹 曉建 Xiaojian Cao <xiaojian.cao@cn.alps.com>; Kai-Heng Feng
> > <kai.heng.feng@canonical.com>
> > Cc: Mario Limonciello <mario.limonciello@dell.com>; open list:HID CORE
> > LAYER <linux-input@vger.kernel.org>; Linux Kernel Mailing List
> > <linux-kernel@vger.kernel.org>; 斉藤 直樹 Naoki Saito
> > <naoki.saito@alpsalpine.com>
> > Subject: RE: Alps touchpad generates IRQ storm after S3
> >
> > Hi, Kai-Heng,
> >
> > Sorry, I'm not in charge of Linux task now.
> >
> > Hi, XiaoJian,
> >
> > Please check the following mail.
> > If you have any question, please ask Kai-Heng.
> >
> > Best Regards,
> > Masaki Ota
> > -----Original Message-----
> > From: Kai-Heng Feng <kai.heng.feng@canonical.com>
> > Sent: Wednesday, August 28, 2019 3:22 PM
> > To: 太田 真喜 Masaki Ota <masaki.ota@alpsalpine.com>
> > Cc: Mario Limonciello <mario.limonciello@dell.com>; open list:HID CORE
> > LAYER <linux-input@vger.kernel.org>; Linux Kernel Mailing List
> > <linux-kernel@vger.kernel.org>
> > Subject: Alps touchpad generates IRQ storm after S3
> >
> > Hi Masaki,
> >
> > The Alps touchpad (044E:1220) on Dell Precision 7530 causes IRQ storm
> > after system suspend (S3).
> > Commit "HID: i2c-hid: Don't reset device upon system resume” which solves
> > the same issue for other vendors, cause the issue on Alps touchpad.
> > So I’d like to know the correct command Alps touchpad expects after
> > system resume.
> >
> > Also Cc Mario because this could relate to BIOS.
> >
> > Kai-Heng
> 


  reply	other threads:[~2019-08-28 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  6:22 Alps touchpad generates IRQ storm after S3 Kai-Heng Feng
2019-08-28  6:35 ` Masaki Ota
2019-08-28  6:51   ` Xiaojian Cao
2019-08-28  6:58     ` Kai-Heng Feng
2019-08-28 13:25       ` Mario.Limonciello [this message]
2019-08-28 14:43         ` Kai-Heng Feng
2019-09-25 10:01           ` Kai-Heng Feng

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=39b2e63e339447e8b09b2601abf3d1ba@AUSX13MPC101.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masaki.ota@alpsalpine.com \
    --cc=naoki.saito@alpsalpine.com \
    --cc=xiaojian.cao@cn.alps.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