public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: Felipe Balbi <felipe.balbi@nokia.com>,
	linux-omap@vger.kernel.org, David Brownell <david-b@pacbell.net>,
	"Syed Mohammed, Khasim" <khasim@ti.com>
Subject: Re: [PATCH 2/2] USB: Generalize usb initialization for omap hw
Date: Thu, 24 Apr 2008 10:12:02 -0700	[thread overview]
Message-ID: <20080424171202.GD16834@atomide.com> (raw)
In-Reply-To: <010C7BAE6783F34D9AC336EE5A01A08805E777E5@dbde01.ent.ti.com>

* Gadiyar, Anand <gadiyar@ti.com> [080424 07:17]:
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org 
> > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Felipe Balbi
> > Sent: Thursday, April 24, 2008 7:16 PM
> > To: linux-omap@vger.kernel.org; David Brownell
> > Cc: Tony Lindgren; Syed Mohammed, Khasim; Felipe Balbi
> > Subject: [PATCH 2/2] USB: Generalize usb initialization for omap hw
> > 
> > Create a generic board-file for initializing usb
> > on omap2430 and omap3 boards.
> > 
> > Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
> > ---
> >  arch/arm/mach-omap2/Makefile                       |    4 +-
> >  arch/arm/mach-omap2/board-2430sdp-usb.c            |   96 
> > --------------------
> >  arch/arm/mach-omap2/board-2430sdp.c                |    3 +-
> >  arch/arm/mach-omap2/board-3430sdp.c                |    3 +-
> >  .../mach-omap2/{board-3430sdp-usb.c => usb-musb.c} |   32 ++++---
> >  include/asm-arm/arch-omap/usb-musb.h               |   35 +++++++
> 
> usb-musb.{c,h}? EHCI/OHCI has nothing to do with mentor.

This is all musb stuff, no? If not, there should be a separate
usb-ehci.c.

Tony


> >  6 files changed, 61 insertions(+), 112 deletions(-)
> >  delete mode 100644 arch/arm/mach-omap2/board-2430sdp-usb.c
> >  rename arch/arm/mach-omap2/{board-3430sdp-usb.c => usb-musb.c} (91%)
> >  create mode 100644 include/asm-arm/arch-omap/usb-musb.h
> > 

  parent reply	other threads:[~2008-04-24 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 13:46 [RFC][PATCH 0/2] musb init generalization Felipe Balbi
2008-04-24 13:46 ` [PATCH 1/2] OMAP: Introduce cpu_class_is_omap3() Felipe Balbi
2008-04-24 13:46   ` [PATCH 2/2] USB: Generalize usb initialization for omap hw Felipe Balbi
2008-04-24 14:13     ` Gadiyar, Anand
2008-04-24 14:18       ` Felipe Balbi
2008-04-24 17:16         ` Tony Lindgren
2008-04-24 18:27           ` Felipe Balbi
2008-04-24 18:29           ` David Brownell
2008-04-24 18:32             ` Felipe Balbi
2008-04-24 19:02               ` David Brownell
2008-04-24 18:51             ` usb generalization Felipe Balbi
2008-04-24 18:51               ` [PATCH] USB: Generalize usb initialization for omap hw Felipe Balbi
2008-04-24 19:07                 ` David Brownell
2008-04-24 20:48                   ` Tony Lindgren
2008-04-24 21:08                     ` Felipe Balbi
2008-04-24 21:31                       ` Tony Lindgren
2008-04-28 10:59                 ` Pandita, Vikram
2008-04-28 11:02                   ` Felipe Balbi
2008-04-24 17:12       ` Tony Lindgren [this message]
2008-04-24 17:10     ` [PATCH 2/2] " Tony Lindgren
2008-04-24 17:06   ` [PATCH 1/2] OMAP: Introduce cpu_class_is_omap3() Tony Lindgren

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=20080424171202.GD16834@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=khasim@ti.com \
    --cc=linux-omap@vger.kernel.org \
    /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