public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: ext Ajay Kumar Gupta <ajay.gupta@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"david-b@pacbell.net" <david-b@pacbell.net>
Subject: Re: [PATCH 7/9] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB
Date: Thu, 6 Aug 2009 16:13:37 +0300	[thread overview]
Message-ID: <20090806131336.GP2358@atomide.com> (raw)
In-Reply-To: <20090806130715.GA2874@nokia.com>

* Felipe Balbi <felipe.balbi@nokia.com> [090806 16:06]:
> On Thu, Aug 06, 2009 at 02:07:38PM +0200, ext Ajay Kumar Gupta wrote:
> > OMAP3 HSUSB ports can be individually programmed in PHY or TLL
> > mode in ES3.0 onwards whereas this is not supported in ES2.1
> > and earlier versions.
> > 
> > CHIP_GE_OMAP3430ES3 is added to program this behavior at runtime.
> > 
> > Also updated the existing macros to use the priviously defined
> > *_GE_* logic instead of repeating the same logic again.
> > 
> > Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
> > ---
> >  arch/arm/plat-omap/include/mach/cpu.h |    7 ++++---
> >  1 files changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/arch/arm/plat-omap/include/mach/cpu.h b/arch/arm/plat-omap/include/mach/cpu.h
> > index 285eaa3..5848717 100644
> > --- a/arch/arm/plat-omap/include/mach/cpu.h
> > +++ b/arch/arm/plat-omap/include/mach/cpu.h
> > @@ -428,10 +428,11 @@ IS_OMAP_TYPE(3430, 0x3430)
> >   * chips at ES2 and beyond, but not, for example, any OMAP lines after
> >   * OMAP3.
> >   */
> > -#define CHIP_GE_OMAP3430ES2		(CHIP_IS_OMAP3430ES2 | \
> > -					 CHIP_IS_OMAP3430ES3_0 | \
> > -					 CHIP_IS_OMAP3430ES3_1)
> >  #define CHIP_GE_OMAP3430ES3_1		(CHIP_IS_OMAP3430ES3_1)
> > +#define CHIP_GE_OMAP3430ES3		(CHIP_IS_OMAP3430ES3_0 | \
> > +					 CHIP_GE_OMAP3430ES3_1)
> > +#define CHIP_GE_OMAP3430ES2		(CHIP_IS_OMAP3430ES2 | \
> > +					 CHIP_GE_OMAP3430ES3)
> 
> Tony, what about this one ? Do you agree with it ? I need this in order
> to get a buildable driver merged through linux-usb. The usb-ehci.c stuff
> I can postpone to be sent later but without this, ehci-omap.c won't
> build.
> 
> any input is appreciated.

Yeh looks OK to me.

Tony

  reply	other threads:[~2009-08-06 13:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 12:07 [PATCH 1/9] ehci: fix ehci pin mux init Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 2/9] ehci: adding mux pin for EHCI phy reset line Ajay Kumar Gupta
2009-08-06 12:07   ` [PATCH 3/9] ehci: correct EHCI init parameters on OMAP3EVM Ajay Kumar Gupta
2009-08-06 12:07     ` [PATCH 4/9] ehci: fix phy_reset init in ehci probe Ajay Kumar Gupta
2009-08-06 12:07       ` [PATCH 5/9] ehci: increase timeout to fix ehci failure Ajay Kumar Gupta
2009-08-06 12:07         ` [PATCH 6/9] ehci: portwise configurations Ajay Kumar Gupta
2009-08-06 12:07           ` [PATCH 7/9] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB Ajay Kumar Gupta
2009-08-06 12:07             ` [PATCH 8/9] ehci: Support for ES3.x Ajay Kumar Gupta
2009-08-06 12:07               ` [PATCH 9/9] ehci: update driver with generic change Ajay Kumar Gupta
2009-08-06 13:07             ` [PATCH 7/9] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB Felipe Balbi
2009-08-06 13:13               ` Tony Lindgren [this message]
2009-09-22  1:10         ` [PATCH 5/9] ehci: increase timeout to fix ehci failure Tony Lindgren
2009-09-22 13:10           ` Gupta, Ajay Kumar
2009-09-22 17:10             ` Tony Lindgren
2009-09-22  1:02       ` [PATCH 4/9] ehci: fix phy_reset init in ehci probe Tony Lindgren
2009-08-06 12:43     ` [PATCH 3/9] ehci: correct EHCI init parameters on OMAP3EVM Tony Lindgren
2009-08-07  9:06       ` Gupta, Ajay Kumar
2009-09-22  0:59     ` Tony Lindgren
2009-09-22  0:55   ` [PATCH 2/9] ehci: adding mux pin for EHCI phy reset line Tony Lindgren
2009-08-06 12:40 ` [PATCH 1/9] ehci: fix ehci pin mux init Tony Lindgren
2009-08-06 13:45   ` Gupta, Ajay Kumar
2009-08-06 14:02     ` Gadiyar, Anand
2009-08-06 14:31       ` Gupta, Ajay Kumar

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=20090806131336.GP2358@atomide.com \
    --to=tony@atomide.com \
    --cc=ajay.gupta@ti.com \
    --cc=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.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