public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: maximilian attems <max@stro.at>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Len Brown <len.brown@intel.com>,
	linux-acpi@vger.kernel.org, sjoerd@luon.net
Subject: Re: [PATCH] ACPI: battery: add sysfs serial number
Date: Wed, 23 Jan 2008 11:18:32 +0100	[thread overview]
Message-ID: <20080123101832.GB4718@stro.at> (raw)
In-Reply-To: <479632AB.2030709@suse.de>

[ added debian hal maintainer on cc ]

On Tue, 22 Jan 2008, Alexey Starikovskiy wrote:

> maximilian attems wrote:
>> while checking the missing bits of ACPI_SYSFS_POWER versus
>> ACPI_PROCFS_POWER i also noticed capacity granularity.
>> is that used by anyone?
> IMHO, nobody cares about it.

ack, will add if someone cries.

>> if yes i can send another patch for that too.
> SBS (sbs.c) has cycle_count field, which might be useful too, so you might 
> want to show it as well.

i see, need to testboot to see if my first try went right.

>> want to switch debian to ACPI_SYSFS_POWER.
> Good luck!

done on the linux side.
thanks. :)

got the following question:
~/src/hal$ egrep 'voltage_(max|min)_design' -r .
./hald/linux/device.c:  if (hal_util_get_int_from_file (path, "voltage_max_design", &voltage_design, 10)) {

any particular reason the kernel is calling it
cat /sys/class/power_supply/BAT0/voltage_min_design 
14400000

shall i send in a patch along the line:
-       case POWER_SUPPLY_PROP_VOLTAGE_MIN_DESIGN:
+       case POWER_SUPPLY_PROP_VOLTAGE_MAX_DESIGN:
                val->intval = battery->design_voltage * 1000;

or is it hal beeing silly?

-- 
maks

  reply	other threads:[~2008-01-23 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 17:46 [PATCH] ACPI: battery: add sysfs serial number maximilian attems
2008-01-22 18:00 ` Alexey Starikovskiy
2008-01-22 18:07   ` maximilian attems
2008-01-22 18:15     ` Alexey Starikovskiy
2008-01-23 10:18       ` maximilian attems [this message]
2008-01-23 11:01         ` Alexey Starikovskiy
2008-01-23 11:15           ` Sjoerd Simons
2008-01-23 11:21             ` Alexey Starikovskiy
2008-02-03 11:02   ` maximilian attems
2008-02-06  2:09   ` Len Brown

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=20080123101832.GB4718@stro.at \
    --to=max@stro.at \
    --cc=astarikovskiy@suse.de \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=sjoerd@luon.net \
    /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