All of lore.kernel.org
 help / color / mirror / Atom feed
From: rvinson@mvista.com (Randy Vinson)
To: Eugene Surovegin <ebs@ebshome.net>
Cc: Greg KH <greg@kroah.com>,
	sensors@stimpy.netroedge.com, linuxppc-embedded@ozlabs.org
Subject: [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374
Date: Sat, 04 Jun 2005 07:59:29 +0000	[thread overview]
Message-ID: <42A0D714.1050601@mvista.com> (raw)
In-Reply-To: <20050603214653.GA15314@gate.ebshome.net>

Eugene Surovegin wrote:
[snip]
> 
> I wonder, why you chose to use those 1-byte SMBus transfers instead of 
> i2c transfer.

I was simply following the guidelines in 
Documentation/i2c/writing-clients as noted in the driver header. This 
note was in the driver I used as my base, so I just followed along.

> 
> I wrote similar DS1374 driver some time ago which used those transfers 
> and they worked just fine.

I checked http://secure.netroedge.com/~lm78/supported.html, 
http://secure.netroedge.com/~lm78/newdrivers.html and looked in the 
lm_sensors-2.9.1 tarball before I started and didn't see a driver for 
the DS1374 listed. That's why I threw mine together. Maybe I missed it.

I would have used I2C transfers myself, but was simply following what I 
thought were current practices. Since this is my first I2C client, I 
just blindly followed the documentation :) Oh well, wouldn't be the 
first time I wandered down the wrong path.

		Randy Vinson



WARNING: multiple messages have this Message-ID (diff)
From: Randy Vinson <rvinson@mvista.com>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: Greg KH <greg@kroah.com>,
	sensors@stimpy.netroedge.com, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip
Date: Fri, 03 Jun 2005 15:17:56 -0700	[thread overview]
Message-ID: <42A0D714.1050601@mvista.com> (raw)
In-Reply-To: <20050603214653.GA15314@gate.ebshome.net>

Eugene Surovegin wrote:
[snip]
> 
> I wonder, why you chose to use those 1-byte SMBus transfers instead of 
> i2c transfer.

I was simply following the guidelines in 
Documentation/i2c/writing-clients as noted in the driver header. This 
note was in the driver I used as my base, so I just followed along.

> 
> I wrote similar DS1374 driver some time ago which used those transfers 
> and they worked just fine.

I checked http://secure.netroedge.com/~lm78/supported.html, 
http://secure.netroedge.com/~lm78/newdrivers.html and looked in the 
lm_sensors-2.9.1 tarball before I started and didn't see a driver for 
the DS1374 listed. That's why I threw mine together. Maybe I missed it.

I would have used I2C transfers myself, but was simply following what I 
thought were current practices. Since this is my first I2C client, I 
just blindly followed the documentation :) Oh well, wouldn't be the 
first time I wandered down the wrong path.

		Randy Vinson

  reply	other threads:[~2005-06-04  7:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 21:36 [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Randy Vinson
2005-06-04  7:59 ` [lm-sensors] [PATCH 1/2] Add support for Maxim/Dallas DS1374 Randy Vinson
2005-06-03 21:41 ` [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Kumar Gala
2005-06-04  7:59   ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Kumar Gala
2005-06-03 22:05   ` [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Randy Vinson
2005-06-04  7:59     ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Randy Vinson
2005-06-03 21:43 ` [PATCH 2/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Randy Vinson
2005-06-04  7:59   ` [lm-sensors] [PATCH 2/2] Add support for Maxim/Dallas DS1374 Randy Vinson
2005-06-03 21:46 ` [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Eugene Surovegin
2005-06-04  7:59   ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Eugene Surovegin
2005-06-03 22:17   ` Randy Vinson [this message]
2005-06-04  7:59     ` Randy Vinson
2005-06-09 17:25     ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Jean Delvare
2005-06-09 19:26       ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas Jean Delvare
2005-06-09 19:06       ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Mark A. Greer
2005-06-09 21:07         ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Mark A. Greer
2005-06-09 19:29         ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Jean Delvare
2005-06-09 21:30           ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas Jean Delvare
2005-06-09 18:21 ` [lm-sensors] [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Jean Delvare
2005-06-09 20:21   ` [lm-sensors] [PATCH 1/2] Add support for Maxim/Dallas DS1374 Jean Delvare

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=42A0D714.1050601@mvista.com \
    --to=rvinson@mvista.com \
    --cc=ebs@ebshome.net \
    --cc=greg@kroah.com \
    --cc=linuxppc-embedded@ozlabs.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 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.