linux-kernel - Re: Adding USB charge current property in the Linux Battery core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111109082005.GH23337@legolas.emea.dhcp.ti.com>
Date:	Wed, 9 Nov 2011 10:20:05 +0200
From:	Felipe Balbi <balbi@...com>
To:	ashishj3 <ashish.jangam@...tcummins.com>
Cc:	linaro-dev@...ts.linaro.org, linux-kernel@...r.kernel.org,
	arnd@...db.de, eric.miao@...aro.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
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.

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

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)