From: Greg KH <greg@kroah.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Mark Brown <broonie@sirena.org.uk>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Schedule slot suggestion- Generic drivers - core topic
Date: Fri, 28 Oct 2016 17:43:06 -0400 [thread overview]
Message-ID: <20161028214306.GA12838@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1610282325150.31629@cbobk.fhfr.pm>
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
next prev parent reply other threads:[~2016-10-28 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 21:16 [Ksummit-discuss] Schedule slot suggestion- Generic drivers - core topic Luis R. Rodriguez
2016-10-28 21:21 ` Jiri Kosina
2016-10-28 21:23 ` Greg KH
2016-10-28 21:25 ` Luis R. Rodriguez
2016-10-28 21:29 ` Jiri Kosina
2016-10-28 21:38 ` Dmitry Torokhov
2016-10-28 21:44 ` Greg KH
2016-10-28 21:51 ` Dmitry Torokhov
2016-10-29 1:12 ` Laurent Pinchart
2016-10-28 21:43 ` Greg KH [this message]
2016-10-31 2:13 ` Rob Herring
2016-10-31 4:33 ` Laurent Pinchart
2016-10-31 4:47 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161028214306.GA12838@kroah.com \
--to=greg@kroah.com \
--cc=broonie@sirena.org.uk \
--cc=jikos@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.