Hi All,
i was earlier reporting USB problems with a DVEVM "alike" board. Later, it became clear, that the board was really unalike in a component critical to the kernel. Meanwhile i got an original DVEVM, and, to set the record straight, can report, that USB 2.0 works well here, both in PIO and DMA mode on the DVEVM board with a recent kernel. Technically, the "alike" board does not have a GPIO, (USB power is hardwired, there) but the DVEVM's USB driver initialisation code is indirectly hooked in the GPIO initialisation (CONFIG_GPIO_PCF857X), resulting in a never-registered HCD. Second point was control of the USB bus power in MUSB, which using the GPIO, is in fact specific to the DVEVM, as pointed out. It can easily be deactivated as it is under control of a define. Since the USB HCD initialisation is started at several ends, (musb, gpio, board-specifics, to name some), diagnosing and fixing the issue mainly meant to identify all these ends, which are all far apart from the USB sources. Because the comments in this thread were all very helpful for me, to collect all the necessary information, i write to express my thanks to the list. Kind regards Lars _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
