From: "Heiko Stübner" <heiko@sntech.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Cc: linux-pm@lists.linux-foundation.org,
Philipp Zabel <philipp.zabel@gmail.com>
Subject: [PATCH v2 0/4] bq24022: Add support for bq2407x family
Date: Mon, 29 Aug 2011 17:55:14 +0200 [thread overview]
Message-ID: <201108291755.15701.heiko@sntech.de> (raw)
The bq2407x family is quite similar to the bq24022 charger.
As suggested by MyungJoo Ham it should be possible to implement
support for it inside the bq24022 driver instead of adding a new one.
The first three patches fix small things Mark Brown identified in my
submission of a separate bq2407x driver that also exist in the bq24022
while the fourth implements the bq2407x specifics.
This second version fixes some glitches found by Mark Brown and introduces
the new second patch fixing the other dev_dbg invocations where dev_err
would be appropriate.
Heiko Stuebner (4):
bq24022: Evaluate returns of gpio_direction_output-calls
bq24022: Use dev_err instead of dev_dbg for error messages to make
them visible
bq24022: Keep track of gpio states
bq24022: Add support for the bq2407x family
drivers/regulator/Kconfig | 7 +-
drivers/regulator/bq24022.c | 144
++++++++++++++++++++++++++++++-------
include/linux/regulator/bq24022.h | 7 ++
3 files changed, 128 insertions(+), 30 deletions(-)
--
1.7.2.3
next reply other threads:[~2011-08-29 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 15:55 Heiko Stübner [this message]
2011-08-29 15:56 ` [PATCH v2 1/4] bq24022: Evaluate returns of gpio_direction_output-calls Heiko Stübner
2011-08-30 10:39 ` Mark Brown
2011-08-29 15:57 ` [PATCH 2/4] bq24022: Use dev_err instead of dev_dbg for error messages Heiko Stübner
2011-08-30 10:40 ` Mark Brown
2011-08-29 15:58 ` [PATCH 3/4] bq24022: Keep track of gpio states Heiko Stübner
2011-08-29 15:59 ` [PATCH v2 4/4] bq24022: Add support for the bq2407x family Heiko Stübner
2011-08-30 10:52 ` Mark Brown
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=201108291755.15701.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=lrg@ti.com \
--cc=philipp.zabel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).