From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-BOOT][PATCH 2/5] MX53: Add register definitions
Date: Fri, 18 Jun 2010 11:35:02 +0200 [thread overview]
Message-ID: <4C1B3DC6.8090807@denx.de> (raw)
In-Reply-To: <12768745682125-git-send-email-r64343@freescale.com>
Jason Liu wrote:
> The patch add header files to support the Freescale i.MX53
> processor, setting definitions for internal registers.
>
> Signed-off-by:Jason Liu <r64343@freescale.com>
> ---
> arch/arm/include/asm/arch-mx53/asm-offsets.h | 52 ++
> arch/arm/include/asm/arch-mx53/crm_regs.h | 708 ++++++++++++++++++++++++++
> arch/arm/include/asm/arch-mx53/imx-regs.h | 193 +++++++
> 3 files changed, 953 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/include/asm/arch-mx53/asm-offsets.h b/arch/arm/include/asm/arch-mx53/asm-offsets.h
The only difference with arch-mx51/asm-offset.h is:
< #define CLKCTL_CCGR7 0x84
< #define CLKCTL_CMEOR 0x88
---
> #define CLKCTL_CMEOR 0x84
We do not need to introduce a newer file.
> diff --git a/arch/arm/include/asm/arch-mx53/crm_regs.h b/arch/arm/include/asm/arch-mx53/crm_regs.h
> new file mode 100644
> index 0000000..cd39055
> +/* Define the bits in register CCR */
> +#define MXC_CCM_CCR_COSC_EN (0x1 << 12)
In mx53 some more bits are defined. However, I have not found grepping
the code where they are defined. I do not think we have to introduce
constants we do not need.
And this file must be merged with arch-mx51/crm_regs.h
> diff --git a/arch/arm/include/asm/arch-mx53/imx-regs.h b/arch/arm/include/asm/arch-mx53/imx-regs.h
> new file mode 100644
> index 0000000..104fae4
> +#define IRAM_BASE_ADDR 0xF8000000 /* internal ram */
This file must be merged with the mx51 counterparts, splitting values
where is needed, as in this case. Something like:
#if defined(CONFIG_MX51)
#define IRAM_BASE_ADDR 0x1FFE8000 /* internal ram */
#elif define (CONFIG_MX53)
#define IRAM_BASE_ADDR 0xF8000000 /* internal ram */
#else
#error "MX5 CPU not supported"
#endif
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2010-06-18 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 15:22 [U-Boot] [U-BOOT][PATCH 1/5] MX53: Add initial support for the Freescale MX53 Jason Liu
2010-06-18 9:23 ` Stefano Babic
2010-06-18 9:50 ` Liu Hui-R64343
[not found] ` <AANLkTim8Xh0VrGc6lIm67lHgcS3PDTJzxB39R819j7GU@mail.gmail.com>
2010-06-23 14:03 ` Stefano Babic
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 2/5] MX53: Add register definitions Jason Liu
2010-06-18 9:35 ` Stefano Babic [this message]
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 3/5] MX53: Add pin and multiplexer definitions Jason Liu
2010-06-18 9:48 ` Stefano Babic
2010-06-18 9:54 ` Liu Hui-R64343
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 4/5] serial_mxc: add support for MX53 processor Jason Liu
2010-06-18 9:52 ` Stefano Babic
2010-06-18 9:55 ` Liu Hui-R64343
2010-06-18 15:22 ` [U-Boot] [U-BOOT][PATCH 5/5] Add initial support for Freescale mx53evk board Jason Liu
2010-06-18 9:45 ` Wolfgang Denk
2010-06-18 10:31 ` Stefano Babic
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=4C1B3DC6.8090807@denx.de \
--to=sbabic@denx.de \
--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