Hi all, The following RFC (yes, another one) is to show what I'm willing to achieve with musb. MUSB is used in several ways: 1. integrated in omap2430 and onwards 2. integrated in DaVinci chips 3. integrated in Blackfin chips 4. tusb6010 as a discrete chip connected to omap via gpmc 5. PCI card (the old OPT) 7. other possibilities. >From those cases, some will have controllable clocks (omap, davinci, etc) and some won't (pci, blackfin). With such a diverse "ecosystem" it's rather complicated to make a usable driver on all cases. It's also complicated to make such a driver be compile-tested easily unless we reconfigure the kernel tree before each compilation cycle. My way of tackling such problem (and allow multi-omap builds to be bootable) is to split out the HW glue layer into it's own platform_device which instantiates musb-hdrc platform_device. The final goal, is that musb-core doesn't have to care about clocks, PM, context save/restore or anything which is HW-specific; those will all be done by the HW platform_device. Please, take a look at the following RFC and comment on how you feel about it. -- 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
