RE: Adding USB charge current property in the Linux Battery core

[Ashish Jangam <Ashish.Jangam@kpitcummins.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1490 bytes --]


> -----Original Message-----
> From: Felipe Balbi [mailto:balbi@ti.com]
> Sent: Wednesday, November 09, 2011 1:50 PM
> To: Ashish Jangam
> Cc: linaro-dev@lists.linaro.org; linux-kernel@vger.kernel.org;
> arnd@arndb.de; eric.miao@linaro.org; Mark Brown
> Subject: Re: Adding USB charge current property in the Linux Battery core
> 
> 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.
> 

This means that we need to modify the function usb_gadget_vbus_draw()
to add a call like blocking_notifier_call_chain() but will this be fine with
the usb gadget driver maintainers?

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


ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥