All of lore.kernel.org
 help / color / mirror / Atom feed
From: bgardner@wabtec.com (bgardner@wabtec.com)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [Patch 0/5] w1: sysfs, select-slave, ds2433
Date: Thu, 30 Jun 2005 16:08:07 +0000	[thread overview]
Message-ID: <200506300907.45063.bgardner@wabtec.com> (raw)

Evgeniy,

I finally have a working driver for w1 family 23.
Along the way, I made a few changes to the w1 slave stuff.
I also learned how to use quilt, so this wasn't nearly as painful as the last 
patch set. =)
The patches depend on each other and should be applied in the following order.

w1-select-slave.diff
I added w1_reset_select_slave()
This function resets the w1 bus and either sends a skip rom (0xCC) or the full 
select ROM + id.  If there is only 1 slave present, it does skip rom.

w1-select-slave-use.diff
I changed w1-therm to use w1_reset_select_slave.

w1-container-of.diff
I added three inline function to hide the use of container_of().
 - dev_to_w1_slave()
 - kobj_to_w1_slave()
 - dev_to_w1_master()

w1-slave-sysfs.diff
Every slave now has at least two sysfs files:
 - id : an 8 byte binary file that holds the 64 bit id 
   example: [23 6c dc 1c 00 00 00 43]
 - name : the name, example: [23-0000001cdc6c]
Family ops is now two callback functions: add_slave() and remove_slave().
The family driver is responsible for creating any other sysfs entries.
This patch updates w1-smem (which is pretty much empty) and w1-therm.

w1-ds2433.diff
The driver for family 23.

Would you take a moment to review and try it out to make sure I didn't break 
anything?

Thanks,
Ben


             reply	other threads:[~2005-06-30 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 16:08 bgardner [this message]
2005-06-30 16:29 ` [lm-sensors] [Patch 0/5] w1: sysfs, select-slave, ds2433 Evgeniy Polyakov
2005-06-30 17:01 ` BGardner

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=200506300907.45063.bgardner@wabtec.com \
    --to=bgardner@wabtec.com \
    --cc=lm-sensors@vger.kernel.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.