From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: [PATCH 4/4] Input: leds - force the LED status after .probe() Date: Fri, 27 Jan 2017 18:34:00 +0100 Message-ID: <20170127173400.GA9511@var.bordeaux.inria.fr> References: <20170127171318.2596-1-benjamin.tissoires@redhat.com> <20170127171318.2596-5-benjamin.tissoires@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:13515 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933253AbdA0ReD (ORCPT ); Fri, 27 Jan 2017 12:34:03 -0500 Content-Disposition: inline In-Reply-To: <20170127171318.2596-5-benjamin.tissoires@redhat.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Benjamin Tissoires Cc: Dmitry Torokhov , Greg Kroah-Hartman , Jiri Slaby , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Benjamin Tissoires, on Fri 27 Jan 2017 18:13:18 +0100, wrote: > Once the host has set the initial setting of the LEDs after a new > USB keyboard gets connected, they appear to have a SET_IDLE command > sent which turns of the LEDs. > This means that the initial step of setting the LEDs on a keyboard is > just reset once .probe() finishes. > To be sure we set the LEDs, start a delayed task to try to resend > them after 1 sec. If there is such issue, I'd say fix the issue (what is sending SET_IDLE?) instead of working around it. Samuel