From: Jiri Kosina <jkosina@suse.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, hschaa@novell.com
Subject: i8042 resume timing
Date: Mon, 26 May 2008 15:19:00 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805261509250.6718@jikos.suse.cz> (raw)
Hi Dmitry,
There are systems [1] that fail in i8042_resume(), as
i8042_command(&i8042_ctr, I8042_CMD_CTL_WCTR) call returns error (not sure
about the exact error yet, the reporter didn't yet collect i8042.debug
output during the failure, as it is not completely reproducible), but
retrying after small amount of time succeeds.
Looks like a buggy hardware to me, which we should workaround. Would you
prefer DMI-based match for this retry logic with respect to CTR register
on the resume path, or would you accept this as a general retry logic on
resume path? (which is very probably not needed on vast majority of
systems though).
Thanks.
[1] https://bugzilla.novell.com/show_bug.cgi?id=351119
--
Jiri Kosina
SUSE Labs
next reply other threads:[~2008-05-26 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 13:19 Jiri Kosina [this message]
2008-05-26 16:35 ` i8042 resume timing Dmitry Torokhov
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=Pine.LNX.4.64.0805261509250.6718@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=hschaa@novell.com \
--cc=linux-input@vger.kernel.org \
/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).