linux-kernel - Re: [PATCH] power_supply: Add driver for TWL4030/TPS65950 BCI charger

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: <20091210141830.GA10687@oksana.dev.rtsoft.ru>
Date:	Thu, 10 Dec 2009 17:18:30 +0300
From:	Anton Vorontsov <avorontsov@...mvista.com>
To:	Grazvydas Ignotas <notasas@...il.com>
Cc:	felipe.balbi@...ia.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

On Thu, Dec 10, 2009 at 04:09:08PM +0200, Grazvydas Ignotas wrote:
[...]
> > dedicated chargers are simple. You kick the charger detection according to
> > USB BC 1.x and if it returns true, you configure high current charging.
> > Host/Hub chargers are also simple, after kicking charger detection, you
> > enable Data pullups (e.g. SOFTCONN bit in musb's power register) and see if
> > the host sends a setup packet...
> >
> > the complicated part is passing the information of which configuration you
> > were enumerated with to the charger chip.
> 
> 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?

Works for me. Let's think of the kernel charging support as an
yet unimplemented feature.

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@...il.com
irc://irc.freenode.net/bd2
--
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/