From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marin Mitov <mitov@issp.bas.bg>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Regression?: keyboard state/LED inconsistency in 2.6.32-rc1/2,3,4
Date: Mon, 12 Oct 2009 22:17:38 -0700 [thread overview]
Message-ID: <20091013051738.GD2887@core.coreip.homeip.net> (raw)
In-Reply-To: <200910130755.43510.mitov@issp.bas.bg>
On Tue, Oct 13, 2009 at 07:55:43AM +0300, Marin Mitov wrote:
> On Tuesday 13 October 2009 06:03:14 am Dmitry Torokhov wrote:
> > On Mon, Oct 12, 2009 at 01:57:08AM -0700, Dmitry Torokhov wrote:
> > > On Mon, Oct 12, 2009 at 10:30:15AM +0200, Vojtech Pavlik wrote:
> > > > On Mon, Oct 12, 2009 at 11:18:28AM +0300, Marin Mitov wrote:
> > > > > Hello,
> > > > >
> > > > > I'm testing 2.6.32-rc1/2,3,4 and I'm using 2.6.31.3.
> > > > > There is a difference in keyboard/LED behavior.
> > > > > If in BIOS NumLock is set on, when the kernel starts
> > > > > it puts NumLock off and the LED state is off in 2.6.31.3
> > > > > (which is consistent), but in 2.6.32-rc1/2,3,4 the LED
> > > > > stays on (and this is not consistent with keyboard's state).
> > > > >
> > > > > Comparing drivers/input/keyboard/atkbd.c (I'm using it)
> > > > > in 2.6.31.3 and 2.6.32-rc1/2,3,4 among others changes I
> > > > > found the following lines (see the patch bellow) deleted,
> > > > > so I propose either to add them again (this will restore
> > > > > keyboard/LED consistency) or revert the patch that has
> > > > > deleted them.
> > > >
> > > > Oh, wow, those lines are quite clearly needed, I wonder why they got
> > > > deleted, and I'm too lazy to find the commit comment ...
> > > >
> > >
> > > Hmm, it appears I deleted a bit too much.. At some point I was thinking
> > > the input core would reset LEDs and repeat rate on newly created device
> > > but it was wrong idea. Unfortunately I was careless in applying atkbd
> > > patch removing resume support (which should be handled by the input
> > > core)...
> > >
> >
> > Could you please try the patch below and let me know if it fixes
> > things?
> >
> > Thanks!
> >
>
> Yes, Dmitry, it fixes the problem, thank you.
>
Thank you for testing. Mouse re-initialization is pretty delicate topic,
may I ask you to test some more just to make sure fix is reliable - a
few more resumes and cold/warm boots would do...
Thanks lot.
--
Dmitry
next prev parent reply other threads:[~2009-10-13 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:18 Regression?: keyboard state/LED inconsistency in 2.6.32-rc1/2,3,4 Marin Mitov
2009-10-12 8:30 ` Vojtech Pavlik
2009-10-12 8:57 ` Dmitry Torokhov
2009-10-13 3:03 ` Dmitry Torokhov
2009-10-13 4:55 ` Marin Mitov
2009-10-13 5:17 ` Dmitry Torokhov [this message]
2009-10-13 5:19 ` Dmitry Torokhov
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=20091013051738.GD2887@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitov@issp.bas.bg \
--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