From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felipe Balbi Subject: Re: Initialization of musb on board-omap2beagle fails in platform_driver_probe Date: Mon, 28 Mar 2011 11:37:22 +0300 Message-ID: <20110328083721.GE2251@legolas.emea.dhcp.ti.com> References: <87hbap5tzp.fsf@gmail.com> Reply-To: balbi@ti.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog104.obsmtp.com ([74.125.149.73]:43268 "EHLO na3sys009aog104.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750921Ab1C1Ih0 (ORCPT ); Mon, 28 Mar 2011 04:37:26 -0400 Content-Disposition: inline In-Reply-To: <87hbap5tzp.fsf@gmail.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Ben Gamari Cc: linux-usb@vger.kernel.org, Beagle Board , linux-omap Hi, On Sat, Mar 26, 2011 at 07:42:34PM -0400, Ben Gamari wrote: > Today I've had a very frustrating time trying to bring up a BeagleBoard > (arch/arm/mach-omap2/board-omap2beagle.c) with the 2.6.38 there's no board-omap2beagle > kernel. Unfortunately musb has been giving me great difficulties, > > # modprobe g_ether > [ 25.276855] usb_gadget_probe_driver 1815: usb_gadget_probe_driver, no dev?? > modprobe: Failed to load module g_ether: No such device. > > After a great deal of printking, I've determined that the error is > coming from platform_driver_probe (platform.c:499). The code in question > appears to be a check ensuring that any devices being probe were first > registered. When the musb-hdrc module is probed, this check seems to > fail with code = 1 and list_empty(&drv->driver.p->klist_devices.k_list) > = 1. looking at your .config from previous mail, it's wrong. You're trying to use am35x glue layer while you be using omap2430, just change: - CONFIG_USB_MUSB_AM35X=y + # CONFIG_USB_MUSB_AM35X is not set + CONFIG_USB_MUSB_OMAP2PLUS=y -- balbi