On Tue, Dec 14, 2010 at 11:06:22AM +0200, Heikki Krogerus wrote:
On Mon, Dec 13, 2010 at 11:07:21AM +0200, ext Felipe Balbi wrote:
IMO, we need a drivers/usb/charging kinda thing grouping all of those.
Agreed. Now that I look what kind of solutions there are for USB
charging, it seems everybody creates their own. And since people are
providing more and more of these drivers, it's getting messy. I mean,
the concept is more or less the same, isn't it?
Even if we don't yet want to consider dedicated charger detection HW,
USB will always provide power. Would there be anyone interested in
making a common interface exposing this information to drivers that
need it? I'm sure it's easier to add support for common way of
detecting the actual chargers after we had something like this. Just
an idea. Maybe this would only make things worse.
I remember you have already talked about charging support Felipe, but
I don't remember what was the outcome?
so far nothing. I'm still playing with the generic UDC layer (hmm, gotta
really get back to those patches), then I'll need a generic transceiver
layer (it's getting normal to have more than one transceiver with
different capabilities on boards, see n900 for instance and any
OMAP4-based board), after that we can start looking into a generic USB
charging code, since transceiver details and UDC details will be more
abstracted.
Then we will also have a place to put all the notifications and
transceiver drivers won't have to care about those.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
