From: Martin Waitz <tali@admingilde.org>
To: Tejun Heo <tj@home-tj.org>
Cc: rusty@rustcorp.com.au, mochel@osdl.org, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.10-rc1 0/4] driver-model: manual device attach
Date: Thu, 4 Nov 2004 11:27:52 +0100 [thread overview]
Message-ID: <20041104102752.GW3618@admingilde.org> (raw)
In-Reply-To: <20041104074330.GG25567@home-tj.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
hoi :)
On Thu, Nov 04, 2004 at 04:43:30PM +0900, Tejun Heo wrote:
> Two files named attach and detach are created under each device's
> sysfs directory. Reading attach node shows the name of applicable
> drivers. Writing a driver name attaches the device to the driver.
> Also, per-device parameters can be specified when writing to an attach
> node. Writing anything to the write-only detach node detaches the
> driver from the currently associated driver.
perhaps it'll be simpler with only the attach file and using a special
magic value ("", "none", "detach", whatever) to manually detach a device
from the driver.
Is it possible (and worthwhile) to reattach a manually detached device
to the default driver? Perhaps using a magic value "auto" for attach.
Something like your dev.autoattach=2 rescan method, but for one
device only. (What is the use case to rescan all busses, anyway?)
--
Martin Waitz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-04 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 7:43 [PATCH 2.6.10-rc1 0/4] driver-model: manual device attach Tejun Heo
2004-11-04 7:44 ` [PATCH 2.6.10-rc1 1/4] driver-model: sysctl node dev.autoattach Tejun Heo
2004-11-04 7:45 ` [PATCH 2.6.10-rc1 2/4] driver-model: devparam expanded to accept direct per-device parameters via @args argument Tejun Heo
2004-11-04 7:45 ` [PATCH 2.6.10-rc1 3/4] driver-model: detach_state functions renamed Tejun Heo
2004-11-04 7:46 ` [PATCH 2.6.10-rc1 4/4] driver-model: attach/detach sysfs node implemented Tejun Heo
2004-11-04 17:05 ` Dmitry Torokhov
2004-11-04 17:49 ` Greg KH
2004-11-04 10:27 ` Martin Waitz [this message]
2004-11-04 17:53 ` [PATCH 2.6.10-rc1 0/4] driver-model: manual device attach Greg KH
2004-11-05 4:50 ` Tejun Heo
2004-11-05 5:02 ` Dmitry Torokhov
2004-11-05 6:32 ` Tejun Heo
2004-11-05 14:53 ` Dmitry Torokhov
2004-11-08 7:23 ` Dmitry Torokhov
2004-11-08 7:23 ` [PATCH 1/3] Add drvctl default device attribute Dmitry Torokhov
2004-11-08 7:25 ` [PATCH 2/3] Add drvctl handler to PCI bus Dmitry Torokhov
2004-11-08 7:26 ` [PATCH 3/3] Add bind_mode default device/driver attributes Dmitry Torokhov
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=20041104102752.GW3618@admingilde.org \
--to=tali@admingilde.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rusty@rustcorp.com.au \
--cc=tj@home-tj.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox