From: Eduardo Valentin <eduardo.valentin@nokia.com>
To: linux-arm-kernel@lists.infradead.org,
Linux-OMAP <linux-omap@vger.kernel.org>
Cc: ext Tony Lindgren <tony@atomide.com>,
ext Kevin Hilman <khilman@deeprootsystems.com>,
"\\\"De-Schrijver Peter (Nokia-D/Helsinki)\\\""
<Peter.De-Schrijver@nokia.com>,
santosh.shilimkar@ti.com, felipe.balbi@nokia.com,
Eduardo Valentin <eduardo.valentin@nokia.com>
Subject: [RESEND PATCHv3 3/4] mach-omap1: Add SoC info data for OMAP1 into /proc/cpuinfo
Date: Wed, 5 May 2010 11:42:07 +0300 [thread overview]
Message-ID: <1273048928-6105-4-git-send-email-eduardo.valentin@nokia.com> (raw)
In-Reply-To: <1273048928-6105-1-git-send-email-eduardo.valentin@nokia.com>
From: Eduardo Valentin <eduardo.valentin@nokia.com>
Report OMAP data into system_soc_info. Now we get omap
information under /proc/cpuinfo.
Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com>
---
arch/arm/mach-omap1/id.c | 15 +++++++++------
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-omap1/id.c b/arch/arm/mach-omap1/id.c
index a0e3560..9a84347 100644
--- a/arch/arm/mach-omap1/id.c
+++ b/arch/arm/mach-omap1/id.c
@@ -120,7 +120,7 @@ static u8 __init omap_get_die_rev(void)
void __init omap_check_revision(void)
{
- int i;
+ int i, sz;
u16 jtag_id;
u8 die_rev;
u32 omap_id;
@@ -194,11 +194,14 @@ void __init omap_check_revision(void)
printk(KERN_INFO "Unknown OMAP cpu type: 0x%02x\n", cpu_type);
}
- printk(KERN_INFO "OMAP%04x", omap_revision >> 16);
+ sz = snprintf(system_soc_info, SYSTEM_SOC_INFO_SIZE, "OMAP%04x",
+ omap_revision >> 16);
if ((omap_revision >> 8) & 0xff)
- printk(KERN_INFO "%x", (omap_revision >> 8) & 0xff);
- printk(KERN_INFO " revision %i handled as %02xxx id: %08x%08x\n",
- die_rev, omap_revision & 0xff, system_serial_low,
- system_serial_high);
+ snprintf(system_soc_info + sz, SYSTEM_SOC_INFO_SIZE - sz,
+ "%x", (omap_revision >> 8) & 0xff);
+ pr_info("%s revision %i handled as %02xxx id: %08x%08x\n",
+ system_soc_info, die_rev, omap_revision & 0xff,
+ system_serial_low, system_serial_high);
+
}
--
1.7.0.4.361.g8b5fe.dirty
next prev parent reply other threads:[~2010-05-05 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 8:42 [RESEND PATCHv3 0/4] Adding soc related info into /proc/cpuinfo Eduardo Valentin
2010-05-05 8:42 ` [RESEND PATCHv3 1/4] ARM: Introduce SoC Info " Eduardo Valentin
2010-05-05 8:42 ` [RESEND PATCHv3 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 " Eduardo Valentin
2010-05-05 8:42 ` Eduardo Valentin [this message]
2010-05-05 8:42 ` [RESEND PATCHv3 4/4] OMAP3: export chip IDCODE, Production ID and Die ID Eduardo Valentin
2010-05-05 8:59 ` [RESEND PATCHv3 0/4] Adding soc related info into /proc/cpuinfo Russell King - ARM Linux
2010-05-10 10:33 ` Eduardo Valentin
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=1273048928-6105-4-git-send-email-eduardo.valentin@nokia.com \
--to=eduardo.valentin@nokia.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=felipe.balbi@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).