From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] I2C update for 2.6.8-rc1
Date: Wed, 14 Jul 2004 17:07:15 -0700 [thread overview]
Message-ID: <10898500353542@kroah.com> (raw)
In-Reply-To: <1089850035501@kroah.com>
ChangeSet 1.1784.13.14, 2004/07/14 11:51:29-07:00, khali@linux-fr.org
[PATCH] I2C: Refine detection of LM75 chips
The LM75 detection method was a bit loose so far and would accept
non-LM75-compatible chips from times to times. It should be better now.
Additionally, the help for the lm75 driver was reworked because we now
know that the LM75 and the LM77 are not compatible.
Signed-off-by: Jean Delvare <khali at linux-fr dot org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
drivers/i2c/chips/Kconfig | 8 ++++++--
drivers/i2c/chips/lm75.c | 37 +++++++++++++++++++++++++++++++------
2 files changed, 37 insertions(+), 8 deletions(-)
diff -Nru a/drivers/i2c/chips/Kconfig b/drivers/i2c/chips/Kconfig
--- a/drivers/i2c/chips/Kconfig 2004-07-14 16:59:00 -07:00
+++ b/drivers/i2c/chips/Kconfig 2004-07-14 16:59:00 -07:00
@@ -103,8 +103,12 @@
select I2C_SENSOR
help
If you say yes here you get support for National Semiconductor LM75
- sensor chips and clones: Dallas Semi DS75 and DS1775, TelCon
- TCN75, and National Semiconductor LM77.
+ sensor chips and clones: Dallas Semiconductor DS75 and DS1775 (in
+ 9-bit precision mode), and TelCom (now Microchip) TCN75.
+
+ The DS75 and DS1775 in 10- to 12-bit precision modes will require
+ a force module parameter. The driver will not handle the extra
+ precision anyhow.
This driver can also be built as a module. If so, the module
will be called lm75.
diff -Nru a/drivers/i2c/chips/lm75.c b/drivers/i2c/chips/lm75.c
--- a/drivers/i2c/chips/lm75.c 2004-07-14 16:59:00 -07:00
+++ b/drivers/i2c/chips/lm75.c 2004-07-14 16:59:00 -07:00
@@ -113,7 +113,7 @@
/* This function is called by i2c_detect */
static int lm75_detect(struct i2c_adapter *adapter, int address, int kind)
{
- int i, cur, conf, hyst, os;
+ int i;
struct i2c_client *new_client;
struct lm75_data *data;
int err = 0;
@@ -149,16 +149,41 @@
new_client->driver = &lm75_driver;
new_client->flags = 0;
- /* Now, we do the remaining detection. It is lousy. */
+ /* Now, we do the remaining detection. There is no identification-
+ dedicated register so we have to rely on several tricks:
+ unused bits, registers cycling over 8-address boundaries,
+ addresses 0x04-0x07 returning the last read value.
+ The cycling+unused addresses combination is not tested,
+ since it would significantly slow the detection down and would
+ hardly add any value. */
if (kind < 0) {
+ int cur, conf, hyst, os;
+
+ /* Unused addresses */
cur = i2c_smbus_read_word_data(new_client, 0);
conf = i2c_smbus_read_byte_data(new_client, 1);
hyst = i2c_smbus_read_word_data(new_client, 2);
+ if (i2c_smbus_read_word_data(new_client, 4) != hyst
+ || i2c_smbus_read_word_data(new_client, 5) != hyst
+ || i2c_smbus_read_word_data(new_client, 6) != hyst
+ || i2c_smbus_read_word_data(new_client, 7) != hyst)
+ goto exit_free;
os = i2c_smbus_read_word_data(new_client, 3);
- for (i = 0; i <= 0x1f; i++)
- if ((i2c_smbus_read_byte_data(new_client, i * 8 + 1) != conf) ||
- (i2c_smbus_read_word_data(new_client, i * 8 + 2) != hyst) ||
- (i2c_smbus_read_word_data(new_client, i * 8 + 3) != os))
+ if (i2c_smbus_read_word_data(new_client, 4) != os
+ || i2c_smbus_read_word_data(new_client, 5) != os
+ || i2c_smbus_read_word_data(new_client, 6) != os
+ || i2c_smbus_read_word_data(new_client, 7) != os)
+ goto exit_free;
+
+ /* Unused bits */
+ if (conf & 0xe0)
+ goto exit_free;
+
+ /* Addresses cycling */
+ for (i = 8; i < 0xff; i += 8)
+ if (i2c_smbus_read_byte_data(new_client, i + 1) != conf
+ || i2c_smbus_read_word_data(new_client, i + 2) != hyst
+ || i2c_smbus_read_word_data(new_client, i + 3) != os)
goto exit_free;
}
next prev parent reply other threads:[~2004-07-15 0:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 0:05 [BK PATCH] I2C update for 2.6.8-rc1 Greg KH
2004-07-15 0:07 ` [PATCH] " Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH
2004-07-15 0:07 ` Greg KH [this message]
2004-07-15 0:07 ` Greg KH
2004-07-16 17:07 ` Pavel Machek
2004-07-16 17:17 ` Greg KH
2004-07-16 17:39 ` Bob Riegelmann
2004-07-16 18:19 ` Adam Kropelin
2004-07-17 14:30 ` Greg (or anyone else) one small i2c question Reinder
2004-07-30 5:40 ` --- " Reinder
2004-07-30 6:30 ` Denis Vlasenko
2004-08-25 6:44 ` Greg " Greg KH
2004-08-24 21:58 ` [BK PATCH] I2C update for 2.6.8-rc1 Alex Williamson
2004-08-24 22:04 ` Greg KH
2004-08-25 0:37 ` Linus Torvalds
2004-08-25 1:38 ` Alex Williamson
2004-08-25 1:42 ` Alex Williamson
2004-08-25 2:02 ` Linus Torvalds
2004-08-25 6:14 ` Greg KH
2004-08-25 6:36 ` 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=10898500353542@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