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]
Date:	Thu, 10 Dec 2009 16:19:38 +0200
From:	Felipe Balbi <felipe.balbi@...ia.com>
To:	ext Grazvydas Ignotas <notasas@...il.com>
Cc:	"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@...ia.com>,
	Anton Vorontsov <avorontsov@...mvista.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Madhusudhan Chikkature <madhu.cr@...com>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: Re: [PATCH] power_supply: Add driver for TWL4030/TPS65950 BCI
 charger

Hi,

On Thu, Dec 10, 2009 at 03:09:08PM +0100, ext Grazvydas Ignotas wrote:
>Ok since it doesn't look like this will resolve soon, what about
>adding some DEVICE_ATTR for the time being and requiring userspace to
>write charge current here to start actual charging?

We can get the charging current from configuration.

When gadget driver call usb_gadget_vbus_draw() we can use that to pass 
the information somewhere else.

But what I'm doing now is implementing an atomic_notifier which will 
call whatever function another driver want whenever we have twl4030-usb 
irqs.

We can use that to kick the charger detection itself (on twl4030-usb) 
and you can register your notifier_block callback to enable charging as 
you wish.

Then we will have the charger detection done on the right place 
(twl4030-usb) and the charging start done on the right place 
(twl4030-bci or bq24xxx).

Thanks to Anton Vorontsov <avorontsov@...mvista.com> for suggesting 
that.

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ