From: Steven King <sfking@fdwdc.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature
Date: Sat, 06 Mar 2010 16:16:54 +0000 [thread overview]
Message-ID: <201003060816.54682.sfking@fdwdc.com> (raw)
In-Reply-To: <201002031723.49976.sfking@fdwdc.com>
On Saturday 06 March 2010 12:35:21 Jean Delvare wrote:
> Hi Andrew,
>
> Adding back Steven and the lm-sensors list...
>
> On Fri, 5 Mar 2010 11:53:42 -0800, Andrew Morton wrote:
> > So you're OK with the patch as-is?
>
> I did not review it. And testing it doesn't seem positive. First of
> all, I get the following in my logs after loading the driver:
>
> (null): not a tmp102
>
> Which suggests the use of an uninitialized device struct. Also, the
> detection fails early, I don't think the detection routine works.
> Looking at the code, it doesn't seem to correspond to the TMP102
> register map at all (assuming the dump I got from Steven is really from
> a TMP102) Steven, did you ever test it? Honestly, I don't think it
> makes sense to have a detect routine for this chip, given that it lacks
> identification registers. We relied on ugly detection quirks for the
> LM75 only because that chip was very popular on PC motherboards at one
> point in time. For devices used on embedded designs and which are
> always enumerated, we don't need detection routines.
For my specific use the part is connected to an embedded system and is always
enumerated; as lm-sensors doesnt build for this target I wasnt aware of any
way to test the detection code. I certainly wouldnt have any problem with
removing the detection routine entirely...
> Then, using the tmp102 driver on the dump sent by Steven produces the
> following "sensors" output:
>
> tmp102-i2c-3-48
> Adapter: SMBus stub driver
> temp1: +2.6°C (high = +15.0°C, hyst = +9.0°C)
>
> These values are suspiciously low and smell like the wrong base unit is
> used (1/100 °C instead of 1/1000 °C). Quick code examination seems to
> confirm this.
Doh! My bad.
> So, no, I am not OK with the patch as-is, it needs more work.
Okay, so besides removing the detect routine, incorporating Andrew's patch and
fixing the base for the temperature conversion, was there anything else I
need to do for v2?
--
Steven King -- sfking at fdwdc dot com
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-03-06 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 1:23 [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature sensor Steven King
2010-02-04 1:23 ` Steven King
2010-02-04 18:22 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Andrew Morton
2010-02-04 18:22 ` [PATCH] hwmon: driver for TI tmp102 temperature sensor Andrew Morton
2010-02-04 21:17 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Steven King
2010-02-04 21:17 ` [PATCH] hwmon: driver for TI tmp102 temperature sensor Steven King
2010-02-04 21:26 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Andrew Morton
2010-02-04 21:26 ` [PATCH] hwmon: driver for TI tmp102 temperature sensor Andrew Morton
2010-02-04 18:37 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Jean Delvare
2010-02-04 18:37 ` [PATCH] hwmon: driver for TI tmp102 temperature sensor Jean Delvare
2010-02-04 21:57 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Steven King
2010-02-04 21:57 ` [PATCH] hwmon: driver for TI tmp102 temperature sensor Steven King
2010-02-05 8:12 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Jean Delvare
2010-02-05 8:12 ` [PATCH] hwmon: driver for TI tmp102 temperature sensor Jean Delvare
2010-03-06 8:35 ` [lm-sensors] [PATCH] hwmon: driver for TI tmp102 temperature Jean Delvare
2010-03-06 16:16 ` Steven King [this message]
2010-03-07 12:23 ` Jean Delvare
2010-03-14 3:29 ` Steven King
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=201003060816.54682.sfking@fdwdc.com \
--to=sfking@fdwdc.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.