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 41A9D5B0 for ; Fri, 28 Oct 2016 21:29:03 +0000 (UTC) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BE87325C for ; Fri, 28 Oct 2016 21:29:02 +0000 (UTC) Date: Fri, 28 Oct 2016 23:29:00 +0200 (CEST) From: Jiri Kosina To: Greg KH In-Reply-To: <20161028212310.GA25668@kroah.com> Message-ID: References: <20161028212310.GA25668@kroah.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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, 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. It'd be nice for the specific driver to be able to claim this property somehow. Thanks, -- Jiri Kosina SUSE Labs