From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: tegra: fuse: export chip id and revision
Date: Mon, 11 Mar 2013 17:10:29 +0000 [thread overview]
Message-ID: <20130311171029.GO4977@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1363005441-26329-1-git-send-email-dahuang@nvidia.com>
On Mon, Mar 11, 2013 at 08:37:21PM +0800, Danny Huang wrote:
> Expose tegra chip id and revision in /proc/cpu/chipinfo for user mode
> usage.
I thought we weren't exporting this stuff out via procfs, but had a
soc specific way to do it - drivers/base/soc.c ? We have soc_id and
revision attributes there... it seems to do what you want already.
prev parent reply other threads:[~2013-03-11 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 12:37 [PATCH] arm: tegra: fuse: export chip id and revision Danny Huang
2013-03-11 13:51 ` Shawn Guo
2013-03-11 17:10 ` Stephen Warren
2013-03-11 17:10 ` Russell King - ARM Linux [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=20130311171029.GO4977@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).