Hi,

i am moving from kernel 3.5.1 to 3.17, on a custom AM1808(arm) based
board.I could have host usb working inserting a usb key, but after
removing it, a second insertion of the stick is not detected anymore.

I had to enable the broken Kconfig option into /drivers/usb/musb/Kconfig:

 config USB_MUSB_DAVINCI

 config USB_MUSB_DA8XX
    tristate "DA8xx/OMAP-L1x"
    depends on ARCH_DAVINCI_DA8XX
-   depends on BROKEN


Even if the driver can work in OTG mode, i set up the MUSB controller
driver to work in MUSB_HOST mode, as it was in kernel 3.5.1, enabling the
same .config and board options.

Seems like something get corrupted after the first usb stick removal.

dmesg, booting

...
davinci_mmc da830-mmc.1: Can't get dma_tx channel
davinci_mmc da830-mmc.1: Using PIO, 4-bit mode
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
davinci-mcbsp davinci-mcbsp.0: Runtime PM disabled, clock forced on.
davinci-mcbsp davinci-mcbsp.0: Runtime PM disabled, clock forced on.
....

then, i insert the usb stick:

[root@test ~]#
usb 1-1: new high-speed USB device number 2 using musb-hdrc
usb-storage 1-1:1.0: USB Mass Storage device detected
scsi host0: usb-storage 1-1:1.0
scsi 0:0:0:0: Direct-Access     USB 2.0  USB Flash Drive  1100 PQ: 0 ANSI: 4
sd 0:0:0:0: [sda] 31950720 512-byte logical blocks: (16.3 GB/15.2 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
Automount: /dev/sda1 inserted
Creating /tmp/.usbmstg0p1
....

The i remove the usb stick

usb 1-1: USB disconnect, device number 2
FAT-fs (sda1): unable to read boot sector to mark fs as dirty

re-insert
nothing happen anymore.

I am studying into drivers to find a solutions.
Every help is veru appreciated.

Thanks
Regards
Angelo

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to