mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: ashishj3 <ashish.jangam@kpitcummins.com>
Cc: linaro-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
	arnd@arndb.de, eric.miao@linaro.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Adding USB charge current property in the Linux Battery core
Date: Wed, 9 Nov 2011 10:20:05 +0200	[thread overview]
Message-ID: <20111109082005.GH23337@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1320826417.1160.8.camel@L-0761.kpit.com>

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

Hi,

On Wed, Nov 09, 2011 at 01:43:37PM +0530, ashishj3 wrote:
> For a better performance in USB charging operation, the DA9052/53 charging
> current can be configured in accordance with the USB host current
> delivering capacity (known through USB drivers negotiation).
>  
> To implement this useful feature, a new writable property "USB charge current"
> needs to be added in the Linux battery core.
> 
> Let me know your views on it.

that's the wrong way to do it. What we need is to use the transceiver
notifications to notify every time someone calls usb_gadget_vbus_draw()
and pass the mA parameter as argument to the event notification.

Charger driver should 'subscribe' to transceiver notifications and
use the mA argument to reconfigure charging.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-09  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09  8:13 ashishj3
2011-11-09  8:20 ` Felipe Balbi [this message]
2011-11-09 12:13   ` Ashish Jangam
2011-11-09 12:19     ` Felipe Balbi
2011-11-09 12:30       ` Ashish Jangam
2011-11-09 12:33         ` Felipe Balbi

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=20111109082005.GH23337@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=arnd@arndb.de \
    --cc=ashish.jangam@kpitcummins.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eric.miao@linaro.org \
    --cc=linaro-dev@lists.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

all inboxes | Powered by JetHome®