From: Dmitry Torokhov <dtor@insightbb.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] blink: Only blink when parameter is set
Date: Wed, 20 Jun 2007 22:56:52 -0400 [thread overview]
Message-ID: <200706202256.53850.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706210222390.3068@twin.jikos.cz>
On Wednesday 20 June 2007 20:24, Jiri Kosina wrote:
> On Thu, 21 Jun 2007, Pavel Machek wrote:
>
> > > this has probably been already solved by proper throttling - see
> > > http://lkml.org/lkml/2007/6/15/22
> > No, it was not. I still saw the problems with CONFIG_BLINK on, that is
> > one blink per 5 seconds or something.
Pavel, does my patch fixes keyboard issues for you when blinking via
setleds?
> > We should rename CONFIG_BLINK to
> > CONFIG_BREAK_THINKPAD_KEYBOARD_AND_MORE.
Also CONFIG_KILL_MY_NOHZ_SAVINGS ;)
>
> In fact it looks quite weird that one blink per 5 seconds can break the
> keyboard, in fact.
Not wierd at all. The driver uses panic_blink - something that we expect
to work after panic. It rapidly polls KBC status register to detect when
it accepted led command and does it without taking i8042_lock (because
it may have been taken before kernel panicked) so it is quite possible
that that interferes with atkbd operation.
IOW I am not really interested in reports regrading issues with keyboards
and/or mice on boxes with blink driver loaded.
--
Dmitry
next prev parent reply other threads:[~2007-06-21 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 8:39 [PATCH] blink: Only blink when parameter is set Bernhard Walle
2007-06-17 16:11 ` Arjan van de Ven
2007-06-18 4:26 ` Randy Dunlap
2007-06-18 7:18 ` Bernhard Walle
2007-06-18 14:43 ` Randy Dunlap
2007-06-20 20:16 ` Pavel Machek
2007-06-20 23:51 ` Jiri Kosina
2007-06-21 0:20 ` Pavel Machek
2007-06-21 0:24 ` Jiri Kosina
2007-06-21 2:56 ` Dmitry Torokhov [this message]
2007-06-22 8:58 ` Pavel Machek
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=200706202256.53850.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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