From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tino Keitel Subject: Re: [PATCH] Input: add appleir USB driver Date: Fri, 16 May 2008 09:26:34 +0200 Message-ID: <20080516072634.GA4867@dose.home.local> References: <20080514221519.GA6575@kroah.com> <20080515132108.GA9327@dose.home.local> <20080515094212.ZZRA012@mailhub.coreip.homeip.net> <20080515174939.GA10881@dose.home.local> <20080515142845.ZZRA012@mailhub.coreip.homeip.net> <20080515205950.GA11794@dose.home.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Jiri Kosina Cc: Dmitry Torokhov , Greg KH , linux-input@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-input@vger.kernel.org On Fri, May 16, 2008 at 09:19:39 +0200, Jiri Kosina wrote: > On Thu, 15 May 2008, Tino Keitel wrote: > > > Does setting the quirks to 0 lead to the creation of a HID device > > immediately? > > The easiest way is either to handle this in the early stage, i.e. specify > 'quirks' module parameter during the module insertion. > > Other possibility is to detach the driver from the device using 'unbind' > functionality of sysfs. libusb has a call for this too. Thanks for the hint. So I guess that the LIRC driver should be extended to watch out for a USB device with the prober vendor/device ID and unbind it before usage, right? This wouldn't help users who use the current LIRC with a kernel that has the HID ignore quirk enabled by default, though (i.e., it would be a regression). Regards, Tino