From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Arun Murthy <arun.murthy@stericsson.com>
Cc: dwmw2@infradead.org, linux-kernel@vger.kernel.org,
karl.komierowski@stericsson.com, johan.palsson@stericsson.com,
linus.walleij@linaro.org
Subject: Re: [PATCH 0/4] AB8500 Battery Management Driver
Date: Wed, 14 Mar 2012 04:59:01 +0400 [thread overview]
Message-ID: <20120314005901.GB1778@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1330532668-5673-1-git-send-email-arun.murthy@stericsson.com>
Hello Arun,
On Wed, Feb 29, 2012 at 09:54:24PM +0530, Arun Murthy wrote:
> Technical reference manual is available at
> http://www.stericsson.com/developers/CD00291561_UM1031_AB8500_user_manual-rev5_CTDS_public.pdf
>
> AB8500 battery driver consists of
> Generic charging algorithm(abx500-chargalg.c)
> Charger driver(ab8500-charger.c)
> Fuel Gauge driver(ab8500-fg.c)
> Battery temperature driver(ab8500-btemp.c)
> The power supply class driver can act as a supply as well as supplicant. Any
> state change in one power supply class driver can be notified to its
> supplicants using notification mechanism provided by Power Supply Class frame
> work. Each Power supply class driver lists its supplicant names in "supplied_to"
> struct member, and each power_supply_changed() call issued by power supply class
> driver will notify supplicants via external_power_changed callback.
A complex thing! Thanks for the driver, it's now applied.
p.s.
Would be nice if you have told that it depends on MFD changes
(i.e. is_ab8500_1p1_or_earlier() thing). :-) It builds with
linux-next (w/ a few small fixups, I'll send them as follow ups),
so it's fine.
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2012-03-14 0:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 16:24 [PATCH 0/4] AB8500 Battery Management Driver Arun Murthy
2012-02-29 16:24 ` [PATCH 1/4] power: abx500-chargalg: Add abx500 charging algorithm Arun Murthy
2012-02-29 16:24 ` [PATCH 2/4] power: ab8500-charger: AB8500 charger driver Arun Murthy
2012-02-29 17:50 ` Andi
2012-02-29 18:21 ` Arun Murthy
2012-02-29 16:24 ` [PATCH 3/4] power: ab8500-fg: A8500 fuel gauge driver Arun Murthy
2012-02-29 16:24 ` [PATCH 4/4] power: ab8500-btemp: AB8500 battery temperature driver Arun Murthy
2012-03-14 0:59 ` Anton Vorontsov [this message]
2012-03-14 1:04 ` [PATCH 1/6] ab8500_charger: Convert to the new USB OTG calls Anton Vorontsov
2012-03-14 4:03 ` Arun MURTHY
2012-03-14 1:05 ` [PATCH 2/6] ab8500_btemp: Get rid of 'enum adc_therm' Anton Vorontsov
2012-03-14 4:25 ` Arun MURTHY
2012-03-14 1:05 ` [PATCH 3/6] ab8500_fg: Get rid of 'struct v_to_cap' Anton Vorontsov
2012-03-14 4:36 ` Arun MURTHY
2012-03-14 1:05 ` [PATCH 4/6] ab8500_fg: Get rid of 'struct battery_type' Anton Vorontsov
2012-03-14 4:36 ` Arun MURTHY
2012-03-14 1:05 ` [PATCH 5/6] ab8500_fg: Fix copy-paste error Anton Vorontsov
2012-03-14 4:36 ` Arun MURTHY
2012-03-14 5:45 ` Arun MURTHY
2012-03-14 1:05 ` [PATCH 6/6] ab8500: Turn unneeded global symbols into local ones Anton Vorontsov
2012-03-14 4:37 ` Arun MURTHY
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=20120314005901.GB1778@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=arun.murthy@stericsson.com \
--cc=dwmw2@infradead.org \
--cc=johan.palsson@stericsson.com \
--cc=karl.komierowski@stericsson.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@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