From: Tony Lindgren <tony@atomide.com>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Manjunatha GK <manjugk@ti.com>
Subject: Re: [PATCH] OMAP3630: Add ES1.1 and ES1.2 detection
Date: Tue, 3 Aug 2010 10:39:40 +0300 [thread overview]
Message-ID: <20100803073940.GS12293@atomide.com> (raw)
In-Reply-To: <1278717461-5329-1-git-send-email-gadiyar@ti.com>
* Anand Gadiyar <gadiyar@ti.com> [100710 02:11]:
> Add revision detection for ES1.1 and ES1.2. Set default
> revision as ES1.2.
>
> Add CHIP_GE_OMAP3630ES1_1 to detect revisions 1.1 and later.
> This is needed for at least one feature that is broken in
> 3630ES1.0 but exists on older (3430 ES3.1) and newer revisions.
>
> Additionally, update some of the CHIP_GE_* macros to use other
> macros for ease of maintenance.
>
> Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Manjunatha GK <manjugk@ti.com>
> Cc: Tony Lindgren <tony@atomide.com>
> ---
> This is based on Manju's original patch at [1] and my update [2].
> The original patch failed to properly update the CHIP_GE_OMAP3630ES1 macro.
>
> Would be nice to get this queued for the next merge window
>
> [1] https://patchwork.kernel.org/patch/95684/
> [2] https://patchwork.kernel.org/patch/99590/
>
> arch/arm/mach-omap2/id.c | 27 +++++++++++++++++++++++----
> arch/arm/plat-omap/include/plat/cpu.h | 15 +++++++++++----
> 2 files changed, 34 insertions(+), 8 deletions(-)
>
> Index: linux-omap-2.6/arch/arm/mach-omap2/id.c
> ===================================================================
> --- linux-omap-2.6.orig/arch/arm/mach-omap2/id.c
> +++ linux-omap-2.6/arch/arm/mach-omap2/id.c
> @@ -269,11 +269,24 @@ void __init omap3_check_revision(void)
> omap_chip.oc |= CHIP_IS_OMAP3430ES3_1;
> break;
> case 0xb891:
> - /* FALLTHROUGH */
> - default:
> - /* Unknown default to latest silicon rev as default*/
> - omap_revision = OMAP3630_REV_ES1_0;
> + /* Handle 36xx devices */
> omap_chip.oc |= CHIP_IS_OMAP3630ES1;
> +
> + switch(rev) {
> + case 0: /* Take care of early samples */
> + omap_revision = OMAP3630_REV_ES1_0;
> + break;
> + case 1:
> + omap_revision = OMAP3630_REV_ES1_1;
> + omap_chip.oc |= CHIP_IS_OMAP3630ES1_1;
> + break;
> + case 2:
> + /* Fall through */
> + default:
> + /* Use the latest known revision as default */
> + omap_revision = OMAP3630_REV_ES1_2;
> + omap_chip.oc |= CHIP_IS_OMAP3630ES1_2;
> + }
> }
> }
Please don't remove the default handling for unknown hawkeye
registers for omap3. Now you're only handling hawkeye 0xb891.
IMHO, setting unknown hawkeye chips to OMAP3630_REV_ES1_2
should be still best option for future chips.
Regards,
Tony
next prev parent reply other threads:[~2010-08-03 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 10:00 Tony mostly offline for the rest of July Tony Lindgren
2010-07-08 10:00 ` Tony Lindgren
2010-07-08 17:37 ` Gadiyar, Anand
2010-07-08 17:37 ` Gadiyar, Anand
2010-07-09 7:29 ` Tony Lindgren
2010-07-09 7:29 ` Tony Lindgren
2010-07-09 23:17 ` [PATCH] OMAP3630: Add ES1.1 and ES1.2 detection Anand Gadiyar
2010-08-03 7:39 ` Tony Lindgren [this message]
2010-08-03 7:43 ` Gadiyar, Anand
2010-08-03 19:59 ` [PATCH v2] " Anand Gadiyar
2010-08-04 10:30 ` Tony Lindgren
2010-08-04 10:51 ` Tony Lindgren
2010-08-04 10:55 ` Gadiyar, Anand
2010-08-04 11:01 ` Felipe Balbi
2010-08-04 11:06 ` Tony Lindgren
2010-08-04 11:09 ` Felipe Balbi
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=20100803073940.GS12293@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=nm@ti.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.