From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: remove name from machine_desc for DT platforms
Date: Thu, 14 Nov 2013 08:46:14 -0600 [thread overview]
Message-ID: <5284E236.1000606@gmail.com> (raw)
In-Reply-To: <CACxGe6uMWjfmB4WDKs+vu05224jqpbDZBHT_ZXnqxw17JzUqvw@mail.gmail.com>
On 11/14/2013 07:33 AM, Grant Likely wrote:
> On Thu, Nov 14, 2013 at 9:32 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Wednesday 13 November 2013, Rob Herring wrote:
>>> I'm not inclined to expand cpuinfo and prior attempts to add more info
>>> to cpuinfo like SoC name have failed. The differences between x86 and
>>> arm cpuinfo already cause issues for arm. lscpu does not really work on arm.
>>
>> Well, they turned into drivers/base/soc.c, which adds the information in
>> a structured way in sysfs, but is only used on a couple of platforms.
>>
>>> I'd actually prefer If you really want more system info, then go read
>>> /proc/device-tree.
>
> I really don't mind pulling that information out of /proc/cpuinfo. My
> point is merely that it is incredibly useful to be able to easily find
> out exactly which machine_desc got chosen on any given platform. I
> don't think I should have to grep the source tree to figure that out.
>
> The kernel log is useful, but it is also helpful to have it in a /proc
> or /sysfs file for when the kernel log overflows. /proc/device-tree
> doesn't give that information.
Either we want to shrink/remove machine_desc or we don't. If we do, then
the name has to go at some point. So what is the reason to remove it
later rather than sooner? Later means we will have "Generic DT based
system" in cpuinfo as platforms transition. Perhaps that is useful to
know in the short term, but once all platforms print the same thing the
information becomes useless. Then we either remove Hardware field from
cpuinfo or change to use DT info. That's changing the string twice
rather than once.
We probably have at least a dozen machine_desc's we are close to being
able to remove (sunxi, picoxcell, highbank, dove, rockchip, virt,
several sh-mobile). There's also more that probably can be combined
together which will change the string in /proc/cpuinfo.
If this is a required feature then we should make machine_desc common
(or at least part of it) with the other arches that have copied arm and
then add it to arm64 as well. Then I could do further consolidation of
the FDT machine matching code. Otherwise this is all just pointless
architecture variation that really has nothing to do with the architecture.
Rob
next prev parent reply other threads:[~2013-11-14 14:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 20:50 [PATCH v2] ARM: remove name from machine_desc for DT platforms Rob Herring
[not found] ` < CAOesGMg7Mt+p8U7Z5sLQDqoFG-QEUi94Vt=pxXM0NqyefBLxVA@mail.gmail.com>
2013-11-04 11:36 ` Grant Likely
2013-11-05 14:34 ` Rob Herring
2013-11-05 17:44 ` Matt Sealey
2013-11-11 17:38 ` Olof Johansson
2013-11-13 19:00 ` Rob Herring
2013-11-13 19:21 ` Olof Johansson
2013-11-13 20:04 ` Rob Herring
2013-11-14 12:32 ` Arnd Bergmann
[not found] ` < CACxGe6uMWjfmB4WDKs+vu05224jqpbDZBHT_ZXnqxw17JzUqvw@mail.gmail.com>
[not found] ` < 5284E236.1000606@gmail.com>
[not found] ` < CACxGe6sgRwiakJLUCtaaQ2NF51PpkoNZvZr6EoE-BPeZiDsDFQ@mail.gmail.com>
2013-11-14 13:33 ` Grant Likely
2013-11-14 14:46 ` Rob Herring [this message]
2013-11-14 17:16 ` Grant Likely
2013-11-14 23:17 ` Rob Herring
2013-11-18 12:59 ` Grant Likely
2013-11-18 13:54 ` Russell King - ARM Linux
2013-11-19 13:43 ` Grant Likely
2013-11-21 23:53 ` Rob Herring
2013-11-15 19:13 ` Russell King - ARM Linux
2013-11-15 20:16 ` Rob Herring
2013-11-15 21:05 ` Arnd Bergmann
2013-11-14 20:33 ` Matt Sealey
2013-11-15 16:08 ` Rob Herring
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=5284E236.1000606@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).