All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Single Sensor Check
Date: Fri, 05 Sep 2008 08:44:30 +0000	[thread overview]
Message-ID: <20080905104430.259c32f3@hyperion.delvare> (raw)
In-Reply-To: <06d401c8ff06$1103d690$330b83b0$@com>

Hi Ken,

On Tue, 2 Sep 2008 17:31:53 -0400, sensored@CubicC.com wrote:
> Thanks, Matt -- I appreciate the time you took to respond.  I *do* have
> control over the motherboard, so I went looking for documentation on the
> chipset & sensors, but there was nothing offered other than basic "How to
> configure the BIOS" information.  Do you have any suggestions of what,
> specifically, I could ask the manufacturer for (if they'll even oblige me).
> 
> I dug deeper into the lm-sensors code, and determined that lm-sensors is
> parsing a file in /sys/devices/platform/i2c-9191/9191-0290/ (and responding
> accordingly).  Can you help me understand how this file got created there,
> and how it is updated (I assume the data needs to be updated in close to
> real-time)?

You must be using a relatively old kernel to have such a device name...

Anyway, the files in question are created by whatever hardware
monitoring driver your system is using. To find out which it is, look
at the "driver" link in this directory.

The data in these files are updated only when you read from them, and
are cached for a short period of time (1 to 2 seconds, depends on the
driver) to prevent a given user from causing too much I/O traffic to
the monitoring chip.

To answer your question more generically: you can ask libsensors for a
specific input value, however the sensors command-line tool doesn't
offer any interface for this so you would have to either add it or
write your own little program interfacing with libsensors. The
alternative is to read from /sys directly, as you already found out,
but then you lose the labelling and scaling facilities of libsensors.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2008-09-05  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 18:38 [lm-sensors] Single Sensor Check sensored
2008-08-16  0:17 ` Matt Roberds
2008-09-02 21:31 ` sensored
2008-09-05  8:44 ` Jean Delvare [this message]

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=20080905104430.259c32f3@hyperion.delvare \
    --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.