Hi, On Thu, Dec 23, 2010 at 11:13:36PM +0800, tom.leiming@xxxxxxxxx wrote:
This patche set removes dependency on the following config option in musb driver: CONFIG_USB_MUSB_OMAP2PLUS CONFIG_USB_MUSB_TUSB6010 CONFIG_USB_MUSB_AM35X CONFIG_USB_MUSB_DAVINCI CONFIG_USB_MUSB_DA8XX CONFIG_USB_MUSB_UX500 also removes the dma controller related config options below from musb source code, and only keep very few of them in header file: CONFIG_USB_INVENTRA_DMA CONFIG_USB_TUSB_OMAP_DMA CONFIG_USB_TI_CPPI_DMA so musb driver source code is more clean than before, :-). The patch set makes full use of the hw glue layer implemented by Felipe. Since all the specific hardwares' related option are removed, we can build one single musb driver(binary) to make it working on multiple machines of same ARCH. Also the patches support the features below: - each glue driver can be compiled as one standalone module - each dma controler driver can be compiler as one standalone module The patch set has been tested on beagle xM, g_ether/g_zero in gadget mode are OK and mass storage/usb hub function in host mode are OK even both OMAP2PLUS, TUSB6010 and AM35X are enabled and the three modules are built in one image at the same time. The patch set is against 2.6.37-rc6-next-20101217 plus the musb fix patch with title below: usb: musb: fix kernel panic during s2ram(v2) v2: - fix musb_platform_get_hw_revision reported by Felipe - coding style fix reported by Sergei - fix dma controller name reported by Sergei and Felipe - define is_inventra_dma/is_cppi_enabled/tusb_dma_omap in musb_dma.h, reported by Sergei and Felipe Thanks Sergei and Felipe. v1: - export symbols as GPL - UX500 cleanup - sync with -next tree - other suggestions from Felipe
I applied these to musb-next branch. I can still take changes to those patches, of course, but it's easier if people want to test. -- 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