mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ruslan Bilovol <ruslan.bilovol@ti.com>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, tony@atomide.com,
	linux@arm.linux.org.uk, eduardo.valentin@ti.com
Subject: [RFC PATCH v3 0/2] ARM: update cpuinfo to print SoC model name
Date: Wed, 30 Jan 2013 17:01:29 +0200	[thread overview]
Message-ID: <1359558091-29251-1-git-send-email-ruslan.bilovol@ti.com> (raw)


The following patches update cpuinfo to print SoC
model name for ARM.
The first patch exactly makes needed changes for ARM
architecture and adds a common approach to show SoC name.
Second patch uses this approach for TI OMAP4 SoCs (as live
example).

Why we need it?

First - the /proc/cpuinfo becomes more informative.
Added new line "SoC name" in the "cpuinfo" output for system
on a chip name. It is placed between CPU information and machine
information, so the file structure looks gracefully
('CPU-SoC-Hardware' instead of 'CPU-Hardware' that we have now)

Second - this information may be used by userspace
for different purposes (as example - OMAP4460 and
OMAP4470 SoCs have different graphics accelerators,
and userspace may want to know what libraries
to use and what module to insert if the graphics
drivers are built as modules)

Looks like there were few attempts to do similar
changes to cpuinfo without any luck (had stuck
on review) so this functionality is still not
in the kernel yet.
In this patch series the update to cpuinfo is very
short (10 lines) and easy.

Comments are welcome as usual

--------------------------------------------------
v3:
Addressed comments from Nishanth (changed 'SoC name'
field for OMAP - now it shows only SoC name without
additional info)

Updated commit messages. Updated this cover letter
with additional information

--------------------------------------------------
v2:
Addressed comments from Russel (changed 'CPU name' > 'SoC name')
Updatet commit messages. Updated cover letter

Ruslan Bilovol (2):
  ARM: kernel: update cpuinfo to print SoC model name
  ARM: OMAP4: setup SoC model name during ID initialisation

 arch/arm/include/asm/setup.h |    1 +
 arch/arm/kernel/setup.c      |    9 +++++++++
 arch/arm/mach-omap2/id.c     |    5 +++++
 3 files changed, 15 insertions(+)

-- 
1.7.9.5


             reply	other threads:[~2013-01-30 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 15:01 Ruslan Bilovol [this message]
2013-01-30 15:01 ` [RFC PATCH v3 1/2] ARM: kernel: " Ruslan Bilovol
2013-01-30 19:07   ` Nicolas Pitre
2013-01-30 20:37     ` Matt Sealey
2013-01-30 21:02       ` Nicolas Pitre
2013-01-30 23:24     ` Russell King - ARM Linux
2013-01-31  0:33       ` Nicolas Pitre
2013-01-31 11:50       ` Ruslan Bilovol
2013-01-30 23:18   ` Jean-Christophe PLAGNIOL-VILLARD
2013-01-30 15:01 ` [RFC PATCH v3 2/2] ARM: OMAP4: setup SoC model name during ID initialisation Ruslan Bilovol
2013-01-30 15:57   ` Russell King - ARM Linux

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=1359558091-29251-1-git-send-email-ruslan.bilovol@ti.com \
    --to=ruslan.bilovol@ti.com \
    --cc=eduardo.valentin@ti.com \
    --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=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

all inboxes | Powered by JetHome®