From: dirk.brandewie@gmail.com
To: linux-kernel@vger.kernel.org
Cc: cbouatmailru@gmail.com, dg77.kim@samsung.com,
kyungmin.park@samsung.com, myungjoo.ham@samsung.com,
Jason.Wortham@maxim-ic.com, bruce.e.robertson@intel.com,
Dirk Brandewie <dirk.brandewie@gmail.com>
Subject: [PATCH 0/5] MAX17042 add support for maxim POR procedure
Date: Tue, 24 Jan 2012 09:26:03 -0800 [thread overview]
Message-ID: <1327425968-21195-1-git-send-email-dirk.brandewie@gmail.com> (raw)
From: Dirk Brandewie <dirk.brandewie@gmail.com>
This patch set adds support for the power on reset procedure for the
max17042 battery fuel gauge and alert interrupts.
The accuracy of the fuel gauge is improved by configuring the fuel
gauge with the characterization data for the battery present in the
platform.
Changes since v3:
Patch added patch to fix scaling of VCELL register values reported
Capacity property now used the reported SOC register to account for
empty compensation in reported capacity.
Fixed sparse/smatch warnings
Changes since v2:
Dropped patch moving non-POR init to worker function.
Reorganized POR patch to only schedule worker thread if the fuel gauge
is in the POR state
Changes since v1:
Moved power_supply_register() back to the probe max17042_get_property()
will return -EAGAIN until the init function completes
Added support for interrupts from the alert pin if the platform has it
connected to an interrupt source.
Added fix for the values returned by POWER_SUPPLY_PROP_VOLTAGE_NOW
and POWER_SUPPLY_PROP_VOLTAGE_AVG.
Added Ack's from previous patch series
Bruce Robertson (1):
max17042: Fix value scaling for VCELL and avgVCELL
Dirk Brandewie (4):
max17042: Align register definitions with data sheet and init appnote
max17042: Add POR init procedure from Maxim appnote
max17042: Add support for signalling change in SOC
max17042: Change capacity property to use reported SOC register
drivers/power/max17042_battery.c | 452 +++++++++++++++++++++++++++++++-
include/linux/power/max17042_battery.h | 93 ++++++-
2 files changed, 522 insertions(+), 23 deletions(-)
--
1.7.7.5
next reply other threads:[~2012-01-24 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 17:26 dirk.brandewie [this message]
2012-01-24 17:26 ` [PATCH 1/5] max17042: Align register definitions with data sheet and init appnote dirk.brandewie
2012-01-24 17:26 ` [PATCH 2/5] max17042: Add POR init procedure from Maxim appnote dirk.brandewie
2012-01-24 17:26 ` [PATCH 3/5] max17042: Add support for signalling change in SOC dirk.brandewie
2012-01-24 17:26 ` [PATCH 4/5] max17042: Fix value scaling for VCELL and avgVCELL dirk.brandewie
2012-03-13 18:19 ` Anton Vorontsov
2012-03-13 21:00 ` bruce robertson
2012-03-13 21:04 ` Jason Wortham
2012-03-13 22:59 ` Dirk Brandewie
2012-03-14 0:04 ` Jason Wortham
2012-03-13 23:18 ` bruce robertson
2012-03-14 0:37 ` Jason Wortham
2012-01-24 17:26 ` [PATCH 5/5] max17042: Change capacity property to use reported SOC register dirk.brandewie
2012-03-13 18:34 ` Anton Vorontsov
2012-03-13 22:54 ` Dirk Brandewie
2012-02-28 16:17 ` [PATCH 0/5] MAX17042 add support for maxim POR procedure Dirk Brandewie
2012-03-13 18:48 ` Anton Vorontsov
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=1327425968-21195-1-git-send-email-dirk.brandewie@gmail.com \
--to=dirk.brandewie@gmail.com \
--cc=Jason.Wortham@maxim-ic.com \
--cc=bruce.e.robertson@intel.com \
--cc=cbouatmailru@gmail.com \
--cc=dg77.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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 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.