linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-input@vger.kernel.org, apw@canonical.com,
	arjan@infradead.org, jkosina@suse.cz
Subject: Re: [patch for 2.6.29? 3/3] psmouse/synaptics: ensure we reset the device on resume
Date: Wed, 4 Mar 2009 22:31:33 -0800	[thread overview]
Message-ID: <20090305063129.GA14884@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <200903042010.n24KAu9G029857@imap1.linux-foundation.org>

On Wed, Mar 04, 2009 at 12:10:55PM -0800, akpm@linux-foundation.org wrote:
> From: Andy Whitcroft <apw@canonical.com>
> 
> When resuming from suspend newer Synaptics touchpads do not recover
> correctly.  Analysis of the resume sequence as applied in Linux was
> compared to that of other operating systems.  This indicated that the
> other OSs were resetting the mouse before attempting to detect it (for
> all Synaptics touchpads, old and new).  Applying this same modification
> fixes these newer Synaptics touchpads and brings the driver into line
> with common OS reset behaviour.
> 
> This patch adds this reset by default providing a module option to
> restore the previous non-reset behaviour:
> 
> 	psmouse.synaptics_resume_reset=N
> 
> Also a message is emmitted on resume hinting as to how to fix a broken
> touchpad.
> 
> [akpm@linux-foundation.org: make message more informative, fix 80-cols]

Andrew,

Please drop this one. I have committed a bit different version of the
same and it is now in mainline.

Thanks.

-- 
Dmitry

      reply	other threads:[~2009-03-05  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 20:10 [patch for 2.6.29? 3/3] psmouse/synaptics: ensure we reset the device on resume akpm
2009-03-05  6:31 ` Dmitry Torokhov [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=20090305063129.GA14884@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=arjan@infradead.org \
    --cc=jkosina@suse.cz \
    --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).