All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH 1/2] Define sysfs interfaces for ibmaem
Date: Tue, 01 Apr 2008 08:47:47 +0000	[thread overview]
Message-ID: <20080401084747.GE7183@tree.beaverton.ibm.com> (raw)
In-Reply-To: <20080401102228.712acbb5@hyperion.delvare>

[Got in a car accident tonight; replies will be scarce for the next week
or two.... :(]

On Tue, Apr 01, 2008 at 10:22:28AM +0200, Jean Delvare wrote:

> OK. Another question that comes to my mind now is the unit... Do the
> chips express the value in Joules internally? I would have expected
> Watt-hours. Of course we can convert as needed, but if all known chips
> use the same unit then I think we should that unit too, to minimize the
> required conversions.

The IBM chips report some form of Joules, not Wh.

> It really depends on what the chips report. Typically the drivers
> should report the values from the chip without too much tinkering
> (other than conversion to standard units). If some chips can report
> both "instantaneous" and "average" power uses, it makes sense to have
> both sets of filenames in the standard interface. If not then I am fine
> getting rid of one set.

Hmm, I'll think about what I want to do with this.  Probably just leave
them.

> I don't think there is any precedent yet. I suggested this for
> unambiguity rather than consistency.

Ok.

> Oh well, I guess that anything shorter than 1 ms can be considered
> "instantaneous power use", so we can go with millisecond.

Ok.

> Out of curiosity, what are the values supported by the ibmaem chip?

I don't know what the lower limits are; it depends on how often the BMC
decides to update the counters, and that seems to vary by machine.

--D

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

WARNING: multiple messages have this Message-ID (diff)
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH 1/2] Define sysfs interfaces for ibmaem driver
Date: Tue, 1 Apr 2008 01:47:47 -0700	[thread overview]
Message-ID: <20080401084747.GE7183@tree.beaverton.ibm.com> (raw)
In-Reply-To: <20080401102228.712acbb5@hyperion.delvare>

[Got in a car accident tonight; replies will be scarce for the next week
or two.... :(]

On Tue, Apr 01, 2008 at 10:22:28AM +0200, Jean Delvare wrote:

> OK. Another question that comes to my mind now is the unit... Do the
> chips express the value in Joules internally? I would have expected
> Watt-hours. Of course we can convert as needed, but if all known chips
> use the same unit then I think we should that unit too, to minimize the
> required conversions.

The IBM chips report some form of Joules, not Wh.

> It really depends on what the chips report. Typically the drivers
> should report the values from the chip without too much tinkering
> (other than conversion to standard units). If some chips can report
> both "instantaneous" and "average" power uses, it makes sense to have
> both sets of filenames in the standard interface. If not then I am fine
> getting rid of one set.

Hmm, I'll think about what I want to do with this.  Probably just leave
them.

> I don't think there is any precedent yet. I suggested this for
> unambiguity rather than consistency.

Ok.

> Oh well, I guess that anything shorter than 1 ms can be considered
> "instantaneous power use", so we can go with millisecond.

Ok.

> Out of curiosity, what are the values supported by the ibmaem chip?

I don't know what the lower limits are; it depends on how often the BMC
decides to update the counters, and that seems to vary by machine.

--D

  reply	other threads:[~2008-04-01  8:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:36 [lm-sensors] [PATCH 1/2] Define sysfs interfaces for ibmaem driver Darrick J. Wong
2008-03-28 21:36 ` Darrick J. Wong
2008-03-29 13:56 ` [lm-sensors] [PATCH 1/2] Define sysfs interfaces for ibmaem Jean Delvare
2008-03-29 13:56   ` [PATCH 1/2] Define sysfs interfaces for ibmaem driver Jean Delvare
2008-03-31 19:55   ` [lm-sensors] [PATCH 1/2] Define sysfs interfaces for ibmaem Wes Felter
2008-03-31 19:55     ` [PATCH 1/2] Define sysfs interfaces for ibmaem driver Wes Felter
2008-03-31 21:01   ` [lm-sensors] [PATCH 1/2] Define sysfs interfaces for ibmaem Darrick J. Wong
2008-03-31 21:01     ` [PATCH 1/2] Define sysfs interfaces for ibmaem driver Darrick J. Wong
2008-04-01  8:22     ` [lm-sensors] [PATCH 1/2] Define sysfs interfaces for ibmaem Jean Delvare
2008-04-01  8:22       ` [PATCH 1/2] Define sysfs interfaces for ibmaem driver Jean Delvare
2008-04-01  8:47       ` Darrick J. Wong [this message]
2008-04-01  8:47         ` Darrick J. Wong

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=20080401084747.GE7183@tree.beaverton.ibm.com \
    --to=djwong@us.ibm.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mhoffman@lightlink.com \
    /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.