From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pali Roh?r <pali.rohar@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Felipe Contreras <felipe.contreras@nokia.com>,
linux-main <linux-kernel@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Aliaksei Katovich <aliaksei.katovich@nokia.com>,
Vladimir Zapolskiy <vz@mleia.com>
Subject: Re: [PATCH] mfd: add bq2415x charger driver
Date: Tue, 6 Dec 2011 11:25:31 +0000 [thread overview]
Message-ID: <20111206112531.GD17194@sirena.org.uk> (raw)
In-Reply-To: <8650361.EbH1hYJT76@pali-elitebook>
On Tue, Dec 06, 2011 at 08:25:49AM +0100, Pali Roh?r wrote:
> On Tuesday 06 December 2011 02:12:47 you wrote:
> > Also, I'm not familiar with the regulator interface, but it seems to
> > be meant for real regulators, which have consumers, and based on those
> > consumers's needs the real voltage changes. This battery charger on
> > the other hand doesn't have anything like that. There will be no
> > consumer, and some stuff like the weak battery voltage is not even
> > related to a voltage supply, but rather a threshold that can be
> > configured to change some behavior of the charger, but there's no
> > point in changing it dynamically (or maybe at all).
> If regulator interface is not good, I can change it to some sysfs interface.
> But bq2415x chip driver is not only rx51 specified, so it should handle all
> chip capabilities.
It's been used by a few charger drivers not for the voltage regulation
but for the current regulation interface - it does provide an
abstraction allowing the battery driver to vary the current going into
the battery independantly of the thing regulating that current. This
does depend on what control the charger offers, some are designed to be
more autonomous than others.
next prev parent reply other threads:[~2011-12-06 11:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 22:35 [PATCH] mfd: add bq2415x charger driver Felipe Contreras
2011-12-05 22:51 ` Felipe Contreras
2011-12-05 23:05 ` Pali Rohár
2011-12-06 0:12 ` Felipe Contreras
2011-12-06 7:25 ` Pali Rohár
2011-12-06 10:58 ` Felipe Contreras
2011-12-06 13:27 ` Pali Rohár
2011-12-06 14:11 ` Felipe Contreras
2011-12-06 15:19 ` Pali Rohár
2011-12-06 11:25 ` Mark Brown [this message]
2011-12-06 2:17 ` Sebastian Reichel
2011-12-06 2:49 ` Felipe Contreras
2011-12-06 13:21 ` Sebastian Reichel
2011-12-06 13:50 ` Felipe Contreras
2011-12-06 13:34 ` Pali Rohár
2011-12-06 11:31 ` Mark Brown
2011-12-06 11:43 ` Felipe Contreras
2011-12-06 11:46 ` Mark Brown
2011-12-07 21:03 ` RFC: bq2415x_charger driver Pali Rohár
2011-12-07 21:25 ` Vladimir Zapolskiy
2011-12-07 21:40 ` Pali Rohár
2012-01-27 2:40 ` RFC 2: " Pali Rohár
2012-01-27 16:24 ` Mark Brown
2012-01-27 18:33 ` Pali Rohár
2012-01-27 19:22 ` Mark Brown
2012-01-27 20:40 ` Sebastian Reichel
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=20111206112531.GD17194@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=aliaksei.katovich@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sameo@linux.intel.com \
--cc=vz@mleia.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