From: Pavel Machek <pavel@ucw.cz>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: Stefan Lippers-Hollmann <s.L-H@gmx.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ilia Mirkin <imirkin@alum.mit.edu>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 3.14-rc: /proc/acpi/battery gone?
Date: Sat, 15 Mar 2014 17:05:45 +0100 [thread overview]
Message-ID: <20140315160545.GA6689@amd.pavel.ucw.cz> (raw)
In-Reply-To: <532471EC.1070107@intel.com>
Hi!
> >>>They have attempted to use the sysfs api, but apparently that
> >>>integration was done with an older version of that API. There's also
> >>>some attempt to get it to work with upower, but I couldn't figure out
> >>>how to make that work either on my (up-to-date gentoo) box. (TBH I
> >>>didn't spend more than an hour or two on it, so it may not be
> >>>impossible.)
> >>
> >>Tianyu, can you please have a look at this?
> >
> >Disclaimer, I've never used wmbattery so far.
> >
> >The current upstream version (2.42, released in early december 2013)
> >of wmbattery[1] no longer reads from /proc/acpi/ at all. Apparently
> >it changed to using upower by default, with non-default fall-backs for
> >reading from sysfs.
> >
> >The only change required for building upower with wmbattery 2.42
> >appears to be a new build-dependency on libupower-glib-dev (at least
> >on Debian, built from the upower source package). Given that this
> >version is present in Debian testing and unstable, I'd assume that it's
> >supposed to work using upower, although I haven't confirmed that myself.
> >
> >Judging from the Gentoo ebuild, you probably just have to add
> >"sys-power/upower" to the RDEPEND variable and make sure to build
> >wmbattery 2.42; this is untested.
> >
>
> Hi Stefan:
> I just glance wmbattery code. I find the code in the acpi.c is
> already using the new sysfs battery interfaces, right?
>
> ...
>
> #define SYSFS_PATH "/sys/class/power_supply"
>
> ...
> char *acpi_labels[] = {
> "uevent",
> "status",
> "BAT",
> "AC",
> "POWER_SUPPLY_CAPACITY=",
> "POWER_SUPPLY_??????_FULL_DESIGN=", /* CHARGE or ENERGY */
> "POWER_SUPPLY_PRESENT=",
> "POWER_SUPPLY_??????_NOW=",
> "POWER_SUPPLY_CURRENT_NOW=",
> "POWER_SUPPLY_STATUS=",
> #if ACPI_THERMAL
> "thermal_zone",
> #endif
> "POWER_SUPPLY_ONLINE=",
> "POWER_SUPPLY_??????_FULL=",
> NULL
> };
New kernel should work with old userspace... and clearly it does not.
Do you have test patch for a revert?
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:[~2014-03-15 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 21:14 3.14-rc: /proc/acpi/battery gone? Pavel Machek
2014-03-14 21:20 ` Pavel Machek
2014-03-14 21:29 ` Ilia Mirkin
2014-03-14 21:45 ` Richard Weinberger
2014-03-15 15:10 ` Lan Tianyu
2014-03-14 22:11 ` Pavel Machek
2014-03-14 22:14 ` Ilia Mirkin
2014-03-15 1:46 ` Rafael J. Wysocki
2014-03-15 2:17 ` Stefan Lippers-Hollmann
2014-03-15 15:29 ` Lan Tianyu
2014-03-15 16:05 ` Pavel Machek [this message]
2014-03-15 17:27 ` Lan Tianyu
2014-03-16 11:12 ` Pavel Machek
2014-03-16 3:57 ` Stefan Lippers-Hollmann
2014-03-17 17:28 ` Ilia Mirkin
2014-04-20 13:09 ` Pavel Machek
2014-04-21 11:29 ` Lan Tianyu
2014-03-15 14:08 ` Pavel Machek
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=20140315160545.GA6689@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=imirkin@alum.mit.edu \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=s.L-H@gmx.de \
--cc=tianyu.lan@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).