public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ajay Kumar Gupta <ajay.gupta@ti.com>
Cc: linux-omap@vger.kernel.org, felipe.balbi@nokia.com, david-b@pacbell.net
Subject: Re: [PATCH 2/2] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB
Date: Tue, 22 Sep 2009 10:11:14 -0700	[thread overview]
Message-ID: <20090922171114.GE14890@atomide.com> (raw)
In-Reply-To: <1253625132-15050-2-git-send-email-ajay.gupta@ti.com>

* Ajay Kumar Gupta <ajay.gupta@ti.com> [090922 06:12]:
> 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.

Please use the omap_rev() test instead.

Tony 
 
> Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
> ---
> This is required to compile EHCI driver. EHCI driver patch
> "support for ES3.x" used CHIP_GE_OMAP3430ES2 and so this patch
> is also required.
> 
>  arch/arm/plat-omap/include/mach/cpu.h |    7 +++----
>  1 files changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm/plat-omap/include/mach/cpu.h b/arch/arm/plat-omap/include/mach/cpu.h
> index 7a5f9e8..be6be3b 100644
> --- a/arch/arm/plat-omap/include/mach/cpu.h
> +++ b/arch/arm/plat-omap/include/mach/cpu.h
> @@ -414,10 +414,9 @@ 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_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)
>  
>  
>  int omap_chip_is(struct omap_chip_id oci);
> -- 
> 1.6.2.4
> 

  parent reply	other threads:[~2009-09-22 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 13:12 [PATCH 1/2] omap3evm: fix compilation warning for omap3evm_flash_init Ajay Kumar Gupta
2009-09-22 13:12 ` [PATCH 2/2] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB Ajay Kumar Gupta
2009-09-22 13:12   ` [PATCH 3/4] ehci: fix kernel panic in ehci_probe Ajay Kumar Gupta
2009-09-22 13:12     ` [PATCH 4/4] ehci: update driver with another generic change Ajay Kumar Gupta
2009-09-22 17:06       ` [APPLIED] " Tony Lindgren
2009-09-22 17:06     ` [APPLIED] [PATCH 3/4] ehci: fix kernel panic in ehci_probe Tony Lindgren
2009-09-22 17:11   ` Tony Lindgren [this message]
2009-09-22 13:19 ` [PATCH 1/2] omap3evm: fix compilation warning for omap3evm_flash_init Gupta, Ajay Kumar
2009-09-22 17:05 ` [APPLIED] [PATCH 1/2] omap3evm: fix compilation warning for 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=20090922171114.GE14890@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