All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Andrew Morton <akpm@osdl.org>, Tomas Szepe <szepe@pinerecords.com>
Cc: gcs@lsc.hu, linux-kernel@vger.kernel.org, petero2@telia.com,
	john stultz <johnstul@us.ibm.com>
Subject: Re: Synaptics problems in -mm1
Date: Sat, 27 Dec 2003 19:45:44 -0500	[thread overview]
Message-ID: <200312271945.44559.dtor_core@ameritech.net> (raw)
In-Reply-To: <20031227160053.11bcd12d.akpm@osdl.org>

On Saturday 27 December 2003 07:00 pm, Andrew Morton wrote:
> Tomas Szepe <szepe@pinerecords.com> wrote:
> >  > I think it ACPI PM timer if you have it activated - I am having
> >  > problems with it myself but didn't have time to look closer. 
> >  > Could you try booting with clock=tsc or clock=pit and see if it
> >  > fixes the touchpad.
> >
> >  clock=tsc		appears to fix the problem.
> >  clock=pit		no change.
>
> So we've established that it is an interaction between the input code,
> the ACPI PM time code and cpufreq, yes?  That's a bit of a witches
> brew.
>
> Does anyone know what aspect of the ACPI PM timer behaviour could cause
> this?

>From my limited experience ACPI PM timer just gets the time wrong.
At least psmouse times out much quicker than 4 seconds when resetting
the touchpad which causes many problems.

Looking at the PM timer was on my TODO list ever since it was included
in -mm... I tried installing cpufreq handler to do the same adjustments
for loops_per_jiffy as in timer_pit but I was still getting pretty much
the same result - time goes too quickly.

Dmitry


  reply	other threads:[~2003-12-28  0:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24  9:59 2.6.0-mm1 GCS
2003-12-24 11:32 ` 2.6.0-mm1 Andrew Morton
2003-12-24 11:53   ` 2.6.0-mm1 GCS
2003-12-24 12:23     ` 2.6.0-mm1 GCS
2003-12-24 15:17       ` 2.6.0-mm1 Dmitry Torokhov
2003-12-24 19:12         ` 2.6.0-mm1 GCS
2003-12-24 12:47   ` 2.6.0-mm1 Thomas Molina
2003-12-25  9:11   ` 2.6.0-mm1 Dmitry Torokhov
2003-12-25  9:13     ` 2.6.0-mm1 - Patch 1/2 - mousedev-remove-jitter Dmitry Torokhov
2003-12-25  9:14       ` 2.6.0-mm1 - Patch 2/2 - mousedev-dont-stop Dmitry Torokhov
2003-12-27 11:38         ` Synaptics problems in -mm1 Tomas Szepe
2003-12-27 12:24           ` GCS
2003-12-27 13:22             ` Tomas Szepe
2003-12-27 17:28           ` Dmitry Torokhov
2003-12-27 18:11             ` Tomas Szepe
2003-12-27 18:23               ` Dmitry Torokhov
2003-12-27 18:37                 ` Tomas Szepe
2003-12-27 18:45                   ` Dmitry Torokhov
2003-12-27 19:01                     ` Tomas Szepe
2003-12-27 21:00                       ` Dmitry Torokhov
2003-12-28  0:00                   ` Andrew Morton
2003-12-28  0:45                     ` Dmitry Torokhov [this message]
2003-12-28  1:21                     ` Tomas Szepe
2003-12-27 17:56           ` Marcos D. Marado Torres
2003-12-27 20:59             ` Dmitry Torokhov
2003-12-25 18:22     ` 2.6.0-mm1 GCS
2003-12-24 14:38 ` 2.6.0-mm1 GCS

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=200312271945.44559.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=gcs@lsc.hu \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=szepe@pinerecords.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.