From: Tony Lindgren <tony@atomide.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: David Brownell <david-b@pacbell.net>,
linux-omap@vger.kernel.org,
linux-omap-open-source <linux-omap-open-source@linux.omap.com>
Subject: Re: RFC: 3430 USB support
Date: Sun, 16 Dec 2007 17:12:59 -0800 [thread overview]
Message-ID: <20071217011258.GY7388@atomide.com> (raw)
In-Reply-To: <5DF83221BE20114E9C331F665ACBC08075E7BB@dbde01.ent.ti.com>
* Pandita, Vikram <vikram.pandita@ti.com> [071205 22:56]:
>
> Hi Kevin/Tony/David/3430-USB-interested-group
>
> As far as USB on 3430 is concerned, following is the difference between 3430 ES1.0 and 3430ES2.0:
>
> 3430 ES1.0:
> USB Core1: MUSB(old) + ISP1504
> USB Core2: FS-OHCI + FS-OTG + FS-DEV (old - Legacy 2430 way)
>
> 3430 ES 2.0:
> USB Core1 : MUSB(old)+ T2-Transceiver(NEW)
> USB Core2 : EHCI/OHCI block (NEW) <---------- All new replacing old block
>
> USB Core1 MUSB:
> We should be able to get MUSB working for both ES1.0 and ES2.0 as there is no extra programming required for the ULPI transceivers. Only the transceiver is changing from ISP1504 to T2.
> So Kevin we will look into the issue you reported of MUSB not working on ES1.0
>
> USB Core2:
> The tricky part is the USB Core2. It is completely replacing the Full-speed OHCI block on ES2.0
> What we are planning is that for 3430, we will support only the ES2.0 and not complicate things for the Core2. Is that fine?
>
> Also I am not sure how many people are using the ES1.0 version?
Yes, sounds like ES1.0 will be gone soon and only used by few people
before they upgrade to ES2.0 also. So let's just keep the core parts
for ES1.0 working, and not worry about drivers beyond serial and
Ethernet.
Tony
prev parent reply other threads:[~2007-12-17 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 13:07 [PATCH 0/3] ARM: OMAP: Patches adding TWL4030 USB support and MUSB support on 34xx Gadiyar, Anand
2007-12-05 20:09 ` Kevin Hilman
2007-12-06 6:55 ` RFC: 3430 USB support Pandita, Vikram
2007-12-17 1:12 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071217011258.GY7388@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox