From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Peter Urbanec <vger.kernel.org.input@urbanec.net>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: Issues detecting i8042 AUX port
Date: Thu, 29 Oct 2009 10:02:16 -0700 [thread overview]
Message-ID: <200910291002.16733.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <4AE989D0.1070302@urbanec.net>
On Thursday 29 October 2009 05:25:52 am Peter Urbanec wrote:
> Jiri Kosina wrote:
> > On Wed, 7 Oct 2009, Peter Urbanec wrote:
> >> In a nutshell, I can run the same kernel on the same hardware and on
> >> some boots the AUX port will not be detected and on other boots it will
> >> come up fine.
> >
> > Does booting with 'i8042.noloop' improve the situation?
>
> Jirko,
>
> Thanks for the suggestion. I have been testing the i8042.noloop
> workaround for a few weeks now. So far I have not not experienced any
> problems when booting with that option. I would say that the workaround
> can be declared as being effective.
>
> I also applied Dmitry's patch to log the timeout condition when
> detecting the AUX port. Without the i8042.noloop option, the AUX port
> detection fails intermittently, but when it does, it causes an aux irq
> test timeout, which coincides with uhci_hcd USB hub initialisation.
> Perhaps the USB code somehow causes the loss of this interrupt.
>
> Adding the DMI info for the machine to the i8042_dmi_noloop_table is
> perhaps not the most correct fix for the underlying problem, but it does
> get results.
>
I ended up just disabling aux irq delivery test in 2.6.32 on all laptops and
portables (as long as they have sane PNP data)... There are just too many
failures and the vast majority of them use PS/2 touchpads/trackpoints.
--
Dmitry
next prev parent reply other threads:[~2009-10-29 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 14:24 Issues detecting i8042 AUX port Peter Urbanec
2009-10-08 21:17 ` Jiri Kosina
2009-10-29 12:25 ` Peter Urbanec
2009-10-29 17:02 ` Dmitry Torokhov [this message]
2009-11-02 14:33 ` Jiri Kosina
2009-11-08 4:22 ` Peter Urbanec
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=200910291002.16733.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=vger.kernel.org.input@urbanec.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.