linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-input@atrey.karlin.mff.cuni.cz, nicolas@boichat.ch,
	linux-usb-devel@lists.sourceforge.net,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make appletouch shut up when it has nothing to say
Date: Tue, 15 May 2007 20:34:55 +0000	[thread overview]
Message-ID: <1179261295.18316.9.camel@localhost> (raw)
In-Reply-To: <20070513185807.18222a0d.zaitcev@redhat.com>

On Sun, 2007-05-13 at 18:58 -0700, Pete Zaitcev wrote:
> On Sun, 13 May 2007 20:57:25 +0100, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> 
> > Ok, I've tidied this up a little. [...]
> 
> Looks fine here... well, almost. Did you try rmmod (I don't even know if
> it's applicable, sorry)? Usually, when schedule_work is involved, you want
> to make sure that a scheduled work won't be run when the module is gone.
> More often, a device removal is the issue, but as I take it, such is not
> possible for a built-in device :-) . In most cases, all it takes is a
> strategically placed flush_scheduled_work().

I was using this patch for some days now and I realized that - from time
to time - the touchpad runs amok, i.e. I more or less unable to control
the mouse when that happens.

Then a rmmod appletouch (+ reload) fixes this, as well as a sleep/resume
cycle.

As I had to rmmod appletouch a lot and did not see crashes I think it
works... though this problem persists...

Soeren
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.

  reply	other threads:[~2007-05-15 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1178995886.4168.10.camel@localhost>
2007-05-13 17:20 ` [PATCH] Make appletouch shut up when it has nothing to say Matthew Garrett
2007-05-13 18:46   ` Pete Zaitcev
2007-05-13 19:57     ` Matthew Garrett
2007-05-14  0:19       ` Soeren Sonnenburg
2007-05-14  1:58       ` Pete Zaitcev
2007-05-15 20:34         ` Soeren Sonnenburg [this message]
2007-05-16  2:38           ` Matthew Garrett

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=1179261295.18316.9.camel@localhost \
    --to=kernel@nn7.de \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mjg59@srcf.ucam.org \
    --cc=nicolas@boichat.ch \
    --cc=zaitcev@redhat.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;
as well as URLs for NNTP newsgroup(s).