From: Pavel Machek <pavel@ucw.cz>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
lenb@kernel.org, rui.zhang@intel.com,
linux-kernel <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH v3] hwmon driver for ACPI 4.0 power meters
Date: Wed, 9 Sep 2009 10:06:38 +0200 [thread overview]
Message-ID: <20090909080637.GA28353@elf.ucw.cz> (raw)
In-Reply-To: <20090908202410.GS10521@tux1.beaverton.ibm.com>
Hi!
> diff --git a/Documentation/hwmon/acpi_power_meter b/Documentation/hwmon/acpi_power_meter
> new file mode 100644
> index 0000000..b02ddaa
> --- /dev/null
> +++ b/Documentation/hwmon/acpi_power_meter
> @@ -0,0 +1,31 @@
> +Kernel driver power_meter
> +=========================
> +
> +This driver talks to ACPI 4.0 power meters.
> +
> +Supported systems:
> + * Any recent system with ACPI 4.0.
> + Prefix: 'power_meter'
> + Datasheet: http://acpi.info/, section 10.4.
> +
> +Author: Darrick J. Wong
> +
> +Description
> +-----------
> +
> +This driver implements sensor reading support for the power meters exposed in
> +the ACPI 4.0 spec (Chapter 10.4). These devices have a simple set of
> +features--a power meter that returns average power use over a configurable
> +interval, an optional capping mechanism, and a couple of trip points.
So where do we get the average power?
> +Special Features
> +----------------
> +
> +The power[1-*]_is_battery knob indicates if the power supply is a battery.
> +Both power[1-*]_average_{min,max} must be set before the trip
> points will work.
How do trip points work? It is not explained here.
> +config ACPI_POWER_METER
> + tristate "ACPI 4.0 power meter"
> + depends on HWMON
> + default m
default M is "evil".
> + devices. Say Y (or M) if you have an Intel or AMD computer with
> + a power meter.
WTF? Neither Intel nor AMD makes _computers_.
> + To compile this driver as a module, choose M here:
> + the module will be called power-meter.
.ko.
> +#define POWER_CAP_NAME "power1_cap"
I did not see power cap explained.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-09 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200908202049.n7KKnKO7015060@imap1.linux-foundation.org>
[not found] ` <20090820211557.GA8431@elf.ucw.cz>
[not found] ` <20090820213755.GB10521@tux1.beaverton.ibm.com>
[not found] ` <20090821091939.GC21167@elf.ucw.cz>
[not found] ` <20090821184718.GD23397@tux1.beaverton.ibm.com>
[not found] ` <20090821221705.GA2108@elf.ucw.cz>
[not found] ` <20090822011744.GH10521@tux1.beaverton.ibm.com>
[not found] ` <20090821140159.GB1328@ucw.cz>
2009-09-08 20:24 ` [PATCH v3] hwmon driver for ACPI 4.0 power meters Darrick J. Wong
2009-09-09 8:06 ` Pavel Machek [this message]
2009-09-09 18:20 ` Darrick J. Wong
2009-09-09 21:27 ` Pavel Machek
2009-09-09 22:14 ` Darrick J. Wong
2009-09-09 18:23 ` [PATCH v4] " Darrick J. Wong
2009-09-09 21:29 ` Pavel Machek
2009-09-09 22:13 ` [PATCH v5] " 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=20090909080637.GA28353@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=djwong@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mm-commits@vger.kernel.org \
--cc=rui.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox