From: Julian Andres Klode <jak@jak-linux.org>
To: Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Matthew Garrett <matthew.garrett@nebula.com>
Cc: Julian Andres Klode <jak@jak-linux.org>,
ibm-acpi-devel@lists.sourceforge.net (open list:THINKPAD ACPI
EXT...),
platform-driver-x86@vger.kernel.org (open list:THINKPAD ACPI
EXT...), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 0/4] thinkpad_acpi: Add support for controlling charge thresholds
Date: Mon, 11 Nov 2013 14:56:29 +0100 [thread overview]
Message-ID: <1384178195-12218-1-git-send-email-jak@jak-linux.org> (raw)
This patch series adds support for specifying charging thresholds,
forcing a battery to discharge, and inhibiting charging, on ThinkPad
Laptops using Sandy Bridge or newer processors.
The first two patches should be stable now, the third one does not work on
my test system (but I'd appreciate if anyone with something other than an
X230 tests it).
The inhibit charging part is a bit unprecise, and I can obviously not test
that -1 really means permanently, but I assume it does. I don't know whether
this one should be merged.
Changes since the RFC PATCH:
- Define batteries more dynamically instead of statically using large
macros. Added support for up to 3 batteries, unsupported ones will not
be exported.
- Added 3 more new patches with more features
Julian Andres Klode (4):
thinkpad_acpi: Add support for controlling charge thresholds
thinkpad_acpi: battery: Add force_discharge attribute
thinkpad_acpi: battery: Add force_discharge_ac_break attribute
thinkpad_acpi: battery: Add inhibit_charge_minutes attribute
Documentation/laptops/thinkpad-acpi.txt | 37 ++++
drivers/platform/x86/thinkpad_acpi.c | 300 ++++++++++++++++++++++++++++++++
2 files changed, 337 insertions(+)
--
1.8.4.2
next reply other threads:[~2013-11-11 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 13:56 Julian Andres Klode [this message]
2013-11-11 13:56 ` [PATCH 1/4] thinkpad_acpi: Add support for controlling charge thresholds Julian Andres Klode
2013-11-13 13:50 ` Julian Andres Klode
2013-12-30 13:29 ` Julian Andres Klode
2013-12-30 21:58 ` Henrique de Moraes Holschuh
2013-12-30 22:40 ` Henrique de Moraes Holschuh
2013-12-31 0:01 ` Julian Andres Klode
2013-12-31 12:12 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2013-12-31 22:46 ` Julian Andres Klode
2014-04-06 12:14 ` Julian Andres Klode
2014-04-09 18:00 ` Henrique de Moraes Holschuh
2013-11-11 13:56 ` [PATCH 2/4] thinkpad_acpi: battery: Add force_discharge attribute Julian Andres Klode
2013-11-11 13:56 ` [PATCH 3/4] thinkpad_acpi: battery: Add force_discharge_ac_break attribute Julian Andres Klode
2013-11-11 13:56 ` [PATCH 4/4] thinkpad_acpi: battery: Add inhibit_charge_minutes attribute Julian Andres Klode
2013-11-25 14:59 ` [PATCH 0/4] thinkpad_acpi: Add support for controlling charge thresholds Julian Andres Klode
2013-12-28 21:10 ` Julian Andres Klode
2013-12-28 22:10 ` Henrique de Moraes Holschuh
2013-12-30 13:26 ` Julian Andres Klode
2013-12-30 20:06 ` Henrique de Moraes Holschuh
2014-01-20 21:22 ` 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=1384178195-12218-1-git-send-email-jak@jak-linux.org \
--to=jak@jak-linux.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--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