From: bryanh@codeaurora.org (Bryan Huntsman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] SoC name and revision in /proc/cpuinfo
Date: Fri, 24 Sep 2010 12:23:45 -0700 [thread overview]
Message-ID: <4C9CFAC1.7030006@codeaurora.org> (raw)
In-Reply-To: <20100924144249.GB17651@game.jcrosoft.org>
On 09/24/2010 07:42 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> I knwon the diff between cpu and soc but today others arch do this the same way
> via cpuinfo as example sh or others.
>
> So what do you propose?
>
> is this better
>
> soc familly: at91
> soc type: at91am9g20
> soc revision: 1.1
>
> or you will prefer we create a new entry like sysinfo?
>
> because today we store the hardware name, revision abd serial in cpuinfo
> also
>
> Best Regards,
> J.
How about something like /sys/devices/system/soc/soc0/[family|type|revision]? We're doing something similar and using this location on MSM chips.
- Bryan
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2010-09-24 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 13:53 [RFC] SoC name and revision in /proc/cpuinfo Jean-Christophe PLAGNIOL-VILLARD
2010-09-24 14:06 ` Russell King - ARM Linux
2010-09-24 14:42 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-24 19:23 ` Bryan Huntsman [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=4C9CFAC1.7030006@codeaurora.org \
--to=bryanh@codeaurora.org \
--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).