Comment 0 for bug 759913

basically the device is not added to the platform bus, and thus the driver cannot attach to a non-existent device:

[flag@newluxor canonical]$ grep musb dmesg-2.6.38.txt
[ 0.332000] bus_add_driver::636 bus: 'platform': add driver musb-tusb
[ 0.382751] musb_init::2434
[ 0.382751] musb-hdrc: version 6.0, tusb-omap-dma, otg (peripheral+host), debug=0
[ 0.382781] bus_add_driver::636 bus: 'platform': add driver musb-hdrc
[ 0.382934] musb_init::2463 ret: -19

#define ENODEV 19 /* No such device */

[flag@newluxor canonical]$ grep musb dmesg-2.6.37.txt
[ 0.000000] bus_add_device::457 bus: 'platform': add device musb_hdrc
[ 0.048736] musb_init::2488
[ 0.048767] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
[ 0.048797] bus_add_driver::637 bus: 'platform': add driver musb_hdrc
[ 0.048919] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[ 0.048919] musb_hdrc: MHDRC RTL version 1.800
[ 0.048950] musb_hdrc: setup fifo_mode 4
[ 0.048950] musb_hdrc: 28/31 max ep, 16384/16384 memory
[ 0.049133] musb_hdrc musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
[ 0.049224] musb_init::2517 ret: 0

it's simply a config difference introduced in 5bfc8061 (while rebasing on 2.6.38-rc1), when USB_MUSB_TUSB6010 was picked instead of USB_MUSB_OMAP2PLUS.