From: Eduardo Valentin <eduardo.valentin@nokia.com>
To: ext Maxime Coquelin <maxime.coquelin-nonst@stericsson.com>
Cc: ext Nishanth Menon <nm@ti.com>,
ext Tony Lindgren <tony@atomide.com>,
Peter De-Schrijver <Peter.De-Schrijver@nokia.com>,
Linus Walleij <linus.walleij@linaro.org>,
Ambresh <a0393775@ti.com>,
Saravana Kannan <skannan@codeaurora.org>,
Andrei Warkentin <andreiw@motorola.com>,
Lee Jones <Lee.Jones@linaro.org>,
Rabin VINCENT <rabin.vincent@stericsson.com>,
Russell King <linux@arm.linux.org.uk>,
Jonas ABERG <jonas.aberg@stericsson.com>,
ext Kevin Hilman <khilman@deeprootsystems.com>,
David Brown <davidb@codeaurora.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Loic PALLARDY <loic.pallardy@stericsson.com>,
"eduardo.valentin@nokia.com" <eduardo.valentin@nokia.com>,
maxime_coquelin@yahoo.fr, Ryan Mallon <ryan@bluewatersys.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Daniel
Subject: Re: [RFC PATCHv1 0/2] Export SoC info through sysfs
Date: Thu, 10 Mar 2011 15:05:27 +0200 [thread overview]
Message-ID: <20110310130527.GA2154@besouro.research.nokia.com> (raw)
In-Reply-To: <1299689961-5028-1-git-send-email-maxime.coquelin-nonst@stericsson.com>
Hi,
Back after long silent :-)
On Wed, Mar 09, 2011 at 05:59:19PM +0100, ext Maxime Coquelin wrote:
> 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
Thanks for taking this further. Looks much more promising now :-).
>
> 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.
Do you mind refreshing my memory why we need two ways of providing data to these attributes?
I mean, I think if we provide the attribute value during registration time should be enough
and simpler.
Unless you guys are talking about attributes with changes over the time, I don't really see
the need for the callback there. At least from the original scope, I don't see any attributes
which would be exported under soc info which would change over the time.
Or am I missing something?
>
> 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
--
Eduardo Valentin
next prev parent reply other threads:[~2011-03-10 13:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 16:59 [RFC PATCHv1 0/2] Export SoC info through sysfs Maxime Coquelin
2011-03-09 16:59 ` [RFC PATCHv1 1/2] " Maxime Coquelin
2011-03-09 17:39 ` Jamie Iles
2011-03-10 9:45 ` Maxime Coquelin
2011-03-09 17:47 ` Mark Brown
2011-03-10 9:58 ` Maxime Coquelin
2011-03-10 13:18 ` Mark Brown
2011-03-10 13:16 ` Maxime Coquelin
2011-03-09 19:58 ` Arnd Bergmann
2011-03-10 12:56 ` Maxime Coquelin
2011-03-10 13:25 ` Linus Walleij
2011-03-10 14:08 ` Mark Brown
2011-03-10 14:29 ` Arnd Bergmann
2011-03-10 14:44 ` Mark Brown
2011-03-10 15:02 ` Arnd Bergmann
2011-03-10 15:10 ` Russell King - ARM Linux
2011-03-10 15:17 ` Linus Walleij
2011-03-10 15:20 ` Mark Brown
2011-03-10 16:11 ` Arnd Bergmann
2011-03-10 16:19 ` Mark Brown
2011-03-10 16:54 ` Arnd Bergmann
2011-03-10 14:23 ` Arnd Bergmann
2011-03-10 16:05 ` Linus Walleij
2011-03-10 16:32 ` Arnd Bergmann
2011-03-10 17:08 ` Linus Walleij
2011-03-11 16:14 ` Arnd Bergmann
2011-03-09 20:38 ` Ryan Mallon
2011-03-09 16:59 ` [RFC PATCHv1 2/2] ux500: Export U8500 " Maxime Coquelin
2011-03-09 20:02 ` Arnd Bergmann
2011-03-10 13:05 ` Eduardo Valentin [this message]
2011-03-10 13:36 ` [RFC PATCHv1 0/2] Export " Maxime Coquelin
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=20110310130527.GA2154@besouro.research.nokia.com \
--to=eduardo.valentin@nokia.com \
--cc=Lee.Jones@linaro.org \
--cc=Peter.De-Schrijver@nokia.com \
--cc=a0393775@ti.com \
--cc=andreiw@motorola.com \
--cc=davidb@codeaurora.org \
--cc=jonas.aberg@stericsson.com \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=loic.pallardy@stericsson.com \
--cc=maxime.coquelin-nonst@stericsson.com \
--cc=maxime_coquelin@yahoo.fr \
--cc=nm@ti.com \
--cc=rabin.vincent@stericsson.com \
--cc=ryan@bluewatersys.com \
--cc=skannan@codeaurora.org \
--cc=tony@atomide.com \
/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).