From: "Dave Neuer" <mr.fred.smoothie@pobox.com>
To: "Dmitry Torokhov" <dtor@insightbb.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>,
"Vojtech Pavlik" <vojtech@suse.cz>
Subject: Re: [RFT/PATCH] i8042: remove polling timer (v6)
Date: Sun, 29 Oct 2006 18:20:19 -0500 [thread overview]
Message-ID: <161717d50610291520i5076901blf8bf253eba6148cc@mail.gmail.com> (raw)
In-Reply-To: <200608232311.07599.dtor@insightbb.com>
On 8/23/06, Dmitry Torokhov <dtor@insightbb.com> wrote:
> Hi everyone,
>
> Here is another version of the patch removing polling timer from i8042
> which is needed if we want tickless kernel. Keyboards should now work
> on boxes that do not have mouse plugged in. PLease give it a test.
What's the intent of this; just to allow tickless? Or is it also to
make the i8042 driver less racy? I ask because I've applied this over
(a modified) 2.6.18 on my Compaq Presario X1010us laptop which has
been driving me crazy w/ Synaptics problems and keyboard problems
(intermittent, but frequent enough lately that I finally figured I
needed to do something about it).
If removing raciness is part of the goal, isn't the window in
i8042_aux_write still a problem?
if (port->mux == -1)
retval = i8042_command(&c, I8042_CMD_AUX_SEND);
else
retval = i8042_command(&c, I8042_CMD_MUX_SEND + port->mux);
/* i8042_command has re-enabled interrupts;
what happens if real interrupt happens here, before we call
the ISR ourselves? */
i8042_interrupt(0, NULL, NULL);
return retval;
}
I don't really know if or how much the races in this driver are
contributing to my problems (keyboard getting stuck repeating last
key, or ignoring interrupts, or synaptics touchpad freezing, last of
which requires cold boot to fix). Maybe more likely an ACPI thing?
Anyway, thought I'd point this out and see if this patch is actually
going in someone's queue. I think I'll keep running w/ the patch since
w/ the polling in there and HZ set to 1000, it seemed like there were
an awful lot of opportunities for the driver to get confused, and even
if it's not causing my problems it doesn't seem like it could be
helping.
Dave
next prev parent reply other threads:[~2006-10-29 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 3:11 Dmitry Torokhov
2006-10-29 23:20 ` Dave Neuer [this message]
2006-10-30 3:34 ` Dmitry Torokhov
2006-10-30 9:08 ` Vojtech Pavlik
2006-10-30 13:01 ` Dave Neuer
2006-10-30 14:22 ` Dave Neuer
2006-11-03 5:56 ` Dmitry Torokhov
2006-11-03 8:18 ` Vojtech Pavlik
2006-11-03 14:08 ` Dmitry Torokhov
2006-11-03 6:03 ` Dmitry Torokhov
2006-11-06 16:22 ` Dave Neuer
2006-11-06 16:48 ` Dmitry Torokhov
2006-11-06 17:09 ` Dave Neuer
2006-11-06 17:21 ` Dave Neuer
2006-11-20 4:36 ` Dave Neuer
2006-11-20 5:04 ` Dave Neuer
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=161717d50610291520i5076901blf8bf253eba6148cc@mail.gmail.com \
--to=mr.fred.smoothie@pobox.com \
--cc=akpm@osdl.org \
--cc=dtor@insightbb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®