[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Direct bind of device to driver

To: Frank.A.Uepping@xxxxxxxxxxx
Subject: Re: Direct bind of device to driver
From: Greg KH <greg@xxxxxxxxx>
Date: Wed, 4 Feb 2004 15:49:52 -0800
Cc: kernelnewbies@xxxxxxxxxxxx
In-Reply-To: <200402032228.42986.Frank.A.Uepping@t-online.de>
List-archive: <http://mail.nl.linux.org/kernelnewbies/>
List-help: <mailto:listar@nl.linux.org?Subject=help>
List-owner: <mailto:riel@nl.linux.org>
List-post: <mailto:kernelnewbies@nl.linux.org>
List-software: Listar version 1.0.0
List-subscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=unsubscribe>
References: <200402032228.42986.Frank.A.Uepping@t-online.de>
Sender: kernelnewbies-bounce@xxxxxxxxxxxx
User-Agent: Mutt/1.4.1i

On Tue, Feb 03, 2004 at 10:28:42PM +0100, Frank.A.Uepping@t-online.de wrote:
> Hi,
> apparently it is possible to skip the match and probe procedure by defining 
> struct device::driver directly. Any scruple in doing so?
> I want use this on a virtual bus, where devices are not registered by the bus 
> driver but by the device driver.

that works.  It's what the i2c core does, and the USB core also does
this in places to work around some nasty USB issues.

greg k-h

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

References:
- Direct bind of device to driver
  - From: Frank.A.Uepping

Prev by Date: Re: File/IO discussion - request for comments
Next by Date: kernel oops after unloading driver module
Prev by thread: Direct bind of device to driver
Next by thread: Include path in module compilation
Index(es):
- Date
- Thread