linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rohwer <tr@tng.de>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@atrey.karlin.mff.cuni.cz,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Problem with appletouch driver in Linux version 2.6.23-rc7
Date: Thu, 27 Sep 2007 23:08:20 +0200	[thread overview]
Message-ID: <46FC1BC4.5050405@tng.de> (raw)
In-Reply-To: <1190915501.7636.4.camel@localhost>

>>> I think there is another bug in this. I mean whenever a mouse button is
>>> pressed or the mouse is moved the counter should be reset - no?
>>>
>>> Currently the idle counter is just increased...
>>>
>>> I mean shouldn't it be
>>>
>>> if (x || y || key)
>>>        dev->idlecount=0;
>>>
>>> if (!x && !y && !key)
>>> {
>>>        dev->idlecount++;
>>>        if (dev->idlecount == 10) {
>>>                dev->valid = 0;
>>>                schedule_work(&dev->work);
>>>        }
>>> }

Hello,

I agree that this is makes sense. I was wondering if one can remove the whole
idlecount logic. I tried replacing 10 with 1. This almost works; only if you press
the touchpad button, after a reset happened, you first get a usb packet with the
button state still 0 and after that one with button 1. I.e. with count 1 instead of 10
you reset the device another time in this case. But one could handle this case separately.
I am currently working with 2 instead of 10.

I was also wondering when the procedure atp_reinit is executed after using schedule_work.
Can it happen that atp_complete is called (even multiple times) before atp_reinit is executed?

Sincerely,

Thomas Rohwer

  reply	other threads:[~2007-09-27 21:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 17:14 Problem with appletouch driver in Linux version 2.6.23-rc7 Thomas Rohwer
2007-09-24 12:40 ` Dmitry Torokhov
2007-09-24 12:49   ` Matthew Garrett
2007-09-24 13:03   ` Soeren Sonnenburg
2007-09-24 13:22     ` Thomas Rohwer
2007-09-26 19:56       ` Soeren Sonnenburg
2007-09-26 20:13         ` Dmitry Torokhov
2007-09-27 17:51           ` Soeren Sonnenburg
2007-09-27 21:08             ` Thomas Rohwer [this message]
2007-10-13 21:33               ` Soeren Sonnenburg
2007-10-13 21:44                 ` Matthew Garrett
2007-10-15 13:09                 ` Dmitry Torokhov
2007-09-24 13:10   ` Thomas Rohwer

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=46FC1BC4.5050405@tng.de \
    --to=tr@tng.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kernel@nn7.de \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=mjg59@srcf.ucam.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).