From: Eduardo Valentin <eduardo.valentin@nokia.com>
To: ext Kevin Hilman <khilman@deeprootsystems.com>
Cc: ext Tony Lindgren <tony@atomide.com>,
"De-Schrijver Peter (Nokia-D/Helsinki)"
<Peter.De-Schrijver@nokia.com>,
"Valentin Eduardo (Nokia-D/Helsinki)"
<eduardo.valentin@nokia.com>,
"santosh.shilimkar@ti.com" <santosh.shilimkar@ti.com>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv3 4/4] OMAP3: PM: export chip IDCODE, Production ID and Die ID
Date: Fri, 30 Apr 2010 09:07:10 +0300 [thread overview]
Message-ID: <20100430060710.GC25339@besouro.research.nokia.com> (raw)
In-Reply-To: <87k4rrh7kh.fsf@deeprootsystems.com>
On Wed, Apr 28, 2010 at 06:21:02PM +0200, ext Kevin Hilman wrote:
> Eduardo Valentin <eduardo.valentin@nokia.com> writes:
>
> > From: Eduardo Valentin <eduardo.valentin@nokia.com>
> >
> > This patch exports the OMAP3 IDCODE and Production ID to userspace
> > via /proc/cpuinfo using the system_soc_info.
> >
> > Die ID is also exported depending on what users pass as kernel
> > parameter. It is same protection mechanism made for x86 product
> > number. So, if user passes "omap3_die_id" parameter, it will append
> > die id code into /proc/cpuinfo as well. A Kconfig option has been
> > added as well, so it can be configurable during compilation time.
> >
> > This can be used to track down silicon specific issues. The info is
> > exported via /proc/cpuinfo because then it can be possible to include this
> > in corematic dumps.
> >
> > This is based on Peter De Schrijver patch, which export same info via sysfs.
> >
> > Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com>
>
> Re: $SUBJECT, why the PM: prefix?
Yes indeed, no need to be PM bound.
>
> Kevin
prev parent reply other threads:[~2010-04-30 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 5:51 [PATCHv3 0/4] Adding soc related info into /proc/cpuinfo Eduardo Valentin
2010-04-28 5:51 ` [PATCHv3 1/4] ARM: Introduce SoC Info " Eduardo Valentin
2010-04-28 5:51 ` [PATCHv3 2/4] mach-omap2: Add SoC info data for OMAP2,3,4 " Eduardo Valentin
2010-04-28 5:51 ` [PATCHv3 3/4] mach-omap1: Add SoC info data for OMAP1 " Eduardo Valentin
2010-04-28 5:51 ` [PATCHv3 4/4] OMAP3: PM: export chip IDCODE, Production ID and Die ID Eduardo Valentin
2010-04-28 16:21 ` Kevin Hilman
2010-04-30 6:07 ` Eduardo Valentin [this message]
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=20100430060710.GC25339@besouro.research.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