linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/4] Adding soc related info into /proc/cpuinfo
Date: Wed,  5 May 2010 11:42:04 +0300	[thread overview]
Message-ID: <1273048928-6105-1-git-send-email-eduardo.valentin@nokia.com> (raw)

Hello all,

I'm resending this series with minor change in the subject prefix of patch 4/4.
Removed the PM: prefix. Everything else is same. So, I kept the v3 prefix as well.

v3:
And now v3 of this series. Basically a minor change wrt string manipulation.
No need to use strlen in so many places. Previous log for reference:

v2:

Here is the version 2 of this series. Now die id is protected using
same x86 protection mechanism to hide x86 product number. Besides,
a compilation Kconfig option has been added for DIE ID as well.

Here is previous PATCH 0/4 message:

v1:

This series is to continue what has been discussed several weeks ago
wrt IDCODE patch. Original patch was made by Peter and discussion is here:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg17553.html

So, the conclusion was that IDCODE info is useful even in production systems,
and for that debugfs is not a good choice to export it. One suggestion was to
add it under /proc/cpuinfo. However this entry nowadays exports only ARM related
information.

So this series does the trick by extending the ARM /proc/cpuinfo to include
soc info data. There are a few ways to add a hook for soc specific data. But
I've decided to implement it via the simplest way I found. Basically it is
same thing which is done for system_rev, system_serial_low and system_serial_high.
Then, now we have system_soc_info, which is printed only if there is something
useful there.

As usual, comments are welcome.

BR,

 *** SUBJECT HERE ***

*** BLURB HERE ***

Eduardo Valentin (4):
  ARM: Introduce SoC Info into /proc/cpuinfo
  mach-omap2: Add SoC info data for OMAP2,3,4 into /proc/cpuinfo
  mach-omap1: Add SoC info data for OMAP1 into /proc/cpuinfo
  OMAP3: export chip IDCODE, Production ID and Die ID

 Documentation/kernel-parameters.txt |    2 +
 arch/arm/include/asm/system.h       |    2 +
 arch/arm/kernel/setup.c             |    5 +++
 arch/arm/mach-omap1/id.c            |   15 ++++++----
 arch/arm/mach-omap2/Kconfig         |   10 +++++++
 arch/arm/mach-omap2/id.c            |   51 ++++++++++++++++++++++++++++++----
 6 files changed, 73 insertions(+), 12 deletions(-)


             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 Eduardo Valentin [this message]
2010-05-05  8:42 ` [RESEND PATCHv3 1/4] ARM: Introduce SoC Info into /proc/cpuinfo 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 ` [RESEND PATCHv3 3/4] mach-omap1: Add SoC info data for OMAP1 " Eduardo Valentin
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-1-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).