Hi, On Sun, Dec 02, 2012 at 05:33:36PM +0200, Dmitry Lifshitz wrote: > Hi, > > We are running kernel v3.5.7 on am3517 based hardware (CM-T3517 module). > Recently we faced with the following issue: am35x MUSB module fails > when trying to reinsert it. > It fails with the message "musb-hdrc.0: failed to claim resource 1", > see the console clip below: > > root@cm-debian:~# modprobe am35x > musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) > 6Waiting for PHY clock good... > musb-hdrc: ConfigData=0x1e (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, > SoftConn) > musb-hdrc: MHDRC RTL version 1.900 > musb-hdrc: setup fifo_mode 4 > musb-hdrc: 28/31 max ep, 16384/16384 memory > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# modprobe -r am35x > udc musb-hdrc.0: releasing 'musb-hdrc.0' > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# > root@cm-debian:~# modprobe am35x > musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) > musb-hdrc.0: failed to claim resource 1 > musb-am35x musb-am35x: failed to register musb device > musb-am35x: probe of musb-am35x failed with error -16 > root@cm-debian:~# > > The issue still exists even in the resent kernel v3.7.0-rc7. > While searching for the resolution I found the similar issue with the > davinci MUSB module: > > http://comments.gmane.org/gmane.linux.davinci/23781 > > It was found almost a year ago. Does anybody know how it can be > properly resolved? Can you try to figure which resource is getting a conflict ? -- balbi
Attachment:
signature.asc
Description: Digital signature
