From: dahuang@nvidia.com (Danny Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: tegra: fuse: export chip id and revision
Date: Mon, 11 Mar 2013 20:37:21 +0800 [thread overview]
Message-ID: <1363005441-26329-1-git-send-email-dahuang@nvidia.com> (raw)
Expose tegra chip id and revision in /proc/cpu/chipinfo for user mode
usage.
Signed-off-by: Danny Huang <dahuang@nvidia.com>
---
arch/arm/mach-tegra/fuse.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/mach-tegra/fuse.c b/arch/arm/mach-tegra/fuse.c
index f7db078..7895542 100644
--- a/arch/arm/mach-tegra/fuse.c
+++ b/arch/arm/mach-tegra/fuse.c
@@ -20,6 +20,7 @@
#include <linux/kernel.h>
#include <linux/io.h>
#include <linux/export.h>
+#include <linux/proc_fs.h>
#include <linux/tegra-soc.h>
#include "fuse.h"
@@ -43,6 +44,7 @@ enum tegra_revision tegra_revision;
static int tegra_fuse_spare_bit;
static void (*tegra_init_speedo_data)(void);
+static struct proc_dir_entry *proc_entry;
/* The BCT to use at boot is specified by board straps that can be read
* through a APB misc register and decoded. 2 bits, i.e. 4 possible BCTs.
@@ -161,3 +163,20 @@ unsigned long long tegra_chip_uid(void)
return (hi << 32ull) | lo;
}
EXPORT_SYMBOL(tegra_chip_uid);
+
+static int show_chip_info(char *page, char **start, off_t offset,
+ int count, int *eof, void *data)
+{
+ return snprintf(page, count, "tegra_chip_id: %d\ntegra_chip_rev: %d\n",
+ tegra_chip_id, tegra_revision);
+}
+
+static int __init tegra_chip_info(void)
+{
+ proc_entry = create_proc_entry("cpu/chipinfo", S_IRUGO, NULL);
+ if (proc_entry)
+ proc_entry->read_proc = show_chip_info;
+ return 0;
+}
+
+late_initcall(tegra_chip_info);
--
1.8.1.5
next reply other threads:[~2013-03-11 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 12:37 Danny Huang [this message]
2013-03-11 13:51 ` [PATCH] arm: tegra: fuse: export chip id and revision Shawn Guo
2013-03-11 17:10 ` Stephen Warren
2013-03-11 17:10 ` 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=1363005441-26329-1-git-send-email-dahuang@nvidia.com \
--to=dahuang@nvidia.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).