All of lore.kernel.org
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos: print CPU id on probe
Date: Wed, 26 Nov 2014 10:35:15 +0900	[thread overview]
Message-ID: <060f01d00919$3aec6e30$b0c54a90$@kernel.org> (raw)
In-Reply-To: <1416884886-9896-1-git-send-email-olof@lixom.net>

Olof Johansson wrote:
> 
> It's useful to get the CPU ID/rev printed during boot sometimes, so
> add a line with that information. Given that the fields have moved
> within the register over time, don't try to be clever and parse it --
> just print the raw values for now.
> 
> Signed-off-by: Olof Johansson <olof@lixom.net>
> ---
> 
> Kukjin, please apply if you're OK with this. Thanks!
> 
Yes, why not? I'll apply, I have small concerns for exynos5800 though ;)

Thanks,
Kukjin

> 
> -Olof
> 
>  arch/arm/plat-samsung/cpu.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/arm/plat-samsung/cpu.c b/arch/arm/plat-samsung/cpu.c
> index 360618ee39e5..71333bb61013 100644
> --- a/arch/arm/plat-samsung/cpu.c
> +++ b/arch/arm/plat-samsung/cpu.c
> @@ -40,10 +40,14 @@ void __init s3c64xx_init_cpu(void)
>  	}
> 
>  	samsung_cpu_rev = 0;
> +
> +	pr_info("Samsung CPU ID: 0x%08lx\n", samsung_cpu_id);
>  }
> 
>  void __init s5p_init_cpu(void __iomem *cpuid_addr)
>  {
>  	samsung_cpu_id = __raw_readl(cpuid_addr);
>  	samsung_cpu_rev = samsung_cpu_id & 0xFF;
> +
> +	pr_info("Samsung CPU ID: 0x%08lx\n", samsung_cpu_id);
>  }
> --
> 2.0.1.473.gc4d58ca

  reply	other threads:[~2014-11-26  1:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  3:08 [PATCH] ARM: exynos: print CPU id on probe Olof Johansson
2014-11-26  1:35 ` Kukjin Kim [this message]
2014-11-26  1:44   ` Olof Johansson

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='060f01d00919$3aec6e30$b0c54a90$@kernel.org' \
    --to=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.