linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	balbi@ti.com
Subject: Re: [PATCH 0/4] omap legacy full speed usb cleanup for v3.6
Date: Fri, 25 May 2012 10:22:46 +0300	[thread overview]
Message-ID: <20120525072245.GA6206@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205241401070.2572@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [120524 23:05]:
> On Mon, 21 May 2012, Tony Lindgren wrote:
> 
> > This series removes the old legacy fulls speed support for
> > omap2 as it's pretty much only used for omap1 only.
> > 
> > For omap2, only n8x0 seems to have active development, and
> > that has the external high speed tusb chip instead.
> 
> Just FYI, full speed host USB exists on OMAP4.  It's in section 23.13 of 
> the TRM and we have a hwmod for it.  No idea if anyone is actually using 
> it.

Interesting, so it's back on omap4 for some legacy compability reasons
i guess. It's not mentioned for omap3 at all, but maybe it's lurking
around there somewhere too.

Looking at the omap4 TRM, looks like there are two instances of OHCI:
The HS OHCI/EHCI controller, and the legacy FS OHCI only controller.
The legacy one is using separate transceiver pins (usbc1_*) from the
HS OHCI/EHCI controller pins (usbb[12]_*).

As the OHCI registers are standard, I'd assume it would be possible
to make the FS USB instance to work with the mach-omap2/usb-host.c
and drivers/usb/host/ohci-omap3.c driver. So it should still be OK
to remove the code in this series.

I doubt that anybody would want to use the legacy FS OHCI controller
instead of the HS OHCI/EHCI controller though.. If somebody
is actually using the legacy controller at usbc1_* pins, please
respond. 

Regards,

Tony

      reply	other threads:[~2012-05-25  7:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 19:00 [PATCH 0/4] omap legacy full speed usb cleanup for v3.6 Tony Lindgren
2012-05-21 19:01 ` [PATCH 2/4] ARM: OMAP2: Remove legacy USB FS support Tony Lindgren
2012-05-22  7:07   ` Felipe Balbi
     [not found] ` <20120521185323.927.88012.stgit-t/zwCYRDW5/25TI67NSWRg@public.gmane.org>
2012-05-21 19:01   ` [PATCH 1/4] ARM: OMAP3: There is no FS USB controller on omap3 Tony Lindgren
     [not found]     ` <20120521190102.927.86158.stgit-t/zwCYRDW5/25TI67NSWRg@public.gmane.org>
2012-05-22  7:06       ` Felipe Balbi
2012-05-21 19:01   ` [PATCH 3/4] ARM: OMAP: Make FS USB omap1 only Tony Lindgren
     [not found]     ` <20120521190109.927.44462.stgit-t/zwCYRDW5/25TI67NSWRg@public.gmane.org>
2012-05-22  7:08       ` Felipe Balbi
2012-05-22 16:07         ` Tony Lindgren
2012-05-21 19:01 ` [PATCH 4/4] USB: Remove omap2 support from omap_udc.c Tony Lindgren
2012-05-22  7:09   ` Felipe Balbi
2012-05-22 16:06     ` Tony Lindgren
2012-05-24 20:02 ` [PATCH 0/4] omap legacy full speed usb cleanup for v3.6 Paul Walmsley
2012-05-25  7:22   ` 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=20120525072245.GA6206@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).