Hi, On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote: > On 03.04.2013 14:04, Felipe Balbi wrote: > > On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote: > > >> Felipe, could you explain the background on how the dsps driver is > >> supposed to work in host mode at boot time with the rework of the driver > >> you did for 3.7? It might just be me not understanding the rationale > >> behind all these changes, but appearantly, I'm not the only one who's > >> affected by that. > > > > right, so the idea with that was to drop the huge amount of ifdeferry > > hack from the MUSB driver. It would be great if someone would send > > *CLEAN* patches adding Kconfig-based role choices again. > > Are Kconfig-based rules really what we want here after all? Wouldn't > run-time configured settings make much more sense, considering that we need both. Say that you want to build a product with MUSB hardwired as host, why would you enable gadget framework ? I can think of at least am335x where this would be perfectly plausible (no EHCI available, only MUSB). > people might want to run a single kernel image on multiple platforms? I > believe it should be up to the DT to define the actual hardware wiring. Right, for runtime decision Ravi pointed me to a patch implementing that (Ravi, could you post it by any chance as RFC ?) which we could start a discussion and hopefully merge for v3.11 -- balbi
Attachment:
signature.asc
Description: Digital signature
