From: Alexander Stein <alexander.stein@systec-electronic.com>
To: guenter.roeck@ericsson.com
Cc: Jean Delvare <khali@linux-fr.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwmon: LM95245 driver
Date: Thu, 23 Jun 2011 11:14:52 +0200 [thread overview]
Message-ID: <201106231114.52841.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <1308770149.8271.600.camel@groeck-laptop>
On Wednesday 22 June 2011 21:15:49 Guenter Roeck wrote:
> On Tue, 2011-06-21 at 05:52 -0400, Alexander Stein wrote:
> > An hwmon driver for the National Semiconductor LM95245 dual temperature
> > sensors chip.
> >
> > Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
>
> Overall pretty well written, only I am a bit at loss why you try to deal
> with the unsigned temperature registers. That adds a bit of complexity
> to the driver. Given that the signed temperature value range is up to
> 127 degrees C, and that the chip is only rated up to 125 degrees C, the
> added complexity doesn't seem to be worth it.
>
> Can you elaborate ?
Well, AFAIK the 125 degrees C limit is for the chip itself. I didn't found
anything about a remote diode limit. Also the remote TCRIT and OS limit range
up to 255 degrees C.
Another point is the optional offset register (not implemented, see below). I
could not found much about it, but I guess this is immediately added to the
remote temperature register.
> Other comments:
>
> For the interval attribute, idea would be to write the value into the
> conversion rate register. Your code does not match the interval with the
> rate programmed into the chip (which is the idea), nor does it update
> the rate if the interval is changed.
Well, I noticed that. But I went the way lm95241 does. I'm also unsure which
interval to choose, if user specify a unsupported interval. Choose the next
small or the next greater one? Maybe you can give me a hint here.
> Chip address 0x29 is missing.
Nice catch.
> It would be nice if the driver would support limit, hysteresis, alarm,
> and fault attributes.
Let's see if I find time for that.
Thanks for the review though.
Regards,
Alexander
next prev parent reply other threads:[~2011-06-23 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 9:52 Alexander Stein
2011-06-22 19:15 ` Guenter Roeck
2011-06-23 9:14 ` Alexander Stein [this message]
2011-06-23 9:33 ` Jean Delvare
2011-06-23 10:50 ` Alexander Stein
2011-06-23 14:26 ` Guenter Roeck
2011-06-23 14:47 ` Guenter Roeck
2011-06-23 15:14 ` Alexander Stein
2011-06-23 15:35 ` Guenter Roeck
2011-06-27 15:49 ` [PATCH v2] " Alexander Stein
2011-06-27 20:21 ` Guenter Roeck
2011-06-28 7:07 ` [PATCH v3] " Alexander Stein
2011-06-28 14:43 ` Guenter Roeck
2011-06-28 15:11 ` [PATCH v4] " Alexander Stein
2011-06-30 9:06 ` Guenter Roeck
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=201106231114.52841.alexander.stein@systec-electronic.com \
--to=alexander.stein@systec-electronic.com \
--cc=guenter.roeck@ericsson.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome