mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masaki Ota <masaki.ota@alpsalpine.com>
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
Date: Wed, 28 Aug 2019 06:35:15 +0000	[thread overview]
Message-ID: <TYAPR01MB30223CB8A576C7809F6382C1ECA30@TYAPR01MB3022.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <44F93018-5F13-4932-A5AC-9D288CDF68DD@canonical.com>

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  6:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  6:22 Kai-Heng Feng
2019-08-28  6:35 ` Masaki Ota [this message]
2019-08-28  6:51   ` Xiaojian Cao
2019-08-28  6:58     ` Kai-Heng Feng
2019-08-28 13:25       ` Mario.Limonciello
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=TYAPR01MB30223CB8A576C7809F6382C1ECA30@TYAPR01MB3022.jpnprd01.prod.outlook.com \
    --to=masaki.ota@alpsalpine.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@dell.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
all inboxes | Powered by JetHome®