Hi everyone,
Sorry for the late test but I had other tasks...
I just had some time to look at it and test it.
Le 30/09/2013 09:47, Mylene Josserand a écrit :
> Le 29/09/2013 19:08, Christoph Fritz a écrit :
>> On Sun, 2013-09-29 at 12:19 -0300, Fabio Estevam wrote:
>>> On Sun, Sep 29, 2013 at 11:32 AM, Christoph Fritz
>>> <chf.fritz@xxxxxxxxxxxxxx> wrote:
>>>>> Le 26/09/2013 17:59, Christoph Fritz a écrit :
>>>>>> Their software fix:
>>>>>> "As first attemp at fixing this issue, one may try to switch LINK to
>>>>>> ULPI mode before configuring MUX and pads for USB operation. Fear is
>>>>>> that this could cause unexpected transfer from PHY to LINK, somehow
>>>>>> preventing proper initialization"
>>>>>>
>>>>>> I'll try that here with the smsc3340-phy.
>>>>
>>>> What a mess, it is also important in what order the muxing of USB-Pins
>>>> is done beside the fact that some USBOTG pins had a GPIO_OUT configured
>>>> wrongly. Don't ask how I hit this, but with that and the info from above
>>>> finally both smsc3340 phys on OTG and USBH2 get detected: pure
>>>
>>> Can you show a patch or code so that others could fix this problem as well?
>>
>> Sure, attached to this mail are 4 of my work-in-progress patches, two
>> for barebox and two for the kernel. Consider them RFC. The ULPI-mode
>> switching before muxing is already part of barebox.
>>
>> Thanks
>> -- Christoph
>>
>
>
> Thank you very much, Christoph !
>
>
> I really like having good news like this to start the working week :D
>
>
> I will try to test it this week !
> I hope it will work for me too :)
>
Unfortunately, I don't know if I missed any configurations but the SMSC
3340 is still not working in my case.. :(
I test it with a 2.6.32 kernel. The phy seems to be detected (same thing
before the "patches") but when I plug an USB-key, no reaction in the kernel.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.2: initializing i.MX USB Controller
navocap_cedalion_h2_gpioinit done
mxc-ehci mxc-ehci.2: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.2: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.2: irq 55, io mem 0x10024400
mxc-ehci mxc-ehci.2: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mxc-ehci mxc-ehci.0: initializing i.MX USB Controller
navocap_cedalion_otg_gpioinit done
mxc-ehci mxc-ehci.0: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.0: new USB bus registered, assigned bus number 2
mxc-ehci mxc-ehci.0: irq 56, io mem 0x10024000
mxc-ehci mxc-ehci.0: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
I test it with a 8.2 kernel too and I have the same previous error
"timeout polling" :
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-mxc: Freescale On-Chip EHCI Host driver
mxc-ehci mxc-ehci.0: initializing i.MX USB Controller
timeout polling for ULPI device
mxc-ehci mxc-ehci.0: unable to init transceiver, probably missing
mxc-ehci mxc-ehci.2: initializing i.MX USB Controller
timeout polling for ULPI device
mxc-ehci mxc-ehci.2: unable to init transceiver, probably missing
Initializing USB Mass Storage driver...
Christoph, you are using a 3.4 kernel, is not it ?
I will continue to search but I have no experience on USB (and I am
"learning" with it how works BSP too) so any help would be very appreciated.
If I make any progress, I will post it on this mail-list, of course !
Best regards,
--
Mylène JOSSERAND
��.n��������+%������w��{.n�����{���)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
