summaryrefslogtreecommitdiff
path: root/Documentation/w1
diff options
context:
space:
mode:
authorAlexander Stein <alexander.stein@informatik.tu-chemnitz.de>2013-05-26 22:06:50 +0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-06-04 01:09:14 +0400
commit8d7bda51888d14c07cbebacc5a10be776477bb63 (patch)
treed127eacb0e8961bbafb5bb2b02e0c2c4b008a78e /Documentation/w1
parenta4b05d1262c1f79ff07e9baceccbf3398846b8c0 (diff)
downloadlinux-8d7bda51888d14c07cbebacc5a10be776477bb63.tar.xz
w1: add family based automatic module loading
This patch allows the 1-wire bus to autoload the corresponding module for each slave being attached. This works similar to bluetooth protocols. Signed-off-by: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/w1')
-rw-r--r--Documentation/w1/w1.generic4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/w1/w1.generic b/Documentation/w1/w1.generic
index 212f4ac31c01..a31c5a242973 100644
--- a/Documentation/w1/w1.generic
+++ b/Documentation/w1/w1.generic
@@ -25,8 +25,8 @@ When a w1 master driver registers with the w1 subsystem, the following occurs:
- sysfs entries for that w1 master are created
- the w1 bus is periodically searched for new slave devices
-When a device is found on the bus, w1 core checks if driver for its family is
-loaded. If so, the family driver is attached to the slave.
+When a device is found on the bus, w1 core tries to load the driver for its family
+and check if it is loaded. If so, the family driver is attached to the slave.
If there is no driver for the family, default one is assigned, which allows to perform
almost any kind of operations. Each logical operation is a transaction
in nature, which can contain several (two or one) low-level operations.