From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Lutomirski <luto@mit.edu>, Anton Vorontsov <cbou@mail.ru>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [ibm-acpi-devel] [RFC] Controlling the ThinkPad battery charger
Date: Tue, 10 May 2011 16:57:53 -0300 [thread overview]
Message-ID: <20110510195753.GA5850@khazad-dum.debian.net> (raw)
In-Reply-To: <20110510184302.GA15631@localhost.ucw.cz>
On Tue, 10 May 2011, Pavel Machek wrote:
> Hmm, I jave a battery pack with reasonably good cells, but firmware killed
> it. IOW available for testing.
That is likely a problem with the battery pack uC, we cannot override that
using any know firmware path in the ThinkPad.
Does the thinkpad recognizes the presence of the battery pack? If it
doesn't, the pack uC is probably dead or in safe mode, and you'd need to
hardware-hack it.
> (And who know, perhaps recalibrate command would bring it back to life?)
AFAIK, the recalibrate command really just does this:
1. sets 'force discharge' flag on EC so that it starts discharging the
battery pack. Discharging stops when cell voltage drops close to the
minimum safety level.
2. sets stop threshold to 0 (100%) for that battery pack.
That way, the box will fully-drain the pack, and then charge it to full. At
that point, the recalibration is complete (the battery pack uC will
auto-calibrate itself when it notices it has hit the fully-drained and
fully-charged points).
You can monitor per-cell-group voltages through tp_smapi on a original IBM
battery pack, that functionality should still be around on the Lenovos.
Since this is not standard SBS functionality, it might not work on
non-original battery packs.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2011-05-10 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 12:35 Andrew Lutomirski
2011-05-09 13:56 ` Matthew Garrett
2011-05-09 14:45 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2011-05-09 15:10 ` Andrew Lutomirski
2011-05-09 15:29 ` Henrique de Moraes Holschuh
2011-05-09 15:47 ` Andrew Lutomirski
2011-05-10 18:43 ` Pavel Machek
2011-05-10 19:57 ` Henrique de Moraes Holschuh [this message]
2011-05-10 20:58 ` 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=20110510195753.GA5850@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=cbou@mail.ru \
--cc=dwmw2@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
/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
all inboxes | Powered by JetHome®