From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Peter M. Petrakis" <peter.petrakis@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Reset ps/2 port should psmouse_probe fail before retrying
Date: Wed, 14 Apr 2010 14:04:22 -0700 [thread overview]
Message-ID: <20100414140422.b6054dbc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4BC629A5.4040500@canonical.com>
On Wed, 14 Apr 2010 16:46:29 -0400 Peter M. Petrakis wrote:
> Filed a bug on this too:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=15780
>
> This particular laptop will lose it's synaptics touch
> pad on return from suspend state. Reloading the psmouse
> module makes no difference. I came up with the attached
> work around which simply calls psmouse_reset on the
> port should the initial probe fail. This solves the problem
> for me and I've tested this on several laptops.
>
> Initially discovered on Ubuntu 2.6.31 (karmic) and the problem
> continues to exist in lucid 2.6.32. I've filed a bug against
> ubuntu kernel here:
>
> https://bugs.launchpad.net/oem-priority/+bug/551234
>
> though the Ubuntu kernel team would really like to get upstream's
> input on the matter before accepting the patch. Please
> let me know what you think. Thanks.
Hi,
Please send patches inline, not as attachments.
Use the full source file path in the patch.
Send the patch to linux-input@vger.kernel.org and cc: the Input
subsystem maintainer.
typo: s/reseting/resetting/
Other than those 4 things, the patch looks OK to me.
Well, we would prefer not to have the
((ret = __psmouse_probe(psmouse)) != 0)
inside the for expression if possible. I.e., make the for(...) simpler.
Please read/review Documentation/SubmittingPatches. Thanks.
---
~Randy
prev parent reply other threads:[~2010-04-14 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 20:46 Peter M. Petrakis
2010-04-14 21:04 ` Randy Dunlap [this message]
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=20100414140422.b6054dbc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.petrakis@canonical.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®