Skip to contentSkip to conversation

USB on OMAP3530

DISCUSSION Rick Bronson 4 participants 4 messages Feb 19, 2009 – Feb 20, 2009

lore
Share & tools
lore
#0 lore raw

Thanks very much for the help.

Quoted 2 lines

so Rick, you need to load a gadget driver for musb to work, g_ether or g_zero are the simplest ones.

But don't I already have the g_zero enabled via:

CONFIG_USB_GADGET_MUSB_HDRC=y

But lets assume that, for the time being, I'm only interested in USB
Host.

I had combed the mailing list looking for ISP1505 support and
happened across this:

Quoted 4 lines

There's one problem here. If this is similar to isp1704, it doesn't have a control interface. And the only way to talk to the transceiver is via ULPI. I have patches that add musb_ulpi_read/write functions using the musb ulpi wrapper.

The ISP1704 is very similar to the ISP1505, neither one has a
control interface (like I2C), only straight ULPI. Does this mean that there is no "out of the box" support for straight ULPI in 2.6.29? If so, what would I need to do to support it?

Rick

#1 lore raw
Quoted 19 lines

Thanks very much for the help.

Quoted 2 lines

so Rick, you need to load a gadget driver for musb to work, g_ether or g_zero are the simplest ones.

But don't I already have the g_zero enabled via:

CONFIG_USB_GADGET_MUSB_HDRC=y

But lets assume that, for the time being, I'm only interested in USB Host.

I had combed the mailing list looking for ISP1505 support and
happened across this:

Quoted 4 lines

There's one problem here. If this is similar to isp1704, it doesn't have a control interface. And the only way to talk to the transceiver is via ULPI. I have patches that add musb_ulpi_read/write functions using the musb ulpi wrapper.

Quoted 8 lines

The ISP1704 is very similar to the ISP1505, neither one has a
control interface (like I2C), only straight ULPI. Does this mean that there is no "out of the box" support for straight ULPI in 2.6.29? If so, what would I need to do to support it?

Rick

The ISP1505 is supposed to be pretty-much plug and play. MUSB should in theory work directly - no configuration required.

The OMAP3 EVM boards also run a similar configuration. Maybe someone with that board can tell you if MUSB in the current kernel works out of the box.

Looking closer at your config options, you have CONFIG_USB_MUSB_OTG which means you need a gadget driver loaded before you can use MUSB. But, you also have CONFIG_USB_ETH=y, which means your gadget driver is also built-in. So you won't need to insmod the module.

#2 lore raw
Quoted 28 lines · Anand
Quoted 19 lines

Thanks very much for the help.

Quoted 2 lines

so Rick, you need to load a gadget driver for musb to work, g_ether or g_zero are the simplest ones.

But don't I already have the g_zero enabled via:

CONFIG_USB_GADGET_MUSB_HDRC=y

But lets assume that, for the time being, I'm only interested in USB Host.

I had combed the mailing list looking for ISP1505 support and
happened across this:

Quoted 4 lines

There's one problem here. If this is similar to isp1704, it doesn't have a control interface. And the only way to talk to the transceiver is via ULPI. I have patches that add musb_ulpi_read/write functions using the musb ulpi wrapper.

Quoted 8 lines

The ISP1704 is very similar to the ISP1505, neither one has a
control interface (like I2C), only straight ULPI. Does this mean that there is no "out of the box" support for straight ULPI in 2.6.29? If so, what would I need to do to support it?

Rick

Quoted 6 lines

The ISP1505 is supposed to be pretty-much plug and play. MUSB should in theory work directly - no configuration required.

The OMAP3 EVM boards also run a similar configuration. Maybe someone with that board can tell you if MUSB in the current kernel works out of the box.

I have a board with isp1704, I only have to talk to it when I wanna e.g. ask it to detect if we have a charger attached to usb port.

Quoted 4 lines

Looking closer at your config options, you have CONFIG_USB_MUSB_OTG which means you need a gadget driver loaded before you can use MUSB. But, you also have CONFIG_USB_ETH=y, which means your gadget driver is also built-in. So you won't need to insmod the module.

Then it should be working. Do you attach micro/mini-A connector to usb port ? What happens in that case ? how about

echo 5 > /sys/modules/musb_hdrc/parameters/musb_debug

Does it give you any messages when you attach cable ? Send us dmesg output with musb_debug set to 5.

Signature · 1 line
balbi
#3 lore raw
In reply to Rick Bronson
Quoted 29 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Rick Bronson
Sent: Thursday, February 19, 2009 8:28 PM
To: Gadiyar, Anand
Cc: [email protected]
Subject: Re: USB on OMAP3530

Thanks very much for the help.

Quoted 2 lines

so Rick, you need to load a gadget driver for musb to work, g_ether or g_zero are the simplest ones.

But don't I already have the g_zero enabled via:

CONFIG_USB_GADGET_MUSB_HDRC=y

But lets assume that, for the time being, I'm only interested in USB
Host.

I had combed the mailing list looking for ISP1505 support and
happened across this:

Quoted 4 lines

There's one problem here. If this is similar to isp1704, it doesn't have a control interface. And the only way to talk to the transceiver is via ULPI. I have patches that add musb_ulpi_read/write functions using the musb ulpi wrapper.

Quoted 4 lines

The ISP1704 is very similar to the ISP1505, neither one has a
control interface (like I2C), only straight ULPI. Does this mean that there is no "out of the box" support for straight ULPI in 2.6.29? If so, what would I need to do to support it?

I am using OMAP35x EVM which has ISP1504 and it works directly. Use omap3_evm_defconfig which has all the required default config for MUSB. Just make sure to insert the gadget module after boot OR use built-in gadget driver.

Regards,
Ajay

Quoted 6 lines

Rick
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html