All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: device model documentation 2/3
Date: Tue, 04 Jun 2002 17:50:58 +0200	[thread overview]
Message-ID: <3CFCE1E2.1040906@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206040918490.654-100000@geena.pdx.osdl.net>

Patrick Mochel wrote:
> Document 2: driver.txt

> 
> This callback only verifies that there actually is supported hardware
> present. It may allocate a driver-specific structure, but it should
> not do any initialization of the hardware itself. The device-specific
> structure may be stored in the device's driver_data field. 
> 
> 	int	(*init)		(struct device * dev);
> 
> init is called during the binding stage. It is called after probe has
> successfully returned and the device has been registered with its
> class. It is responsible for initializing the hardware.

"init is called during the *attachment*."
You see it even sounds more naturall.


  parent reply	other threads:[~2002-06-04 16:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 16:25 device model documentation 2/3 Patrick Mochel
2002-06-02  2:00 ` Pavel Machek
2002-06-04 15:50 ` Martin Dalecki [this message]
2002-06-04 17:49 ` Greg KH
2002-06-05 12:51 ` Oliver Neukum
2002-06-05 19:11   ` Patrick Mochel
2002-06-02  4:49     ` Pavel Machek
2002-06-06 19:15       ` [linux-usb-devel] " David Brownell
2002-06-06 19:24         ` Pavel Machek
2002-06-06 20:00         ` Oliver Neukum
2002-06-05 21:54     ` Oliver Neukum
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02  4:49 Pavel Machek
2002-06-05 12:41 ` Oliver Neukum
2002-06-05 12:51 ` Oliver Neukum
2002-06-05 19:04 ` Patrick Mochel
2002-06-05 19:11 ` Patrick Mochel
2002-06-05 21:52 ` Oliver Neukum
2002-06-05 21:54 ` Oliver Neukum

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=3CFCE1E2.1040906@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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.