From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: Keyboard LED state after suspend Date: Thu, 13 Nov 2008 16:52:53 -0500 Message-ID: <20081113165230.ZZRA012@mailhub.coreip.homeip.net> References: <200811132208.37874.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200811132208.37874.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Oliver Neukum Cc: Alan Stern , Jiri Kosina , linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, USB list List-Id: linux-input@vger.kernel.org On Thu, Nov 13, 2008 at 10:08:37PM +0100, Oliver Neukum wrote: > Am Donnerstag, 13. November 2008 21:05:39 schrieb Alan Stern: > > Jiri and Oliver: > > > > I tried the experiment of turning off NumLock and all the other > > keyboard LED settings before hibernating. After resuming, the LEDs on > > my PS/2 keyboard remained off but the NumLock LED on my USB keyboard > > was on. Probably the BIOS turned it on during the restart and Linux > > never turned it back off. > > > > Should we set the keyboard LED state whenever a keyboard is resumed? > > Is this handled already in the new autosuspend work? > > No, as this is no autosuspend problem. In fact it is not a driver problem > at all. This suggests that the HID layer should have hooks in resumption. > Actually I have patches that do that in input layer. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html