USB support on i.MX27

USB support on i.MX27

[Alan Carvalho de Assis]

Hi Javier,

I am trying to add USB support to i.MX27 on mainline linux kernel, I
am following your modifications as in this post:

"Re: Comment to "[PATCH 7/8] Add EHCI support for MX27 and MX31 based boards"

I can't find xcvr.h and isp1504_xcvr.h then I copied fsl_xcvr.h from
FSL kernel to mainline:

alan at metropolis:~/ltib-patches/ltib/rpm/BUILD/linux$ cp
include/linux/usb/fsl_xcvr.h
~/linux/pengutronix/linux-2.6/include/linux/usb/xcvr.h

But I can't to figure out where to find isp1504_xcvr.h.

Could you please help me to get USB working on iMX27ADS?

Best Regards,

Alan

USB support on i.MX27

[Daniel Mack]

On Tue, Nov 24, 2009 at 09:43:41AM -0200, Alan Carvalho de Assis wrote:
> I am trying to add USB support to i.MX27 on mainline linux kernel, I
> am following your modifications as in this post:
> 
> "Re: Comment to "[PATCH 7/8] Add EHCI support for MX27 and MX31 based boards"
> 
> I can't find xcvr.h and isp1504_xcvr.h then I copied fsl_xcvr.h from
> FSL kernel to mainline:
> 
> alan at metropolis:~/ltib-patches/ltib/rpm/BUILD/linux$ cp
> include/linux/usb/fsl_xcvr.h
> ~/linux/pengutronix/linux-2.6/include/linux/usb/xcvr.h
> 
> But I can't to figure out where to find isp1504_xcvr.h.

There is nothing special about the ISP1504. On the register level, it is
compliant to generic ULPI transceivers, and hence the driver in mainline
was named accordingly. There is nothing you need to add from the BSPs
anymore, everything is on its way to mainline already.

> Could you please help me to get USB working on iMX27ADS?

There are a number of boards that implement USB support already for MX3,
and they're all in Sascha's tree. Most of them have been added just
recently, so make sure you're looking at the newest source. As mentioned
above, for ISP1504, you just need create a generic ULPI transceiver.

The only thing that is missing is code that maps the .flags and maybe
.portsc settings from the mxc_usbh_platform_data struct to the
appropriate registers on MX27. And of course, your board support will
need some IOMUX settings.

Daniel

USB support on i.MX27

[Alan Carvalho de Assis]

Hi Daniel,

On 11/24/09, Daniel Mack <daniel@caiaq.de> wrote:
> On Tue, Nov 24, 2009 at 09:43:41AM -0200, Alan Carvalho de Assis wrote:
>> I am trying to add USB support to i.MX27 on mainline linux kernel, I
>> am following your modifications as in this post:
>>
>> "Re: Comment to "[PATCH 7/8] Add EHCI support for MX27 and MX31 based
>> boards"
>>
>> I can't find xcvr.h and isp1504_xcvr.h then I copied fsl_xcvr.h from
>> FSL kernel to mainline:
>>
>> alan at metropolis:~/ltib-patches/ltib/rpm/BUILD/linux$ cp
>> include/linux/usb/fsl_xcvr.h
>> ~/linux/pengutronix/linux-2.6/include/linux/usb/xcvr.h
>>
>> But I can't to figure out where to find isp1504_xcvr.h.
>
> There is nothing special about the ISP1504. On the register level, it is
> compliant to generic ULPI transceivers, and hence the driver in mainline
> was named accordingly. There is nothing you need to add from the BSPs
> anymore, everything is on its way to mainline already.
>

Hmm, then don't need I to add ISP1504 driver from FSL kernel? Great!

>> Could you please help me to get USB working on iMX27ADS?
>
> There are a number of boards that implement USB support already for MX3,
> and they're all in Sascha's tree. Most of them have been added just
> recently, so make sure you're looking at the newest source. As mentioned
> above, for ISP1504, you just need create a generic ULPI transceiver.
>

I am using mxc-master updated but there is nothing related to usb or
otg on mx31lilly.c. Fortunately I figure out mx31moboard.c has it. I
will base on it for now.

> The only thing that is missing is code that maps the .flags and maybe
> .portsc settings from the mxc_usbh_platform_data struct to the
> appropriate registers on MX27. And of course, your board support will
> need some IOMUX settings.
>

Yes, to configure external pins, but I will base on old FSL kernel to
get it working.

Thank you very much again for your help and patience.

Best Regards,

Alan

USB support on i.MX27

[Daniel Mack]

On Tue, Nov 24, 2009 at 10:31:12AM -0200, Alan Carvalho de Assis wrote:
> On 11/24/09, Daniel Mack <daniel@caiaq.de> wrote:
> > On Tue, Nov 24, 2009 at 09:43:41AM -0200, Alan Carvalho de Assis wrote:
> >> I am trying to add USB support to i.MX27 on mainline linux kernel, I
> >> am following your modifications as in this post:
> >>
> >> "Re: Comment to "[PATCH 7/8] Add EHCI support for MX27 and MX31 based
> >> boards"
> >>
> >> I can't find xcvr.h and isp1504_xcvr.h then I copied fsl_xcvr.h from
> >> FSL kernel to mainline:
> >>
> >> alan at metropolis:~/ltib-patches/ltib/rpm/BUILD/linux$ cp
> >> include/linux/usb/fsl_xcvr.h
> >> ~/linux/pengutronix/linux-2.6/include/linux/usb/xcvr.h
> >>
> >> But I can't to figure out where to find isp1504_xcvr.h.
> >
> > There is nothing special about the ISP1504. On the register level, it is
> > compliant to generic ULPI transceivers, and hence the driver in mainline
> > was named accordingly. There is nothing you need to add from the BSPs
> > anymore, everything is on its way to mainline already.
> >
> 
> Hmm, then don't need I to add ISP1504 driver from FSL kernel? Great!

Correct.

> > There are a number of boards that implement USB support already for MX3,
> > and they're all in Sascha's tree. Most of them have been added just
> > recently, so make sure you're looking at the newest source. As mentioned
> > above, for ISP1504, you just need create a generic ULPI transceiver.
> >
> 
> I am using mxc-master updated but there is nothing related to usb or
> otg on mx31lilly.c. Fortunately I figure out mx31moboard.c has it. I
> will base on it for now.

The support is in mx31lilly-db.c which is the _board_ specific code.
People might decide to not have USB on their custom boards, and so this
functions are not enabled from the module code (mx31lilly.c).

> > The only thing that is missing is code that maps the .flags and maybe
> > .portsc settings from the mxc_usbh_platform_data struct to the
> > appropriate registers on MX27. And of course, your board support will
> > need some IOMUX settings.
> >
> 
> Yes, to configure external pins, but I will base on old FSL kernel to
> get it working.

Mixing those versions is not recommended. Try using a kernel based on
mxc-master, apply the pending USB patches manually and modify the EHCI
driver so it works for MX27. A patch that diffs between your version and
the latest USB patches would be appreciated.

If that works, a second patch to add USB to MX27ADS would be the next
step.

Daniel

USB support on i.MX27

[javier Martin]

2009/11/24 Alan Carvalho de Assis <acassis@gmail.com>

> Hi Javier,
>
> I am trying to add USB support to i.MX27 on mainline linux kernel, I
> am following your modifications as in this post:
>
> "Re: Comment to "[PATCH 7/8] Add EHCI support for MX27 and MX31 based
> boards"
>
> I can't find xcvr.h and isp1504_xcvr.h then I copied fsl_xcvr.h from
> FSL kernel to mainline:
>
> alan at metropolis:~/ltib-patches/ltib/rpm/BUILD/linux$ cp
> include/linux/usb/fsl_xcvr.h
> ~/linux/pengutronix/linux-2.6/include/linux/usb/xcvr.h
>
> But I can't to figure out where to find isp1504_xcvr.h.
>
> Could you please help me to get USB working on iMX27ADS?
>

Hum, normally the only thing you must be careful with is about enabling
isp1504 transceiver through a GPIO.
Also note that tests were issued with an early version of Daniel Mack's
patches which AFAIK have been slightly modified since then, specially the
part regarding to generic xcvr framework.


-- 
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091125/361b1e6a/attachment-0001.htm>

USB support on i.MX27

[Daniel Mack]

On Wed, Nov 25, 2009 at 07:52:08AM +0100, javier Martin wrote:
> 2009/11/24 Alan Carvalho de Assis <acassis@gmail.com>
> 
> > Hi Javier,
> >
> > I am trying to add USB support to i.MX27 on mainline linux kernel, I
> > am following your modifications as in this post:
> >
> > "Re: Comment to "[PATCH 7/8] Add EHCI support for MX27 and MX31 based
> > boards"
> >
> > I can't find xcvr.h and isp1504_xcvr.h then I copied fsl_xcvr.h from
> > FSL kernel to mainline:
> >
> > alan at metropolis:~/ltib-patches/ltib/rpm/BUILD/linux$ cp
> > include/linux/usb/fsl_xcvr.h
> > ~/linux/pengutronix/linux-2.6/include/linux/usb/xcvr.h
> >
> > But I can't to figure out where to find isp1504_xcvr.h.
> >
> > Could you please help me to get USB working on iMX27ADS?
> >
> 
> Hum, normally the only thing you must be careful with is about enabling
> isp1504 transceiver through a GPIO.
> Also note that tests were issued with an early version of Daniel Mack's
> patches which AFAIK have been slightly modified since then, specially the
> part regarding to generic xcvr framework.

As I pointed out, the ISP1504 driver turned into a generic ULPI
transceiver driver eventually. And the code got some cleanup, but apart
from that, things are still like they used to be.

Daniel

USB support on i.MX27

[Alan Carvalho de Assis]

Hi Daniel,

On 11/27/09, Daniel Mack <daniel@caiaq.de> wrote:
>
> As I pointed out, the ISP1504 driver turned into a generic ULPI
> transceiver driver eventually. And the code got some cleanup, but apart
> from that, things are still like they used to be.
>

USB Host1 worked fine, but USB Host2 (connected to ISP1504) is crashing:

FEC Ethernet Driver
fec: PHY @ 0x3, ID 0x0007c0f1 -- LAN8710
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.1: initializing i.MX USB Controller
mxc-ehci mxc-ehci.1: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.1: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.1: irq 54, io mem 0x10024200
mxc-ehci mxc-ehci.1: 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.2: initializing i.MX USB Controller
timeout polling for ULPI device
timeout polling for ULPI device
timeout polling for ULPI device
timeout polling for ULPI device
ULPI transceiver vendor/product ID 0xffffff92/0xffffff92
ULPI ID does not match any known transceiver.
mxc-ehci mxc-ehci.2: unable to init transceiver
mxc-ehci mxc-ehci.2: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.2: new USB bus registered, assigned bus number 2
Unhandled fault: external abort on non-linefetch (0x808) at 0xc8896584
Internal error: : 808 [#1] PREEMPT
last sysfs file:
Modules linked in:
CPU: 0    Not tainted  (2.6.32-rc6-g415c7d2-dirty #3)
PC is at ehci_hub_control+0x87c/0x8b4
LR is at 0x4
pc : [<c020f49c>]    lr : [<00000004>]    psr: 00000093
sp : c781fe50  ip : 00000001  fp : 00000000
r10: c8896584  r9 : 00000000  r8 : 60000013
r7 : c78bc8c8  r6 : 00000001  r5 : 00000000  r4 : c781e000
r3 : 80000000  r2 : 00000007  r1 : 80000000  r0 : 00000044
Flags: nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: 0005317f  Table: a0004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc781e270)
Stack: (0xc781fe50 to 0xc7820000)
fe40:                                     00000000 c78bd400 c792f240 00000037
fe60: 00000000 c78bc8c8 c78bc800 c78bc8c8 00000000 00000000 00000000 c78bc800
fe80: c792f240 00000037 00000000 c0211ddc 00000000 00000000 00000002 00000000
fea0: c78bc800 000000a0 c78bd400 c01fefac c792f240 c038d8a0 00000000 c0047e48
fec0: c034a6a4 ffffffff 00000000 c038b2b0 c038b2a8 c78bc800 c038d8a0 c0212ce4
fee0: 00000000 00000000 00000000 00000037 c781ff1c c038b2b0 c03a25ac c03a25ac
ff00: c03dd978 c79339e0 00000000 c03a0260 00000000 c01d2020 c03a25ac c01d0dd4
ff20: c7827de8 c038b2b0 c03a25ac c038b2e4 c01d0ecc c01d0f50 00000000 c781ff48
ff40: c03a25ac c01d0078 c78034d8 c7867d10 c001ead0 c01d0800 c001ead0 c03a25ac
ff60: c0017f08 c01d0898 c0322a08 c02b7b78 c03de5ac c001ead0 c03a25ac c0017f08
ff80: 00000000 00000001 c03aaaec c01d12f0 c03de5ac c001ead0 c781e000 c0017f08
ffa0: 00000000 c0017f74 c001ea64 c002236c c0021950 3532e80c 00000035 00000000
ffc0: 00000000 00000110 c001ea64 c001ead0 c001e80c 00000000 00000000 00000000
ffe0: 00000000 c000875c 00000000 00000000 00000000 c0023a44 fffffeff ffffffff
[<c020f49c>] (ehci_hub_control+0x87c/0x8b4) from [<c0211ddc>] (ehci_mxc_setup+0)
[<c0211ddc>] (ehci_mxc_setup+0x308/0x36c) from [<c01fefac>] (usb_add_hcd+0x1c4/)
[<c01fefac>] (usb_add_hcd+0x1c4/0x5b0) from [<c0212ce4>] (ehci_mxc_drv_probe+0x)
[<c0212ce4>] (ehci_mxc_drv_probe+0x23c/0x418) from [<c01d2020>] (platform_drv_p)
[<c01d2020>] (platform_drv_probe+0x1c/0x24) from [<c01d0dd4>] (driver_probe_dev)
[<c01d0dd4>] (driver_probe_device+0x88/0x180) from [<c01d0f50>] (__driver_attac)
[<c01d0f50>] (__driver_attach+0x84/0x88) from [<c01d0078>] (bus_for_each_dev+0x)
[<c01d0078>] (bus_for_each_dev+0x54/0x80) from [<c01d0898>] (bus_add_driver+0xb)
[<c01d0898>] (bus_add_driver+0xb8/0x2dc) from [<c01d12f0>] (driver_register+0x5)
[<c01d12f0>] (driver_register+0x58/0x144) from [<c0017f74>] (ehci_hcd_init+0x6c)
[<c0017f74>] (ehci_hcd_init+0x6c/0xc4) from [<c002236c>] (do_one_initcall+0x2c/)
[<c002236c>] (do_one_initcall+0x2c/0x1a8) from [<c000875c>] (kernel_init+0x9c/0)
[<c000875c>] (kernel_init+0x9c/0x108) from [<c0023a44>] (kernel_thread_exit+0x0)
Code: e597300c e3130010 13c13a01 13c3302a (158a3000)
---[ end trace 76e229204033b0ca ]---
note: swapper[1] exited with preempt_count 2
Kernel panic - not syncing: Attempted to kill init!

Using Freescale kernel 2.6.22 is works fine.

Best Regards,

Alan

USB support on i.MX27

[Alan Carvalho de Assis]

Daniel,

On 11/30/09, Alan Carvalho de Assis <acassis@gmail.com> wrote:
>
> USB Host1 worked fine, but USB Host2 (connected to ISP1504) is crashing:
>
> FEC Ethernet Driver
> fec: PHY @ 0x3, ID 0x0007c0f1 -- LAN8710
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> mxc-ehci mxc-ehci.1: initializing i.MX USB Controller
> mxc-ehci mxc-ehci.1: Freescale On-Chip EHCI Host Controller
> mxc-ehci mxc-ehci.1: new USB bus registered, assigned bus number 1
> mxc-ehci mxc-ehci.1: irq 54, io mem 0x10024200
> mxc-ehci mxc-ehci.1: 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.2: initializing i.MX USB Controller
> timeout polling for ULPI device
> timeout polling for ULPI device
> timeout polling for ULPI device
> timeout polling for ULPI device
> ULPI transceiver vendor/product ID 0xffffff92/0xffffff92
> ULPI ID does not match any known transceiver.
> mxc-ehci mxc-ehci.2: unable to init transceiver
> mxc-ehci mxc-ehci.2: Freescale On-Chip EHCI Host Controller
> mxc-ehci mxc-ehci.2: new USB bus registered, assigned bus number 2
> Unhandled fault: external abort on non-linefetch (0x808) at 0xc8896584
> Internal error: : 808 [#1] PREEMPT
>...

I forgot to comment, I am configuring usbh2's portsc as on mx31lite:

.portsc = MXC_EHCI_MODE_ULPI | MXC_EHCI_UTMI_8BIT,

I defined and configured usbh2 pins:
        /* USBH2 */
        PA0_PF_USBH2_CLK,
        PA1_PF_USBH2_DIR,
        PA3_PF_USBH2_NXT,
        PA4_PF_USBH2_STP,
        PD22_AF_USBH2_DATA0,
        PD24_AF_USBH2_DATA1,
        PD23_AF_USBH2_DATA2,
        PD20_AF_USBH2_DATA3,
        PD19_AF_USBH2_DATA4,
        PD26_AF_USBH2_DATA5,
        PD21_AF_USBH2_DATA6,
        PA2_PF_USBH2_DATA7,
        PA24_AIN_SLDCD1_D0, /* EN_B */
        PA26_PF_PS, /* RES_B */

What you think could be this issue?

Thank you very much,

Alan

USB support on i.MX27

[Alan Carvalho de Assis]

Hi Daniel,

On 11/30/09, Alan Carvalho de Assis <acassis@gmail.com> wrote:
> I forgot to comment, I am configuring usbh2's portsc as on mx31lite:
>
> .portsc = MXC_EHCI_MODE_ULPI | MXC_EHCI_UTMI_8BIT,
>
> I defined and configured usbh2 pins:
>         /* USBH2 */
>         PA0_PF_USBH2_CLK,
>         PA1_PF_USBH2_DIR,
>         PA3_PF_USBH2_NXT,
>         PA4_PF_USBH2_STP,
>         PD22_AF_USBH2_DATA0,
>         PD24_AF_USBH2_DATA1,
>         PD23_AF_USBH2_DATA2,
>         PD20_AF_USBH2_DATA3,
>         PD19_AF_USBH2_DATA4,
>         PD26_AF_USBH2_DATA5,
>         PD21_AF_USBH2_DATA6,
>         PA2_PF_USBH2_DATA7,
>         PA24_AIN_SLDCD1_D0, /* EN_B */
>         PA26_PF_PS, /* RES_B */
>
> What you think could be this issue?
>

More some debug and everything worked fine:

FEC Ethernet Driver
fec: PHY @ 0x0, ID 0x0007c0f1 -- LAN8710
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.1: initializing i.MX USB Controller
mxc-ehci mxc-ehci.1: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.1: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.1: irq 54, io mem 0x10024200
mxc-ehci mxc-ehci.1: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.32-rc6-g415c7d2-dirty ehci_hcd
usb usb1: SerialNumber: mxc-ehci.1
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.2: initializing i.MX USB Controller
ULPI transceiver vendor/product ID 0x04cc/0x1504
mxc-ehci mxc-ehci.2: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.2: new USB bus registered, assigned bus number 2
mxc-ehci mxc-ehci.2: irq 55, io mem 0x10024400
mxc-ehci mxc-ehci.2: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Freescale On-Chip EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.32-rc6-g415c7d2-dirty ehci_hcd
usb usb2: SerialNumber: mxc-ehci.2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
hub 1-0:1.0: over-current change on port 1

Best Regards,

Alan

USB support on i.MX27

[Daniel Mack]

On Tue, Dec 01, 2009 at 12:16:03PM -0200, Alan Carvalho de Assis wrote:
> On 11/30/09, Alan Carvalho de Assis <acassis@gmail.com> wrote:
> > I forgot to comment, I am configuring usbh2's portsc as on mx31lite:
> >
> > .portsc = MXC_EHCI_MODE_ULPI | MXC_EHCI_UTMI_8BIT,
> >
> > I defined and configured usbh2 pins:
> >         /* USBH2 */
> >         PA0_PF_USBH2_CLK,
> >         PA1_PF_USBH2_DIR,
> >         PA3_PF_USBH2_NXT,
> >         PA4_PF_USBH2_STP,
> >         PD22_AF_USBH2_DATA0,
> >         PD24_AF_USBH2_DATA1,
> >         PD23_AF_USBH2_DATA2,
> >         PD20_AF_USBH2_DATA3,
> >         PD19_AF_USBH2_DATA4,
> >         PD26_AF_USBH2_DATA5,
> >         PD21_AF_USBH2_DATA6,
> >         PA2_PF_USBH2_DATA7,
> >         PA24_AIN_SLDCD1_D0, /* EN_B */
> >         PA26_PF_PS, /* RES_B */
> >
> > What you think could be this issue?
> >
> 
> More some debug and everything worked fine:

Hmm, I don't follow. You added some debug output and it started working,
is that what you say? Do we possibly need memory barriers somewhere?

Can you post a patch with your changes, please?

Daniel

USB support on i.MX27

[Alan Carvalho de Assis]

Hi Daniel,

On 12/1/09, Daniel Mack <daniel@caiaq.de> wrote:
>
> Hmm, I don't follow. You added some debug output and it started working,
> is that what you say? Do we possibly need memory barriers somewhere?
>

Basically it, but I will do more tests to isolate the issue.

In fact there is a board where the issue remain, but using old kernel
(2.6.22) both work.

> Can you post a patch with your changes, please?
>

Sure, I will do that as soon as I isolate it.

Best Regards,

Alan

USB support on i.MX27

[Valentin Longchamp]

Hi Daniel and Alan,

Alan Carvalho de Assis wrote:
> Hi Daniel,
> 
> On 12/1/09, Daniel Mack <daniel@caiaq.de> wrote:
>> Hmm, I don't follow. You added some debug output and it started working,
>> is that what you say? Do we possibly need memory barriers somewhere?
>>
> 
> Basically it, but I will do more tests to isolate the issue.
> 
> In fact there is a board where the issue remain, but using old kernel
> (2.6.22) both work.

I am also investigating this issue. The same happens sometimes with my 
USB host with ULPI-ISP1504, but it never happens with the USB slave with 
the exact same hardware ULPI-ISP1504, that's why I have the feeling that 
it's a purely software issue.

I also had the feeling that it was a timing issue (maybe with a clock 
not ready at the right time) and what I read from Alan comforts me with 
this feeling. But I haven't been able to isolate this either.

Best Regards

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp at epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne

USB support on i.MX27

[Eric Bénard]

Hi,

Valentin Longchamp a ?crit :
> Alan Carvalho de Assis wrote:
>> On 12/1/09, Daniel Mack <daniel@caiaq.de> wrote:
>>> Hmm, I don't follow. You added some debug output and it started working,
>>> is that what you say? Do we possibly need memory barriers somewhere?
>>>
>>
>> Basically it, but I will do more tests to isolate the issue.
>>
>> In fact there is a board where the issue remain, but using old kernel
>> (2.6.22) both work.
> 
> I am also investigating this issue. The same happens sometimes with my 
> USB host with ULPI-ISP1504, but it never happens with the USB slave with 
> the exact same hardware ULPI-ISP1504, that's why I have the feeling that 
> it's a purely software issue.
> 
we once met a similar problem on i.MX27 : in fact, during IOMUX 
configuration, some pins were togled on the ULPI and the ISP1504 was 
taking this toggles as a command and was taking control of the ULPI bus 
which means the IMX wasn't anymore able to talk to it through ULPI. Just 
reseting the ISP1504 allawed the boot to continue fine.
Maybe your issue is similar to this.

Eric

USB support on i.MX27

[Valentin Longchamp]

Hello all,

Eric B?nard wrote:
> Valentin Longchamp a ?crit :
>> Alan Carvalho de Assis wrote:
>>> On 12/1/09, Daniel Mack <daniel@caiaq.de> wrote:
>>>> Hmm, I don't follow. You added some debug output and it started 
>>>> working,
>>>> is that what you say? Do we possibly need memory barriers somewhere?
>>>>
>>>
>>> Basically it, but I will do more tests to isolate the issue.
>>>
>>> In fact there is a board where the issue remain, but using old kernel
>>> (2.6.22) both work.
>>
>> I am also investigating this issue. The same happens sometimes with my 
>> USB host with ULPI-ISP1504, but it never happens with the USB slave 
>> with the exact same hardware ULPI-ISP1504, that's why I have the 
>> feeling that it's a purely software issue.
>>
> we once met a similar problem on i.MX27 : in fact, during IOMUX 
> configuration, some pins were togled on the ULPI and the ISP1504 was 
> taking this toggles as a command and was taking control of the ULPI bus 
> which means the IMX wasn't anymore able to talk to it through ULPI. Just 
> reseting the ISP1504 allawed the boot to continue fine.
> Maybe your issue is similar to this.
> 

I have found a fix to this issue, and it looks a bit like what Eric just 
described. I will post a patch in the next minutes and it would be nice 
if (at least) Alan and Daniel could test it to see if it fixes the 
problem for them too.

With the patch, I have never noticed a problem during the whole 
afternoon (around 30-35 reboots with ULPI init).

Val