linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.coquelin-nonst@stericsson.com (Maxime Coquelin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv1 0/2] Export SoC info through sysfs
Date: Thu, 10 Mar 2011 14:36:27 +0100	[thread overview]
Message-ID: <4D78D3DB.90708@stericsson.com> (raw)
In-Reply-To: <20110310130527.GA2154@besouro.research.nokia.com>

Hi Eduardo,

On 03/10/2011 02:05 PM, Eduardo Valentin wrote:
>
>> 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?


It would be simpler indeed. But I don't know what are other SoC vendors 
needs, does someone need to export a piece of information which may 
change at runtime? If we all agree that providing a string at 
registration is enough, I'll remove it.

      reply	other threads:[~2011-03-10 13:36 UTC|newest]

Thread overview: 32+ 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:21                 ` Helmut Raiger
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 ` [RFC PATCHv1 0/2] Export " Eduardo Valentin
2011-03-10 13:36   ` Maxime Coquelin [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=4D78D3DB.90708@stericsson.com \
    --to=maxime.coquelin-nonst@stericsson.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).