From: Daniel Manrique <daniel.manrique@canonical.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Bug: touchpad unresponsive after resume from S3 (psmouse driver)
Date: Fri, 02 Dec 2011 12:39:33 -0500 [thread overview]
Message-ID: <4ED90D55.20802@canonical.com> (raw)
In-Reply-To: <20111202061623.GA9688@core.coreip.homeip.net>
On 11-12-02 01:16 AM, Dmitry Torokhov wrote:
> On Thu, Dec 01, 2011 at 03:39:43PM -0500, Daniel Manrique wrote:
>>
>> The ssleep(1); line is what appears to do the trick; the version that just
>> queries the ID exhibits the same problem I reported initially, while the one
>> that just ssleeps works fine, with the touchpad working OK after resuming.
>>
>> I'll await further instructions on this, thanks so much for your help!
>>
>
> OK, great. Could you please try the patch below to make sure it works as
> intended and I'll queue it to upstream/stable?
>
> Thanks.
>
Hi Dmitry!
I tried the attached patch and tested just as before, I created two versions of
the module, one with the patch, one without, and tested them.
Yes, the code in the patch works as it did before, and the touchpad works fine
after resuming. I tried several times with both modules to be sure, and results
are consistent every time (i.e. patched module works, unpatched one always fails)
Thanks for this!
- Daniel
prev parent reply other threads:[~2011-12-02 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 16:26 Bug: touchpad unresponsive after resume from S3 (psmouse driver) Daniel Manrique
2011-11-29 17:53 ` Dmitry Torokhov
2011-11-29 19:43 ` Daniel Manrique
2011-11-30 0:17 ` Dmitry Torokhov
2011-11-30 15:18 ` Daniel Manrique
2011-12-01 5:15 ` Dmitry Torokhov
2011-12-01 20:39 ` Daniel Manrique
2011-12-02 6:16 ` Dmitry Torokhov
2011-12-02 17:39 ` Daniel Manrique [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=4ED90D55.20802@canonical.com \
--to=daniel.manrique@canonical.com \
--cc=dmitry.torokhov@gmail.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).