From: "Mark A. Greer" <mgreer@animalcreek.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Subject: Re: bq24190: What's the correct API to turn boost mode (OTG) on for the battery charger ?
Date: Wed, 21 May 2014 12:01:30 -0700 [thread overview]
Message-ID: <20140521190130.GA29941@animalcreek.com> (raw)
In-Reply-To: <20140521182543.GA28477@animalcreek.com>
[Removing Anton from CC]
On Wed, May 21, 2014 at 11:25:43AM -0700, Mark A. Greer wrote:
> On Fri, May 16, 2014 at 12:35:34AM +0200, Laurent Pinchart wrote:
> > Hi Mark,
> >
> > Thank you for the quick reply.
>
> Hi Laurent. Sorry for the delay.
>
> > On Thursday 15 May 2014 15:08:44 Mark A. Greer wrote:
> > > On Thu, May 15, 2014 at 10:29:26PM +0200, Laurent Pinchart wrote:
> > > > Hello,
> > >
> > > [Adding Anton Vorontsov to CC list.]
> > >
> > > Hi Laurent.
> > >
> > > > I'm trying to enable battery charging on an OMAP4 board based on a twl6030
> > > > PMIC with external bq24190 battery charger and bq27510 fuel gauge.
> > > >
> > > > The system has an OTG USB port that can be used to charge the battery, and
> > > > that can also be used in host mode. In that case the bq24190 needs to be
> > > > switched to boost mode to provide the +5V power supply from the battery.
> > > >
> > > > The bq24190 has a charge configuration register field that supports charge
> > > > disabled, charge enabled and OTG (boost mode). The field is set by the
> > > > bq24190 driver in response to setting the charge type :
> > > > POWER_SUPPLY_CHARGE_TYPE_NONE will disable charing, and
> > > > POWER_SUPPLY_CHARGE_TYPE_TRICKLE and
> > > > POWER_SUPPLY_CHARGE_TYPE_FAST will enable it. However, OTG boost mode is
> > > > not supported.
> > > >
> > > >
> > > > The driver exposes most register fields as sysfs attributes (which doesn't
> > > > sound very safe to me, but that's another story). I can thus enable OTG
> > > > boost mode directly from userspace through the driver-specific API, but
> > > > that just bypasses the power supply API. I'm thus not very fond of that
> > > > solution.
> > >
> > > No, its not a good solution. As indicated in the commit log, the sysfs
> > > entries are there because there are just so many fields that don't map
> > > well to the existing interface.
> > >
> > > Maybe we should add support for a DT entry to enable exporting those
> > > fields(disabled by default)?
> > >
> > > > Possibly due to my really basic (not to say nonexistent) knowledge of the
> > > > power supply subsystem I haven't found an API to expose this feature. I
> > > > was wondering if someone had given a though regarding how to implement
> > > > this properly.
> > >
> > > What if we just added something like POWER_SUPPLY_CHARGE_TYPE_BOOST?
> >
> > That was actually my first thought, and I assumed it would be rejected as
> > boost mode is not a charge type but a discharge type :-)
>
> Er, right. :(
>
> > This being said, I
> > don't have enough experience with battery chargers to decide whether this is a
> > good solution. If you believe it is, I'll trust you on that.
>
> No, you're right, that isn't a good solution.
>
> I don't see a really good fit anywhere. The easiest thing may be to add
> a new POWER_SUPPLY_PROP_xxx power_supply_property member which can be set
> to flip it into boost mode but I'm not sure if that's really the right
> thing to do.
>
> I hope Anton will comment on this.
After looking at MAINTAINERS and its git log, it looks like Dmitry has
taken over.
Dmitry, do you have anything insight?
Mark
--
prev parent reply other threads:[~2014-05-21 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 20:29 bq24190: What's the correct API to turn boost mode (OTG) on for the battery charger ? Laurent Pinchart
2014-05-15 22:08 ` Mark A. Greer
2014-05-15 22:35 ` Laurent Pinchart
2014-05-21 18:25 ` Mark A. Greer
2014-05-21 18:32 ` Mark A. Greer
2014-05-21 19:01 ` Mark A. Greer [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=20140521190130.GA29941@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=laurent.pinchart@ideasonboard.com \
--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