public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] I2C patches for 2.6.10
Date: Fri, 7 Jan 2005 21:39:35 -0800	[thread overview]
Message-ID: <1105162775137@kroah.com> (raw)
In-Reply-To: <11051627753704@kroah.com>

ChangeSet 1.1938.445.1, 2004/12/15 11:29:09-08:00, johnpol@2ka.mipt.ru

[PATCH] w1: Documentation bits for generic w1 behaviour.

Documentation bits for generic w1 behaviour.

Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>


 Documentation/w1/w1.generic |   19 +++++++++++++++++++
 1 files changed, 19 insertions(+)


diff -Nru a/Documentation/w1/w1.generic b/Documentation/w1/w1.generic
--- /dev/null	Wed Dec 31 16:00:00 196900
+++ b/Documentation/w1/w1.generic	2005-01-07 14:56:22 -08:00
@@ -0,0 +1,19 @@
+Any w1 device must be connected to w1 bus master device - for example
+ds9490 usb device or w1-over-GPIO or RS232 converter.
+Driver for w1 bus master must provide several functions(you can find
+them in struct w1_bus_master definition in w1.h) which then will be
+called by w1 core to send various commands over w1 bus(by default it is
+reset and search commands). When some device is found on the bus, w1 core
+checks if driver for it's family is loaded.
+If driver is loaded w1 core creates new w1_slave object and registers it
+in the system(creates some generic sysfs files(struct w1_family_ops in
+w1_family.h), notifies any registered listener and so on...).
+It is device driver's business to provide any communication method
+upstream.
+For example w1_therm driver(ds18?20 thermal sensor family driver)
+provides temperature reading function which is bound to ->rbin() method
+of the above w1_family_ops structure.
+w1_smem - driver for simple 64bit memory cell provides ID reading
+method.
+
+You can call above methods by reading appropriate sysfs files.


  reply	other threads:[~2005-01-08  7:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08  5:38 [BK PATCH] I2C patches for 2.6.10 Greg KH
2005-01-08  5:39 ` [PATCH] " Greg KH
2005-01-08  5:39   ` Greg KH
2005-01-08  5:39     ` Greg KH
2005-01-08  5:39       ` Greg KH
2005-01-08  5:39         ` Greg KH
2005-01-08  5:39           ` Greg KH
2005-01-08  5:39             ` Greg KH
2005-01-08  5:39               ` Greg KH
2005-01-08  5:39                 ` Greg KH
2005-01-08  5:39                   ` Greg KH
2005-01-08  5:39                     ` Greg KH
2005-01-08  5:39                       ` Greg KH
2005-01-08  5:39                         ` Greg KH [this message]
2005-01-08  5:39                           ` Greg KH
2005-01-08  5:39                             ` Greg KH
2005-01-08  5:39                               ` Greg KH
2005-01-08  5:39                                 ` Greg KH
2005-01-08  5:39                                   ` Greg KH
2005-01-08  5:39                                     ` Greg KH
2005-01-08  5:39                                       ` Greg KH
2005-01-08  5:39                                         ` Greg KH
2005-01-08  5:39                                           ` Greg KH
2005-01-08  5:39                                             ` Greg KH
2005-01-08  6:22                                               ` Mark M. Hoffman
2005-01-08 10:15                                                 ` Jean Delvare
2005-01-08 15:37                                                   ` Greg KH
2005-01-08 19:09 ` [BK PATCH] " Christoph Hellwig
2005-01-08 22:28   ` Greg KH

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=1105162775137@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.com \
    /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