From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Proposal
Date: Sat, 16 Jun 2007 19:35:56 +0000 [thread overview]
Message-ID: <46743B9C.7060401@hhs.nl> (raw)
In-Reply-To: <200704081630.17151.hjk@linutronix.de>
Mark M. Hoffman wrote:
> Hi all:
>
> * Jean Delvare <khali@linux-fr.org> [2007-04-11 13:49:01 +0200]:
>> Hi Hans,
>>
>> On Mon, 09 Apr 2007 14:34:35 +0200, Hans de Goede wrote:
>>> Oh and another thing I just came up with, last time I checked, it isn't
>>> possible from userspace to change an inX_input to a tempX_input, or are you
>>> suggesting that I export all 48 sensors, 3 times, once as in, once as temp and
>>> once as fan and them make user space ignore temp1 and fan1, and use in0, as
>>> sensor 0/1 actually is an in sensor?
>> You're right, this isn't possible, because it's not needed. The drivers
>> are usually able to read the device configuration from its registers,
>> and create the right sysfs entries based on that information. The only
>> exceptions being the vt1211 and gl520sm drivers, which I mentioned in
>> my previous reply.
>
> In this case, there is no practical difference between reading that info from a
> register on the chip and inferring it from a register on the motherboard.
>
To be precise, the info actually is read from a register on the chip, not a
register on the motherboard (the chip is on the motherboard ofcourse).
So there really is no difference here, a register gets read and based on its
contents it gets determined what inputs are available and what their types are.
As an added bonus, one can also determine the scaling factors and labels for
the inputs too.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-06-16 19:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 14:30 [lm-sensors] Proposal Hans-Jürgen Koch
2007-04-08 17:36 ` Hans de Goede
2007-04-08 18:31 ` Hans-Jürgen Koch
2007-04-08 18:56 ` Hans de Goede
2007-04-08 19:18 ` Hans-Jürgen Koch
2007-04-09 11:23 ` Jean Delvare
2007-04-09 11:27 ` Jean Delvare
2007-04-09 12:24 ` Jean Delvare
2007-04-09 12:26 ` Hans de Goede
2007-04-09 12:34 ` Hans de Goede
2007-04-09 12:50 ` Hans de Goede
2007-04-11 11:35 ` Jean Delvare
2007-04-11 11:49 ` Jean Delvare
2007-04-11 11:56 ` Jean Delvare
2007-04-11 13:49 ` Hans de Goede
2007-06-16 15:14 ` Mark M. Hoffman
2007-06-16 15:21 ` Mark M. Hoffman
2007-06-16 15:42 ` Mark M. Hoffman
2007-06-16 19:35 ` Hans de Goede [this message]
2007-06-16 19:40 ` Hans de Goede
2007-06-16 19:50 ` Hans de Goede
2007-06-16 19:52 ` Mark M. Hoffman
2007-06-18 18:31 ` Jean Delvare
2007-06-18 19:58 ` Hans de Goede
2007-06-19 7:59 ` Jean Delvare
2007-06-19 8:15 ` Jean Delvare
2007-06-19 8:31 ` Hans de Goede
2007-06-19 12:27 ` Mark M. Hoffman
2007-06-24 11:43 ` Jean Delvare
2007-06-24 12:11 ` 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=46743B9C.7060401@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--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.