Hi,
[..]
> > +* We have to override VBUS/ID signals when MUSB is configured into
> the
> > +* host-only mode -- ID pin will float if no cable is connected, so
> the
> > +* controller won't be able to drive VBUS thinking that it's a B-
> device.
> > +* Otherwise, we want to use the O
Hello.
Gupta, Ajay Kumar wrote:
AM35x has musb interface (version 1.8) and uses CPPI41
DMA engine.
It has USB phy built inside the IP itself.
So it's more like DaVinci (earlier CPPI as well as
integrated PHY) than OMAP3...
Yes. Actually they removed original musb controller from OMAP3
a
> > > AM35x has musb interface (version 1.8) and uses CPPI41
> > DMA engine.
> > > It has USB phy built inside the IP itself.
>
> So it's more like DaVinci (earlier CPPI as well as
> integrated PHY) than OMAP3...
Yes. Actually they removed original musb controller from OMAP3
and replaced it with
--- On Fri, 5/28/10, Sergei Shtylyov wrote:
>
> Ajay Kumar Gupta wrote:
>
> > AM35x has musb interface (version 1.8) and uses CPPI41
> DMA engine.
> > It has USB phy built inside the IP itself.
So it's more like DaVinci (earlier CPPI as well as
integrated PHY) than OMAP3...
> > Also added AR
Hello.
Ajay Kumar Gupta wrote:
AM35x has musb interface (version 1.8) and uses CPPI41 DMA engine.
It has USB phy built inside the IP itself.
Also added ARCH_AM35x which is required to differentiate musb ips
between OMAP3x and AM35x. This config would be used to for below
purposes,
-
AM35x has musb interface (version 1.8) and uses CPPI41 DMA engine.
It has USB phy built inside the IP itself.
Also added ARCH_AM35x which is required to differentiate musb ips
between OMAP3x and AM35x. This config would be used to for below
purposes,
- Select am3517.c instead of omap2430.c
AM35x has musb interface (version 1.8) and uses CPPI41 DMA engine.
It supports upto 500mA of power in host mode.
Signed-off-by: Ajay Kumar Gupta
---
Patch created against linus'tree + all musb patches in Greg's queue
and patches available in linux-omap/for-next branch.
arch/arm/mach-omap2/board
