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 <[email protected]> for suggesting
that.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
