From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name
Date: Tue, 29 Jan 2013 10:11:05 -0600 [thread overview]
Message-ID: <5107F499.2050608@gmail.com> (raw)
In-Reply-To: <1359474865-15408-1-git-send-email-ruslan.bilovol@ti.com>
On 01/29/2013 09:54 AM, Ruslan Bilovol wrote:
> Hi,
>
> The following patches update cpuinfo to print CPU
> model name for ARM. First patch exactly makes needed
> changes for ARM architecture.
> Second patch adds this ability to OMAP4 SoCs.
>
> This adds a common approach to show SoC name.
>
> Looks like there were few attempts to do similar
> changes to cpuinfo without any luck.
Care to point out how your solution is different from those or addresses
the issues with them.
Assuming we want to do this, I think this information should come from
DeviceTree. OMAP may have this in a register, but others don't.
Rob
>
> So - comments are welcome
>
> Ruslan Bilovol (2):
> ARM: kernel: update cpuinfo to print CPU model name
> ARM: OMAP4: setup CPU model name during ID initialisation
>
> arch/arm/include/asm/setup.h | 1 +
> arch/arm/kernel/setup.c | 10 ++++++++++
> arch/arm/mach-omap2/id.c | 18 ++++++++++++++++--
> 3 files changed, 27 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2013-01-29 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 15:54 [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name Ruslan Bilovol
2013-01-29 15:54 ` [RFC PATCH 1/2] ARM: kernel: " Ruslan Bilovol
2013-01-29 16:08 ` Russell King - ARM Linux
2013-01-29 23:12 ` Ruslan Bilovol
2013-01-30 5:52 ` Santosh Shilimkar
2013-01-30 7:42 ` anish singh
2013-01-29 15:54 ` [RFC PATCH 2/2] ARM: OMAP4: setup CPU model name during ID initialisation Ruslan Bilovol
2013-01-29 16:02 ` [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name Nishanth Menon
2013-01-29 23:08 ` Ruslan Bilovol
2013-01-29 23:38 ` Nishanth Menon
2013-01-30 13:20 ` Ruslan Bilovol
2013-01-29 16:11 ` Rob Herring [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=5107F499.2050608@gmail.com \
--to=robherring2@gmail.com \
--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).