From: Vojtech Pavlik <vojtech@suse.cz>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: Half second spend in i8042 during suspend on TUXEDO BU1406
Date: Thu, 9 Feb 2017 00:58:26 +0100 [thread overview]
Message-ID: <20170208235826.GA28058@suse.com> (raw)
In-Reply-To: <234cc57f-6922-d866-e457-66eb2cafb85d@molgen.mpg.de>
On Wed, Feb 08, 2017 at 02:12:44PM +0100, Paul Menzel wrote:
> On the TUXEDO BU1406 [1] the Linux kernel (tested with 4.10-rc{6,7})
> takes over a second to get into suspend [2]. For whatever reason
> around 550 ms are spent in `i8042_set_mux_mode()` (cf. attached
> /*
> * Internal loopback test - send three bytes, they should come back
> from the
> * mouse interface, the last should be version.
> */
>
> param = val = 0xf0;
> if (i8042_command(¶m, I8042_CMD_AUX_LOOP) || param != val)
> return -1;
> param = val = multiplex ? 0x56 : 0xf6;
> if (i8042_command(¶m, I8042_CMD_AUX_LOOP) || param != val)
> return -1;
> param = val = multiplex ? 0xa4 : 0xa5;
> if (i8042_command(¶m, I8042_CMD_AUX_LOOP) || param == val)
> return -1;
> ```
>
> Is that a hardware limitation, or even an error as such long delays
> are not allowed according to some standard?
It looks like an EC firmware bug not handling the CMD_AUX_LOOP command
correctly.
> Is there anything, that can be done about this, to get into S3 state faster?
Does it still happen if you specify i8042.nomux=1 on the kernel command
line?
If that helps, it can be added to a blacklist based on DMI.
Vojtech
next prev parent reply other threads:[~2017-02-09 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <234cc57f-6922-d866-e457-66eb2cafb85d@molgen.mpg.de>
2017-02-08 13:33 ` Half second spend in i8042 during suspend on TUXEDO BU1406 Paul Menzel
2017-02-08 23:58 ` Vojtech Pavlik [this message]
2017-02-09 9:17 ` Paul Menzel
2017-02-09 11:24 ` Vojtech Pavlik
2017-02-09 16:07 ` Paul Menzel
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=20170208235826.GA28058@suse.com \
--to=vojtech@suse.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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;
as well as URLs for NNTP newsgroup(s).