Hello,
I am using the fsl_usb2_udc driver on my mx31 system (mx31moboard,
support in the kernel). I mostly use it as g_ehter gadget because we do
not have a real ethernet device on our board. We use ISP1504 Phy
transceivers.
Now I have a systematic problem at kernel boot: as soon as I register
the platform_device and until the fsl_usb2_udc module is loaded, the USB
bus is blocked (this for example means that I cannot use the USB mouse
and keyboard on the computer my board is plugged into). This only
happens when I do a "warm reboot" and I was thinking maybe we do
something wrong in the fsl_usb2_udc driver, especially at
fsl_udc_remove. We could maybe add a call that disables the physical
transceiver, the equivalent to the dr_controller call in fsl_udc_probe.
Of course, I already have a workaround having fsl_usb2_udc built in the
kernel and not as a module: the driver is registered very quickly after
the usb_udc platforme_device and I don't notice the USB bus being
blocked (maybe is it very short but still happens). But I think this
problem should not happend, even with fsl_usb2_udc built as module.
I also wanted to ask the people who use this driver on mx31 (or maybe
another platform, because it is available for other Freescale SoCs) if
they already have noticed this kind of behavior ?
Best Regards
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@xxxxxxx, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
