From: Nick Thompson <nick.thompson@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: make timer variables in gt_t available for all ARM platforms
Date: Thu, 02 Dec 2010 11:54:27 +0000 [thread overview]
Message-ID: <4CF788F3.9000403@ge.com> (raw)
In-Reply-To: <1291205812-5491-1-git-send-email-prafulla@marvell.com>
On 01/12/10 12:16, Prafulla Wadaskar wrote:
> After ARM relocation,
> any code executed directly or indirectly by board_init_f() have
> global (BSS) variables need to be fixed. mostly timer.c needs to
> fix on most of the ARM platforms.
>
> This patch makes timer related variables in gd_t available for
> all ARM implementation
>
> Signed-off-by: Prafulla Wadaskar <prafulla@marvell.com>
> ---
> arch/arm/include/asm/global_data.h | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/include/asm/global_data.h b/arch/arm/include/asm/global_data.h
> index ada3fbb..efb502e 100644
> --- a/arch/arm/include/asm/global_data.h
> +++ b/arch/arm/include/asm/global_data.h
> @@ -55,7 +55,9 @@ typedef struct global_data {
> unsigned long plla_rate_hz;
> unsigned long pllb_rate_hz;
> unsigned long at91_pllb_usb_init;
> - /* "static data" needed by at91's timer.c */
> +#endif
> +#ifdef CONFIG_ARM
> + /* "static data" needed by most of timer.c on ARM platforms */
> unsigned long timer_rate_hz;
> unsigned long tbl;
> unsigned long tbu;
This file is ARM specific. Doesn't this mean CONFIG_ARM is always defined here?
Regards,
Nick.
next prev parent reply other threads:[~2010-12-02 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 12:16 [U-Boot] [PATCH] ARM: make timer variables in gt_t available for all ARM platforms Prafulla Wadaskar
2010-12-02 11:54 ` Nick Thompson [this message]
2010-12-07 12:24 ` Prafulla Wadaskar
2010-12-07 13:10 ` Wolfgang Denk
2010-12-08 23:03 ` Wolfgang Denk
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=4CF788F3.9000403@ge.com \
--to=nick.thompson@ge.com \
--cc=u-boot@lists.denx.de \
/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