From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] 2.6.16-rc5: unreasonable temperature reported by
Date: Tue, 04 Apr 2006 19:59:18 +0000 [thread overview]
Message-ID: <20060404215918.fdd76b30.khali@linux-fr.org> (raw)
In-Reply-To: <44144A01.2050207@t-online.de>
Harald,
> "Power control" reminds me of something: Sometimes ACPI power off
> doesn't work. Do you think this is a related problem?
I don't think so. The other I2C chips we've seen which were dealing
with "power" were usually VID control chips, which can be used to
slightly alter the CPU Vcore. This can be used for power-saving
purposes or overclocking purposes, depending on the change direction.
My understanding is that these chips should not be needed for regular
users. But then again, I don't know what _this_ chip does at all, so I
can't tell.
> Creating a driver on my own sounds pretty cool. Probably it is
> allowed to use an existing driver as a template?
Not allowed. Required ;)
Not absolutely required, in fact, but strongly encouraged, as this will
make it much easier for you. Hardware monitoring drivers have many
common points, and if you choose your template(s) properly, the new
driver can be done in no time and its review will be much faster too.
I didn't look at the datasheet for your chip yet (no time for this
sorry) so I can't tell you exactly which driver to start from. But this
should be an i2c-only driver (no platform driver, and no i2c-isa
trick.) Maybe lm90 will do, as it's both simple and up-to-date with
regards to recent changes. And you can always peek at other drivers for
the features your chip has and lm90 doesn't.
--
Jean Delvare
next prev parent reply other threads:[~2006-04-04 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 16:19 [lm-sensors] 2.6.16-rc5: unreasonable temperature reported by Harald Dunkel
2006-03-12 16:40 ` Jean Delvare
2006-03-12 18:32 ` Harald Dunkel
2006-03-13 9:31 ` Jean Delvare
2006-03-18 5:14 ` Harald Dunkel
2006-03-26 9:43 ` Harald Dunkel
2006-03-31 12:35 ` Jean Delvare
2006-04-01 5:44 ` Harald Dunkel
2006-04-01 12:48 ` Jean Delvare
2006-04-01 13:59 ` Harald Dunkel
2006-04-04 18:07 ` Harald Dunkel
2006-04-04 19:49 ` Jean Delvare
2006-04-04 19:59 ` Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 16:24 Harald Dunkel
2006-05-20 9:03 ` Jean Delvare
2006-05-26 10:46 ` Harald Dunkel
2006-05-26 12:10 ` Jean Delvare
2006-05-26 19:02 ` Harald Dunkel
2006-05-28 17:24 ` Harald Dunkel
2006-06-10 7:33 ` Harald Dunkel
2006-08-19 9:39 ` Rudolf Marek
2006-08-20 5:50 ` Harald Dunkel
2006-08-20 10:44 ` Rudolf Marek
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=20060404215918.fdd76b30.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.