linux-kernel - [RFC PATCHv1 0/2] Export SoC info through sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Mar 2011 17:59:19 +0100
From:	Maxime Coquelin <maxime.coquelin-nonst@...ricsson.com>
To:	LKML <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"eduardo.valentin@...ia.com" <eduardo.valentin@...ia.com>,
	Saravana Kannan <skannan@...eaurora.org>,
	Ryan Mallon <ryan@...ewatersys.com>,
	Linus Walleij <linus.walleij@...aro.org>
Cc:	<maxime_coquelin@...oo.fr>, ext Nishanth Menon <nm@...com>,
	ext Tony Lindgren <tony@...mide.com>,
	Peter De-Schrijver <Peter.De-Schrijver@...ia.com>,
	Ambresh <a0393775@...com>,
	Jouni Hogander <jouni.hogander@...ia.com>,
	Lee Jones <Lee.Jones@...aro.org>,
	Rabin VINCENT <rabin.vincent@...ricsson.com>,
	Russell King <linux@....linux.org.uk>,
	Jonas ABERG <jonas.aberg@...ricsson.com>,
	ext Kevin Hilman <khilman@...prootsystems.com>,
	David Brown <davidb@...eaurora.org>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	Loic PALLARDY <loic.pallardy@...ricsson.com>,
	Linux-OMAP <linux-omap@...r.kernel.org>,
	Daniel Walker <dwalker@...eaurora.org>,
	Andrei Warkentin <andreiw@...orola.com>,
	Paul Mundt <lethal@...ux-sh.org>,
	"santosh.shilimkar@...com" <santosh.shilimkar@...com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Maxime Coquelin <maxime.coquelin-nonst@...ricsson.com>
Subject: [RFC PATCHv1 0/2] Export SoC info through sysfs

Here is the first version of the proposal to export SoC related information to user-space through sysFS interface.

This serie is to continue what has been discussed on the "socinfo" thread created by Eduardo Valentin:
https://lkml.org/lkml/2010/5/11/364

The first patch introduces the common part, which provides an interface to the platform to register its name, and exports platform-defined IDs to user-space.
The IDs strings can be provided in two ways: either with a pointer to the string, or by a callback returning the string.

The second patch is given as example for the ux500 architecture. It registers with the machine name "DB8500", and exports 3 informations (SoC unique ID, sili
con revision and silicon process).

Here is the output for DB8500:
root@ME:/sys/devices/system/soc ls -l
-r--r--r--    1 root     root         4096 Jan 11 02:43 mach_name
-r--r--r--    1 root     root         4096 Jan 11 02:43 process
-r--r--r--    1 root     root         4096 Jan 11 02:43 revision
-r--r--r--    1 root     root         4096 Jan 11 02:43 soc_id
root@ME:/sys/devices/system/soc cat mach_name
DB8500
root@ME:/sys/devices/system/soc cat process
Standard
root@ME:/sys/devices/system/soc cat revision
2.0
root@ME:/sys/devices/system/soc cat soc_id
2ba07ce9e5835d6185321e9577462ef2ea2129cf

Any comments are welcome.

Note that I will be off from 13th to 21th of March.

Regards,
Maxime

-------------------------------------------------------------------------------

Maxime Coquelin (2):
  Export SoC info through sysfs
  ux500: Export U8500 SoC info through sysfs

 arch/arm/mach-ux500/id.c |   96 ++++++++++++++++++++++++++++++++++++++++++++++
 drivers/base/Kconfig     |    4 ++
 drivers/base/Makefile    |    1 +
 drivers/base/soc.c       |   88 ++++++++++++++++++++++++++++++++++++++++++
 include/linux/sys_soc.h  |   33 ++++++++++++++++
 5 files changed, 222 insertions(+), 0 deletions(-)
 create mode 100644 drivers/base/soc.c
 create mode 100644 include/linux/sys_soc.h

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/