Hi George, On 29 April 2014 04:58, George Cherian <[email protected]> wrote: > On 4/29/2014 11:49 AM, Yegor Yefremov wrote: >> >> On Thu, Apr 24, 2014 at 11:11 PM, Ezequiel Garcia >> <[email protected]> wrote: >>> >>> The DMA controller is needed for the USB controller to be correctly >>> registered. Therefore, if the DMA node is located at the end an >>> unecessary >>> probe deferral is produced systematically. >>> >>> This is easily fixed by moving the node at the beggining of the child >>> list, >>> so it's probed first. > > This will give issues on module removal. > Since we use device_for_each_child in remove patch, it will try to remove > cppi dma controller, while the channel > is still in use by musb node. >
OK, this seems confusing: are you sure module removal works? Doing this simple test on v3.15-rcN: $ modprobe musb_dsps $ modprobe musb_am335x $ modprobe musb_am335x -r And the kernel blows up :-( I've been debugging this and I think we simply cannot support removal of the musb_am335x module. Had this ever worked before? -- Ezequiel García, VanguardiaSur www.vanguardiasur.com.ar -- 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
