linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: ykzhao <yakui.zhao@intel.com>
Cc: Len Brown <lenb@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	lm-sensors <lm-sensors@lm-sensors.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH 2/2] acpi_power_meter: hwmon driver for ACPI 4.0 power meters
Date: Mon, 3 Aug 2009 13:48:18 -0700	[thread overview]
Message-ID: <20090803204817.GA14694@plum> (raw)
In-Reply-To: <1248659067.3556.70.camel@localhost.localdomain>

On Mon, Jul 27, 2009 at 09:44:27AM +0800, ykzhao wrote:
> On Sat, 2009-07-25 at 08:43 +0800, Darrick J. Wong wrote:
> > This driver exposes ACPI 4.0 compliant power meters as hardware monitoring
> > devices.
> It seems OK to me. But it seems that some attributes can't be obtained
> by using the hwmon sys I/F.
>    a. Can we add a sys I/F that can exports the Power meter capability?
> display all the content of _PMC as what we have done in battery

Are you talking about all 17 fields of the _PMC return value?  Or specifically
the feature bit field "Supported Capabilities"?  The feature bits control
whether or not the corresponding sysfs attributes even show up, and the other
fields (except the string data) are all there.  I suppose it would be useful to
display the OEM data too...

>    b. Add a sys I/F that displays the name of device list measured by
> the power meter if there exists the _PMD object.

As soon as I figure out how to do that. :)

Sorry for the slow response as I was mountain climbing = no Internet.

--D

  reply	other threads:[~2009-08-03 20:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25  0:43 [PATCH 0/2] ACPI 4.0 power meter Darrick J. Wong
2009-07-25  0:43 ` [PATCH 1/2] hwmon: Enhance the sysfs API for power meters Darrick J. Wong
2009-08-07 18:09   ` Pavel Machek
2009-08-08 17:40     ` Darrick J. Wong
2009-08-08 21:48       ` Pavel Machek
2009-08-10 21:12         ` Darrick J. Wong
2009-08-12 11:56           ` Pavel Machek
2009-08-18 23:32             ` Darrick J. Wong
2009-07-25  0:43 ` [PATCH 2/2] acpi_power_meter: hwmon driver for ACPI 4.0 " Darrick J. Wong
2009-07-27  1:44   ` ykzhao
2009-08-03 20:48     ` Darrick J. Wong [this message]
2009-07-27  6:45   ` Zhang Rui
2009-08-03 20:52     ` Darrick J. Wong
2009-07-28  1:25   ` Len Brown
2009-08-03 20:58     ` Darrick J. Wong
2009-08-06 20:42       ` [PATCH v2] " Darrick J. Wong
2009-08-17 22:05         ` Andrew Morton
2009-08-18 16:24           ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2009-08-18 23:47 [PATCH 0/2] ACPI 4.0 power meter Darrick J. Wong
2009-08-18 23:48 ` [PATCH 2/2] acpi_power_meter: hwmon driver for ACPI 4.0 power meters Darrick J. Wong
2009-08-20 23:47   ` Andrew Morton

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=20090803204817.GA14694@plum \
    --to=djwong@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=rui.zhang@intel.com \
    --cc=yakui.zhao@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;
as well as URLs for NNTP newsgroup(s).