From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3 1/2] ARM: kernel: update cpuinfo to print SoC model name
Date: Wed, 30 Jan 2013 23:24:08 +0000 [thread overview]
Message-ID: <20130130232408.GL2637@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1301301402330.6300@xanadu.home>
On Wed, Jan 30, 2013 at 02:07:53PM -0500, Nicolas Pitre wrote:
> On Wed, 30 Jan 2013, Ruslan Bilovol wrote:
>
> > Currently, reading /proc/cpuinfo provides userspace with CPU ID of
> > the CPU carrying out the read from the file.
> > Userspace using this information may decide what module
> > to load or how to configure some specific (and processor-depended)
> > settings or so.
> > However, since really different SoCs can share same ARM core,
> > this information currently is not so useful.
> > For example, TI OMAP4460 and OMAP4470 SoCs show the same
> > information in the /proc/cpuinfo whereas they are different.
> > Since in most cases ARM CPU is a part of some system on a chip (SoC),
> > the "cpuinfo" file looks like exactly that place, where this
> > information have to be displayed.
> >
> > So 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)
> >
> > Example:
> >
> > / # cat proc/cpuinfo
> > [...]
> > CPU variant : 0x2
> > CPU part : 0xc09
> > CPU revision : 10
> >
> > SoC name : OMAP4470
> >
> > Hardware : OMAP4 Blaze Tablet
>
> Please remove that extra blank line between "SoC name" and "Hardware".
> The blank line after "CPU revision" is fine.
>
> Also, please rename this to "System name". Not all systems are "on
> chip". By using "System name" this is more universally useful.
You may notice I've already suggested that this should be using the SoC
infrastructure to export this information, which was explicitly designed
to do this.
If we're going to have one SoC doing one thing and another SoC exporting
this information a completely different way, we're doomed. We need to
make a decision and do it one way and one way only - and that decision
was made when drivers/base/soc.c was merged.
Unfortunately, I'd forgotten about that when I made my initial comments
about the difference between "CPU" and "SoC".
next prev parent reply other threads:[~2013-01-30 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 15:01 [RFC PATCH v3 0/2] ARM: update cpuinfo to print SoC model name Ruslan Bilovol
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 [this message]
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=20130130232408.GL2637@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).