From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Donggeun Kim <dg77.kim@samsung.com>
Cc: linux-pm@vger.kernel.org, len.brown@intel.com, pavel@ucw.cz,
rjw@sisk.pl, rdunlap@xenotime.net, pali.rohar@gmail.com,
prakity@mavell.com, broonie@opensource.wolfsonmicro.com,
lars@metafoo.de, kyungmin.park@samsung.com,
myungjoo.ham@samsung.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] power: introduce Charger-Manager
Date: Wed, 4 Jan 2012 08:11:03 +0400 [thread overview]
Message-ID: <20120104041103.GA12650@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1324979269-2453-1-git-send-email-dg77.kim@samsung.com>
On Tue, Dec 27, 2011 at 06:47:47PM +0900, Donggeun Kim wrote:
> Charger Manager provides in-kernel battery charger management that
> requires temperature monitoring during both normal and suspend-to-RAM states
> and where each battery may have multiple chargers attached and the userland
> wants to look at the aggregated information of the multiple chargers.
>
> Charger Manager is a platform_driver with power-supply-class entries.
> An instance of Charger Manager (a platform-device created with
> Charger-Manager) represents a battery with chargers. If there are multiple
> batteries with their own chargers acting independently in a system,
> the system may need multiple instances of Charger Manager.
> Multiple chargers (e.g., USB, wireless, and solar panels) may be included
> as pairs of a regulator and a power-supply-class
> per charger.
>
> Charger Manager glues multiple charger-related frameworks (regulators of
> chargers, power-supply-class from chargers and fuel-gauge, RTC,
> suspend-again, ...) together to provide aggregated information and
> transparent battery monitoring to userspace.
>
> For the discussions about the need for in-suspend monitoring, please
> refer to the discussions of suspend-again in PM:
> v1 https://lists.linux-foundation.org/pipermail/linux-pm/2011-April/031052.html
> v2 https://lists.linux-foundation.org/pipermail/linux-pm/2011-April/031111.html
> v3 https://lists.linux-foundation.org/pipermail/linux-pm/2011-May/031267.html
> v4 https://lists.linux-foundation.org/pipermail/linux-pm/2011-May/031357.html
> v5 (last, applied) https://lists.linux-foundation.org/pipermail/linux-pm/2011-June/031561.html
>
> To see the usage example, please refer to:
> http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads/charger-manager
> In this git branch, a test code for Exynos4-NURI is shown.
>
> This patch set supports initial Charger Manager driver.
Merged, thanks! I'm pretty excited, we have a full fledged charger
manager, yay! :-)
Please send all further improvements against these patches, or (better)
against battery-2.6.git tree: http://git.infradead.org/battery-2.6.git
Much thanks for your hard work! Also million thanks to reviewers!
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
prev parent reply other threads:[~2012-01-04 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 9:47 [PATCH v3 0/2] power: introduce Charger-Manager Donggeun Kim
2011-12-27 9:47 ` [PATCH v3 1/2] power: Charger-Manager: add initial Charger-Manager driver Donggeun Kim
2011-12-27 11:36 ` Mark Brown
2011-12-28 5:00 ` Donggeun Kim
2011-12-27 9:47 ` [PATCH v3 2/2] power: Charger-Manager: add properties for power-supply-class Donggeun Kim
2011-12-27 10:55 ` [PATCH v3 0/2] power: introduce Charger-Manager Mark Brown
2011-12-28 4:48 ` Donggeun Kim
2011-12-28 11:05 ` Mark Brown
2012-01-02 9:49 ` [PATCH] regulator: add regulator_force_disable() definition for !CONFIG_REGULATOR MyungJoo Ham
2012-01-02 11:40 ` Mark Brown
2012-01-04 4:11 ` Anton Vorontsov [this message]
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=20120104041103.GA12650@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dg77.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lars@metafoo.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=prakity@mavell.com \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.