q7 IMX6 :: usb slave : no hotplug

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

q7 IMX6 :: usb slave : no hotplug

1,069 Views
oliviergerard
Contributor I

Hi all,

I have a problem using gadget usb on a MSC Q7 IMX6 board, with kernel 3.0.35 (revision 14.03.01 from MSC).

My device is connected to a Windows computer via usb, and everything works well if the usb cable is plugged BEFORE initiating the gadgetfs.

I can then unplug and plug again without problems.

If I plug the usb cable AFTER starting my application on the device I never get interrupts to configure the gadget.

I've searched for a patch, but found nothing.

Is there anything wrong in my understanding of the process, or did I miss a patch?

Here is dmesg:

*** the part I have in bith cases:

[ 1336.172033] gadgetfs: bound to fsl-usb2-udc driver

[ 1336.172039] Suspend udc for OTG auto detect

[ 1336.172058] j=103574 [fsl_otg_set_peripheral] ID pin=1

[ 1336.172061]

[ 1336.172075] USB Gadget resume begins

[ 1336.172081] fsl_udc_resume, Wait for wakeup thread finishes

[ 1336.172088] fsl_udc_resume(): stopped 1  suspended 1

[ 1336.175353] dr_controller_run: udc out low power mode

[ 1336.175360] USB Gadget resume ends

[ 1336.175366] fsl-usb2-udc: bind to driver gadgetfs

*** the following is only reached when the cable is plugged at init:

[ 1336.178409] suspend_irq begins

[ 1336.178416] gadgetfs: suspended from state 2

[ 1336.178427] suspend_irq ends

[ 1336.352873] suspend_irq begins

[ 1336.352880] gadgetfs: suspended from state 2

[ 1336.352890] suspend_irq ends

[ 1337.441513] gadgetfs: connected

[ 1337.445113] gadgetfs: disconnected

[ 1337.550344] gadgetfs: connected

[ 1337.565407] gadgetfs: configuration #1

[ 1337.565779] udc: fsl_ep_enable ep.name=ep1in

[ 1337.565957] udc: fsl_ep_enable ep.name=ep1out

Best regards

Olivier GERARD

Labels (4)
0 Kudos
2 Replies

565 Views
oliviergerard
Contributor I

Up please!

I'm really stuck with that bug, I need to handle usb cable plug after boot

Could someone help me finding what i did wrong?

0 Kudos

565 Views
oliviergerard
Contributor I

Does anyone has an idea for my usb problem?

I've tried the following patches without succes:

usb_memory_issue

0001-ENGR00276652-ARM-mx6-Use-IOMUXC-irq-instead-of-125

0010-ENGR00295714-GPT-Status-register-bits-are-cleared-in

0020-ENGR00300417-MX6SL-Add-100M-and-24M-MMDC-parameters-

0021-ENGR00267929-MX6SL-Add-DDR3-support-for-MX6SL

0034-ENGR00316182-imx6x-Fix-bugs-in-clock-and-cpufreq-cod

0035-ENGR00316180-iMX6x-Support-IRAM-page-table-when-DDR-

0037-ENGR00320182-iMX6DQ-iMX6DL-Fix-bug-in-DLL-off-mode-c

0063-ENGR00331050-imx6qdl-Fix-the-workaround-for-ERR00577

0068-ENGR00331611-imx6x-Set-SCU-CPU-Power-status-register

0069-ENGR00327364-imx6x-Ensure-that-the-bandgap-self-bias

0070-ENGR00334447-imx6qdl-Fix-random-failures-caused-by-d

0071-MLK-9663-imx6x-Fix-the-DDR-self-refresh-entry-proced

0072-MLK-9664-imx6x-Remove-unused-commented-code

0075-MLK-9685-ARM-imx6x-Ensure-that-the-kernel-can-boot-w

0076-MLK-9698-ARM-imx6x-Fix-build-break-when-CONFIG_SMP-i

Thanks

Olivier

0 Kudos