From: Vitaly Andrianov <vitalya@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/8] ARM: keystone2: Enable CONFIG_DISPLAY_CPUINFO
Date: Wed, 22 Jul 2015 11:56:14 -0400 [thread overview]
Message-ID: <55AFBD1E.20805@ti.com> (raw)
In-Reply-To: <1437579558-26579-3-git-send-email-lokeshvutla@ti.com>
On 07/22/2015 11:39 AM, Lokesh Vutla wrote:
> Add print_cpuinfo() function and enable
> CONFIG_DISPLAY_CPUINFO for keystone platforms,
> so that cpu info can be displayed during boot.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> arch/arm/mach-keystone/init.c | 24 ++++++++++++++++++++++++
> include/configs/ti_armv7_keystone2.h | 1 +
> 2 files changed, 25 insertions(+)
>
> diff --git a/arch/arm/mach-keystone/init.c b/arch/arm/mach-keystone/init.c
> index c96845c..d742ad3 100644
> --- a/arch/arm/mach-keystone/init.c
> +++ b/arch/arm/mach-keystone/init.c
> @@ -149,3 +149,27 @@ void enable_caches(void)
> dcache_enable();
> #endif
> }
> +
> +#if defined(CONFIG_DISPLAY_CPUINFO)
> +int print_cpuinfo(void)
> +{
> + u16 cpu = get_part_number();
> +
> + puts("CPU: ");
> + switch (cpu) {
> + case CPU_66AK2Hx:
> + puts("66AK2Hx\n");
> + break;
> + case CPU_66AK2Lx:
> + puts("66AK2Lx\n");
> + break;
> + case CPU_66AK2Ex:
> + puts("66AK2Ex\n");
> + break;
> + default:
> + puts("Unknown\n");
> + }
> +
> + return 0;
> +}
> +#endif
> diff --git a/include/configs/ti_armv7_keystone2.h b/include/configs/ti_armv7_keystone2.h
> index 198e365..056b938 100644
> --- a/include/configs/ti_armv7_keystone2.h
> +++ b/include/configs/ti_armv7_keystone2.h
> @@ -15,6 +15,7 @@
> /* U-Boot Build Configuration */
> #define CONFIG_SKIP_LOWLEVEL_INIT /* U-Boot is a 2nd stage loader */
> #define CONFIG_BOARD_EARLY_INIT_F
> +#define CONFIG_DISPLAY_CPUINFO
>
> /* SoC Configuration */
> #define CONFIG_ARCH_CPU_INIT
>
Reviewed-by: Vitaly Andrianov <vitalya@ti.com>
next prev parent reply other threads:[~2015-07-22 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 15:39 [U-Boot] [PATCH 0/8] ARM: keystone2: Clocls and PLLs cleanup Lokesh Vutla
2015-07-22 15:39 ` [U-Boot] [PATCH 1/8] ARM: keystone2: Cleanup SoC detection Lokesh Vutla
2015-07-22 15:54 ` Vitaly Andrianov
2015-07-23 19:29 ` Tom Rini
2015-07-24 11:50 ` Lokesh Vutla
2015-07-22 15:39 ` [U-Boot] [PATCH 2/8] ARM: keystone2: Enable CONFIG_DISPLAY_CPUINFO Lokesh Vutla
2015-07-22 15:56 ` Vitaly Andrianov [this message]
2015-07-23 19:29 ` Tom Rini
2015-07-22 15:39 ` [U-Boot] [PATCH 3/8] ARM: keystone2: Cleanup PLL init code Lokesh Vutla
2015-07-23 19:29 ` Tom Rini
2015-07-22 15:39 ` [U-Boot] [PATCH 4/8] ARM: keystone2: Fix dev and arm speed detection Lokesh Vutla
2015-07-23 19:29 ` Tom Rini
2015-07-22 15:39 ` [U-Boot] [PATCH 5/8] ARM: keystone2: Use common structure for PLLs Lokesh Vutla
2015-07-23 19:30 ` Tom Rini
2015-07-22 15:39 ` [U-Boot] [PATCH 6/8] ARM: keystone2: Cleanup init_pll definition Lokesh Vutla
2015-07-23 18:01 ` Vitaly Andrianov
2015-07-24 4:20 ` Lokesh Vutla
2015-07-24 11:48 ` Vitaly Andrianov
2015-07-23 19:30 ` Tom Rini
2015-07-22 15:39 ` [U-Boot] [PATCH 7/8] ARM: keystone2: Remove unsed external clocks Lokesh Vutla
2015-07-23 19:30 ` Tom Rini
2015-07-22 15:39 ` [U-Boot] [PATCH 8/8] ARM: keystone2: Use common definition for clk_get_rate Lokesh Vutla
2015-07-23 19:30 ` Tom Rini
2015-07-22 15:45 ` [U-Boot] [PATCH 0/8] ARM: keystone2: Clocls and PLLs cleanup Lokesh Vutla
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=55AFBD1E.20805@ti.com \
--to=vitalya@ti.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