From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] ARM: mx31: Print the silicon version
Date: Mon, 11 Apr 2011 12:16:50 +0200 [thread overview]
Message-ID: <20110411101650.0497B151F83@gemini.denx.de> (raw)
In-Reply-To: <1302491295-11222-1-git-send-email-festevam@gmail.com>
Dear Fabio Estevam,
In message <1302491295-11222-1-git-send-email-festevam@gmail.com> you wrote:
> Use the same method of the Linux kernel to print the MX31 silicon version on
> boot.
>
> Tested on a MX31PDK with a 2.0 silicon, where it shows:
>
> CPU: Freescale i.MX31 at 531 MHz
...
> +#define IMX_CHIP_REVISION_1_0 0x10
> +#define IMX_CHIP_REVISION_1_1 0x11
> +#define IMX_CHIP_REVISION_1_2 0x12
> +#define IMX_CHIP_REVISION_1_3 0x13
> +#define IMX_CHIP_REVISION_2_0 0x20
> +#define IMX_CHIP_REVISION_2_1 0x21
> +#define IMX_CHIP_REVISION_2_2 0x22
> +#define IMX_CHIP_REVISION_2_3 0x23
> +#define IMX_CHIP_REVISION_3_0 0x30
> +#define IMX_CHIP_REVISION_3_1 0x31
> +#define IMX_CHIP_REVISION_3_2 0x32
> +#define IMX_CHIP_REVISION_3_3 0x33
What a nightmare. Does this not give the creeps to any of you who add
to this code?
I'm finally fed up with this, and say NAK here.
Please use something like this instead:
#define IMX_CHIP_REVISION(maj, min) ((maj) * 16 + (min))
Feel free to add appropriate range checking on the parameters,
probably using BUILD_BUG_ON() so it gets caught at compile time.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Common sense and a sense of humor are the same thing, moving at
different speeds. A sense of humor is just common sense, dancing.
- Clive James
prev parent reply other threads:[~2011-04-11 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 3:08 [U-Boot] [PATCH v2] ARM: mx31: Print the silicon version Fabio Estevam
2011-04-11 10:16 ` Wolfgang Denk [this message]
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=20110411101650.0497B151F83@gemini.denx.de \
--to=wd@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