[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMbhsRT-ZTh7WQ1E0NUjX8FOMGAvx5zNnB-VYD=j8sWhM-9j+A@mail.gmail.com>
Date: Mon, 20 Feb 2012 15:13:10 -0800
From: Colin Cross <ccross@...roid.com>
To: Peter De Schrijver <pdeschrijver@...dia.com>
Cc: Olof Johansson <olof@...om.net>,
Stephen Warren <swarren@...dia.com>,
Russell King <linux@....linux.org.uk>,
Gary King <gking@...dia.com>, Arnd Bergmann <arnd@...db.de>,
linux-tegra@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 02/10] ARM: tegra: export Tegra chipid
On Thu, Feb 9, 2012 at 3:47 PM, Peter De Schrijver
<pdeschrijver@...dia.com> wrote:
> The powergating and reset handling code needs to differentiate between Tegra
> variants. Therefore we export the chipid here.
>
> Signed-off-by: Peter De Schrijver <pdeschrijver@...dia.com>
> ---
> arch/arm/mach-tegra/fuse.c | 2 +-
> arch/arm/mach-tegra/fuse.h | 1 +
> 2 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-tegra/fuse.c b/arch/arm/mach-tegra/fuse.c
> index 032a936..3298880 100644
> --- a/arch/arm/mach-tegra/fuse.c
> +++ b/arch/arm/mach-tegra/fuse.c
> @@ -34,7 +34,7 @@
> int tegra_sku_id;
> int tegra_cpu_process_id;
> int tegra_core_process_id;
> -static int tegra_chip_id;
> +int tegra_chip_id;
> enum tegra_revision tegra_revision;
>
> /* The BCT to use at boot is specified by board straps that can be read
> diff --git a/arch/arm/mach-tegra/fuse.h b/arch/arm/mach-tegra/fuse.h
> index c554572..d2107b2 100644
> --- a/arch/arm/mach-tegra/fuse.h
> +++ b/arch/arm/mach-tegra/fuse.h
> @@ -41,6 +41,7 @@ enum tegra_revision {
> extern int tegra_sku_id;
> extern int tegra_cpu_process_id;
> extern int tegra_core_process_id;
> +extern int tegra_chip_id;
> extern enum tegra_revision tegra_revision;
>
> extern int tegra_bct_strapping;
Other platforms use accessors for this (cpu_is_xxx(), although
soc_is_xxx() is probably more appropriate).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists