From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] mxs: generalize code for print_cpuinfo()
Date: Sat, 23 Jun 2012 22:08:52 +0200 [thread overview]
Message-ID: <201206232208.52632.marex@denx.de> (raw)
In-Reply-To: <1340482108-18468-5-git-send-email-otavio@ossystems.com.br>
Dear Otavio Salvador,
> The information now is gathered from HW_DIGCTL_CHIPID register and
> includes the revision of the chip on the output.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Stefano Babic <sbabic@denx.de>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/cpu/arm926ejs/mx28/mx28.c | 58
> ++++++++++++++++++++++++++++++++++-- 1 file changed, 56 insertions(+), 2
> deletions(-)
>
> diff --git a/arch/arm/cpu/arm926ejs/mx28/mx28.c
> b/arch/arm/cpu/arm926ejs/mx28/mx28.c index a82ff25..15be605 100644
> --- a/arch/arm/cpu/arm926ejs/mx28/mx28.c
> +++ b/arch/arm/cpu/arm926ejs/mx28/mx28.c
> @@ -38,6 +38,11 @@
>
> DECLARE_GLOBAL_DATA_PTR;
>
> +/* Product code identification */
> +#define CHIPID_MASK (0xffff << 16)
> +#define CHIPID_MX23 (0x3780 << 16)
> +#define CHIPID_MX28 (0x2800 << 16)
Don't we have arch/arm/include/asm-mx28/regs-digctl.h ?
[...]
Rest seems ok
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-23 20:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 20:08 [U-Boot] [PATCH 1/4] cmd_bootm: fix compilation warning for assigned but never used variable Otavio Salvador
2012-06-23 20:08 ` [U-Boot] [PATCH 2/4] mx53loco: add a comment about local copy of print_cpuinfo method Otavio Salvador
2012-06-23 20:07 ` Otavio Salvador
2012-06-23 20:09 ` Marek Vasut
2012-06-24 7:53 ` Wolfgang Denk
2012-06-24 19:02 ` Otavio Salvador
2012-06-24 22:04 ` Wolfgang Denk
2012-06-24 22:10 ` Otavio Salvador
2012-06-23 20:08 ` [U-Boot] [PATCH 2/4] mx53loco: Add a comment about local print_cpuinfo method in board file Otavio Salvador
2012-06-24 7:55 ` Wolfgang Denk
2012-06-24 19:11 ` Otavio Salvador
2012-06-24 21:23 ` Otavio Salvador
2012-06-24 22:05 ` Wolfgang Denk
2012-06-24 22:12 ` Otavio Salvador
2012-06-24 22:53 ` Wolfgang Denk
2012-06-25 3:35 ` Fabio Estevam
2012-06-23 20:08 ` [U-Boot] [PATCH 3/4] imx: Use a clear identification of an unidentified CPU type Otavio Salvador
2012-06-24 6:57 ` Wolfgang Denk
2012-06-24 13:08 ` Marek Vasut
2012-06-24 13:19 ` Fabio Estevam
2012-06-24 13:43 ` Marek Vasut
2012-06-24 13:52 ` Wolfgang Denk
2012-06-24 19:48 ` Otavio Salvador
2012-06-24 19:53 ` Marek Vasut
2012-06-24 19:57 ` Otavio Salvador
2012-06-24 22:08 ` Wolfgang Denk
2012-06-24 22:17 ` Otavio Salvador
2012-06-25 0:20 ` Marek Vasut
2012-06-23 20:08 ` [U-Boot] [PATCH 4/4] mxs: generalize code for print_cpuinfo() Otavio Salvador
2012-06-23 20:08 ` Marek Vasut [this message]
2012-06-23 20:31 ` [U-Boot] [PATCH 4/4 v2] " Otavio Salvador
2012-06-23 22:56 ` [U-Boot] [PATCH 1/4] cmd_bootm: fix compilation warning for assigned but never used variable Wolfgang Denk
2012-06-23 23:00 ` Otavio Salvador
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=201206232208.52632.marex@denx.de \
--to=marex@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