From: Nishanth Menon <nm@ti.com>
To: "eduardo.valentin@nokia.com" <eduardo.valentin@nokia.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
ext Tony Lindgren <tony@atomide.com>,
ext Kevin Hilman <khilman@deeprootsystems.com>,
"De-Schrijver Peter (Nokia-D/Helsinki)"
<Peter.De-Schrijver@nokia.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"K, Ambresh" <ambresh@ti.com>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
"Hogander Jouni (Nokia-D/Tampere)" <jouni.hogander@nokia.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCHv5 2/3] OMAP: export OMAP info under /proc/socinfo
Date: Wed, 12 May 2010 07:36:22 -0500 [thread overview]
Message-ID: <4BEAA0C6.3020100@ti.com> (raw)
In-Reply-To: <20100512123423.GA11782@besouro.research.nokia.com>
Eduardo Valentin had written, on 05/12/2010 07:34 AM, the following:
> Hello,
>
> On Tue, May 11, 2010 at 06:58:46PM +0200, Valentin Eduardo (Nokia-D/Helsinki) wrote:
>> Hello Nishanth,
>>
>> On Tue, May 11, 2010 at 04:28:15PM +0200, ext Nishanth Menon wrote:
>>> Eduardo Valentin had written, on 05/11/2010 09:15 AM, the following:
>>>> From: Eduardo Valentin <eduardo.valentin@nokia.com>
>>>>
>>>> Export OMAP name and rev under /proc/socinfo node.
>>>>
>>>> Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com>
>>>> ---
>>>> arch/arm/Kconfig | 1 +
>>>> arch/arm/mach-omap1/id.c | 31 ++++++++++++++++++++++++-------
>>>> arch/arm/mach-omap2/id.c | 32 ++++++++++++++++++++++++++------
>>>> 3 files changed, 51 insertions(+), 13 deletions(-)
>>>>
>>> [..]
>>>
>>>> diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
>>>> index 37b8a1a..b67486b 100644
>>>> --- a/arch/arm/mach-omap2/id.c
>>>> +++ b/arch/arm/mach-omap2/id.c
>>> [..]
>>>
>>>> @@ -356,7 +363,8 @@ void __init omap3_cpuinfo(void)
>>>> }
>>>>
>>>> /* Print verbose information */
>>>> - pr_info("%s ES%s (", cpu_name, cpu_rev);
>>>> + snprintf(socinfo, SOCINFO_SZ, "%s ES%s", cpu_name, cpu_rev);
>>>> + pr_info("%s (", socinfo);
>>>>
>>>> OMAP3_SHOW_FEATURE(l2cache);
>>>> OMAP3_SHOW_FEATURE(iva);
>>> Just a minor comment -> is it a good idea to pushin the features to SOC
>>> info as well? currently this is being displayed at bootlog and not
>>> beyond.. might be a better approach to move it into socinfo..
>> Yeah. I would expect that someone would ask this. When I was writing this part
>> I also thought that would be nice to just duplicate all info which is printed
>> into kernel log buffer. But then I decided to proceed with only the info we are
>> needing from userspace. If you think that would be useful to know those as well,
>> then why not adding them.
>
> As discussed in #linux-omap IRC channel, we agreed that it would be nice and useful
> to export the OMAP FEATURES under this interface. But as the code to detect omap features is
> under re-work currently, for now we are going to leave it out of this patch set.
>
Agreed. other than this, I dont see an issue :) thanks for the work..
Acked-by: Nishanth Menon <nm@ti.com>
>>>
>>> [..]
>>>
>>> --
>>> Regards,
>>> Nishanth Menon
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-05-12 12:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 14:15 [PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data Eduardo Valentin
2010-05-11 14:15 ` [PATCHv5 1/3] procfs: Introduce socinfo under /proc Eduardo Valentin
2010-05-11 14:15 ` [PATCHv5 2/3] OMAP: export OMAP info under /proc/socinfo Eduardo Valentin
2010-05-11 14:28 ` Nishanth Menon
2010-05-11 16:58 ` Eduardo Valentin
2010-05-12 12:34 ` Eduardo Valentin
2010-05-12 12:36 ` Nishanth Menon [this message]
2010-05-11 14:15 ` [PATCHv5 3/3] OMAP3: export chip IDCODE, Production ID and Die ID Eduardo Valentin
2010-05-12 22:24 ` [PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data Andrew Morton
2010-05-14 8:24 ` Eduardo Valentin
2010-05-14 16:27 ` Tony Lindgren
2011-02-15 12:58 ` Linus Walleij
2011-02-16 11:57 ` Eduardo Valentin
2011-02-28 10:28 ` Maxime Coquelin
2011-03-01 4:51 ` Saravana Kannan
2011-03-02 1:13 ` Andrei Warkentin
2011-03-02 1:19 ` Saravana Kannan
[not found] ` <4D6D9D06.2020204@bluewatersys.com>
[not found] ` <4D6D9FC7.1090206@codeaurora.org>
[not found] ` <4D6DA290.2010607@bluewatersys.com>
[not found] ` <4D6DAA24.3000204@codeaurora.org>
[not found] ` <4D6DAE6E.4030701@bluewatersys.com>
2011-03-02 2:55 ` Saravana Kannan
2011-03-02 3:11 ` Ryan Mallon
2011-03-02 3:21 ` Saravana Kannan
2011-03-02 3:35 ` Ryan Mallon
2011-03-02 3:46 ` Saravana Kannan
2011-03-02 3:54 ` Ryan Mallon
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=4BEAA0C6.3020100@ti.com \
--to=nm@ti.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=ambresh@ti.com \
--cc=eduardo.valentin@nokia.com \
--cc=felipe.balbi@nokia.com \
--cc=jouni.hogander@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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).