From: Felipe Balbi <felipe.balbi@nokia.com>
To: "Valentin Eduardo (Nokia-D/Helsinki)" <eduardo.valentin@nokia.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
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" <santosh.shilimkar@ti.com>
Subject: Re: [PATCHv2 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 into /proc/cpuinfo
Date: Tue, 27 Apr 2010 18:01:30 +0300 [thread overview]
Message-ID: <20100427150129.GA8600@nokia.com> (raw)
In-Reply-To: <1272374055-9656-3-git-send-email-eduardo.valentin@nokia.com>
On Tue, Apr 27, 2010 at 03:14:13PM +0200, Valentin Eduardo (Nokia-D/Helsinki) wrote:
>From: Eduardo Valentin <eduardo.valentin@nokia.com>
>
>Report OMAP2,3,4 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-omap2/id.c | 21 +++++++++++++++------
> 1 files changed, 15 insertions(+), 6 deletions(-)
>
>diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
>index 37b8a1a..75e36a5 100644
>--- a/arch/arm/mach-omap2/id.c
>+++ b/arch/arm/mach-omap2/id.c
>@@ -152,10 +152,15 @@ void __init omap24xx_check_revision(void)
> j = i;
> }
>
>- pr_info("OMAP%04x", omap_rev() >> 16);
>- if ((omap_rev() >> 8) & 0x0f)
>- pr_info("ES%x", (omap_rev() >> 12) & 0xf);
>- pr_info("\n");
>+ snprintf(system_soc_info, SYSTEM_SOC_INFO_SIZE, "OMAP%04x",
>+ omap_rev() >> 16);
>+ if ((omap_rev() >> 8) & 0x0f) {
>+ int sz = strlen(system_soc_info);
how about you use the return of the first snprintf instead of asking
strlen() here ? I mean:
int sz = snprintf(system_soc_info, SYSTEM_SOC_INFO_SIZE, "OMAP%04x",
omap_rev() >> 16);
if ((omap_rev() >> 8) & 0x0f)
snprintf(system_soc_info + sz, SYSTEM_SOC_INFO_SIZE - sz,
"ES%x", (omap_rev() >> 12) & 0x0f);
would that work ???
--
balbi
DefectiveByDesign.org
WARNING: multiple messages have this Message-ID (diff)
From: felipe.balbi@nokia.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 into /proc/cpuinfo
Date: Tue, 27 Apr 2010 18:01:30 +0300 [thread overview]
Message-ID: <20100427150129.GA8600@nokia.com> (raw)
In-Reply-To: <1272374055-9656-3-git-send-email-eduardo.valentin@nokia.com>
On Tue, Apr 27, 2010 at 03:14:13PM +0200, Valentin Eduardo (Nokia-D/Helsinki) wrote:
>From: Eduardo Valentin <eduardo.valentin@nokia.com>
>
>Report OMAP2,3,4 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-omap2/id.c | 21 +++++++++++++++------
> 1 files changed, 15 insertions(+), 6 deletions(-)
>
>diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
>index 37b8a1a..75e36a5 100644
>--- a/arch/arm/mach-omap2/id.c
>+++ b/arch/arm/mach-omap2/id.c
>@@ -152,10 +152,15 @@ void __init omap24xx_check_revision(void)
> j = i;
> }
>
>- pr_info("OMAP%04x", omap_rev() >> 16);
>- if ((omap_rev() >> 8) & 0x0f)
>- pr_info("ES%x", (omap_rev() >> 12) & 0xf);
>- pr_info("\n");
>+ snprintf(system_soc_info, SYSTEM_SOC_INFO_SIZE, "OMAP%04x",
>+ omap_rev() >> 16);
>+ if ((omap_rev() >> 8) & 0x0f) {
>+ int sz = strlen(system_soc_info);
how about you use the return of the first snprintf instead of asking
strlen() here ? I mean:
int sz = snprintf(system_soc_info, SYSTEM_SOC_INFO_SIZE, "OMAP%04x",
omap_rev() >> 16);
if ((omap_rev() >> 8) & 0x0f)
snprintf(system_soc_info + sz, SYSTEM_SOC_INFO_SIZE - sz,
"ES%x", (omap_rev() >> 12) & 0x0f);
would that work ???
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-04-27 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 13:14 [PATCHv2 0/4] Adding soc related info into /proc/cpuinfo Eduardo Valentin
2010-04-27 13:14 ` Eduardo Valentin
2010-04-27 13:14 ` [PATCHv2 1/4] ARM: Introduce SoC Info " Eduardo Valentin
2010-04-27 13:14 ` Eduardo Valentin
2010-04-27 13:14 ` [PATCHv2 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 " Eduardo Valentin
2010-04-27 13:14 ` [PATCHv2 2/4] mach-omap2: Add SoC info data for OMAP2, 3, 4 " Eduardo Valentin
2010-04-27 15:01 ` Felipe Balbi [this message]
2010-04-27 15:01 ` [PATCHv2 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 " Felipe Balbi
2010-04-28 5:43 ` Eduardo Valentin
2010-04-28 5:43 ` Eduardo Valentin
2010-04-27 13:14 ` [PATCHv2 3/4] mach-omap1: Add SoC info data for OMAP1 " Eduardo Valentin
2010-04-27 13:14 ` Eduardo Valentin
2010-04-27 13:14 ` [PATCHv2 4/4] OMAP3: PM: export chip IDCODE, Production ID and Die ID Eduardo Valentin
2010-04-27 13:14 ` 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=20100427150129.GA8600@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=eduardo.valentin@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 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.