All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] Fixed CPU type check for OMAP3
Date: Wed, 10 Sep 2008 17:29:13 -0700	[thread overview]
Message-ID: <20080911002912.GG21163@atomide.com> (raw)
In-Reply-To: <1220892685-3422-1-git-send-email-tero.kristo@nokia.com>

* Tero Kristo <tero.kristo@nokia.com> [080908 08:01]:
> ES version definitions were incorrect, also GP/EMU/SEC etc. types were not
> detected at all.

I've redone the id.c, the old one was getting messy for omap2. Maybe
try my patch I posted on Tuesday and see how it works for you?

Also one comment below.

> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
> ---
>  arch/arm/mach-omap2/id.c              |    11 +++++++++--
>  arch/arm/plat-omap/include/mach/cpu.h |    2 +-
>  2 files changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
> index a526c0f..290b88c 100644
> --- a/arch/arm/mach-omap2/id.c
> +++ b/arch/arm/mach-omap2/id.c
> @@ -53,6 +53,13 @@ static struct omap_id omap_ids[] __initdata = {
>  	{ .hawkeye = 0xb68a, .dev = 0x0, .type = 0x24300000 },
>  };
>  
> +static const char omap3_revs[][4] = {
> +	"1.0",
> +	"2.0",
> +	"2.1",
> +	"3.0"
> +};
> +
>  static struct omap_chip_id omap_chip;
>  
>  /**
> @@ -224,7 +231,7 @@ void __init omap2_check_revision(void)
>  	 * Note that rev cannot be used directly as ES1.0 uses value 0.
>  	 */
>  	if (hawkeye == 0xb7ae) {
> -		system_rev = 0x34300000 | ((1 + rev) << 12);
> -		pr_info("OMAP%04x ES2.%i\n", system_rev >> 16, rev);
> +		_set_system_rev(0x34300000 | (rev << 12), rev);
> +		pr_info("OMAP%04x ES%s\n", system_rev >> 16, omap3_revs[rev]);
>  		_set_omap_chip();
>  		return;
> diff --git a/arch/arm/plat-omap/include/mach/cpu.h b/arch/arm/plat-omap/include/mach/cpu.h
> index e046418..e170d29 100644
> --- a/arch/arm/plat-omap/include/mach/cpu.h
> +++ b/arch/arm/plat-omap/include/mach/cpu.h
> @@ -357,7 +357,7 @@ IS_OMAP_TYPE(3430, 0x3430)
>  #define OMAP3430_REV_ES1_0	0x34300000
>  #define OMAP3430_REV_ES2_0	0x34301000
>  #define OMAP3430_REV_ES2_1	0x34302000
> -#define OMAP3430_REV_ES2_2	0x34303000
> +#define OMAP3430_REV_ES3_0	0x34303000
>  
>  /*
>   * omap_chip bits

Are you sure ES3.0 gives a three for revision? I believe 2.2 had 3, or
is the revision register broken again?

Tony

  reply	other threads:[~2008-09-11  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 16:51 [PATCH] Fixed CPU type check for OMAP3 Tero Kristo
2008-09-11  0:29 ` Tony Lindgren [this message]
2008-09-11  8:52   ` Tero.Kristo
  -- strict thread matches above, loose matches on Subject: below --
2008-09-08 16:33 Tero Kristo
2008-09-08 14:47 ` Tero.Kristo

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=20080911002912.GG21163@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tero.kristo@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.