From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 82D45907 for ; Fri, 28 Oct 2016 21:42:57 +0000 (UTC) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0410F1A9 for ; Fri, 28 Oct 2016 21:42:56 +0000 (UTC) Date: Fri, 28 Oct 2016 17:43:06 -0400 From: Greg KH To: Jiri Kosina Message-ID: <20161028214306.GA12838@kroah.com> References: <20161028212310.GA25668@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Mark Brown , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] Schedule slot suggestion- Generic drivers - core topic List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Oct 28, 2016 at 11:29:00PM +0200, Jiri Kosina wrote: > On Fri, 28 Oct 2016, Greg KH wrote: > > > On Fri, Oct 28, 2016 at 02:16:59PM -0700, Luis R. Rodriguez wrote: > > > Having some generic device driver load, prior to a specific driver, > > > and issues / maintenance issues that come with the hacks currently in > > > place to support this / re-invent the wheel to support this per > > > subsystem. > > > > We have hacks for this today? What do you mean by this, quirks? > > I have to maintain a device-id list that explicitly enumerates "these > devices can be handled by generic driver, but would better be handled by > specific driver", in the generic driver itself. Which is horrible. Yes, I agree, but so far, it's the only way we know how :( > It'd be nice for the specific driver to be able to claim this property > somehow. I also agree, it would be "nice", but I have yet to see a way to do this in a generic way :( thanks, greg k-h