linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin-nonst@stericsson.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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" <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@>
Subject: Re: [RFC PATCHv1 1/2] Export SoC info through sysfs
Date: Thu, 10 Mar 2011 10:58:36 +0100	[thread overview]
Message-ID: <4D78A0CC.1030705@stericsson.com> (raw)
In-Reply-To: <20110309174752.GC1225@sirena.org.uk>

On 03/09/2011 06:47 PM, Mark Brown wrote:
> On Wed, Mar 09, 2011 at 05:59:20PM +0100, Maxime Coquelin wrote:
>
>> +config SYS_SOC
>> +	bool "Export SoC specific informations"
>> +	depends on EMBEDDED
>> +
>>   endmenu
> Would it not be better for this to depend on a symbol that systems can
> select when they add useful output?  If there's nothing that generates
> information for it on a given platform there's no point in enabling it.
>

It is deactivated by default when "default" parameter is not mentioned.

>> +static ssize_t show_info(struct sysdev_class *class,
>> +				struct sysdev_class_attribute *attr, char *buf)
>> +{
>> +	struct sys_soc_info *si = container_of(attr,
>> +			struct sys_soc_info, attr);
>> +
>> +	if (si->info)
>> +		return sprintf(buf, "%s\n", si->info);
>> +	else if (si->get_info)
>> +		return sprintf(buf, "%s\n", si->get_info(si));
> It seems like it'd be easier to pass the output buffer directly to
> get_info(), otherwise the get_info() implementation will have to figure
> out a buffer to return data from.

You're right, I will propose a path with passing the output buffer directly.

Regards,
Maxime

  reply	other threads:[~2011-03-10  9:58 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 [this message]
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 ` [RFC PATCHv1 0/2] Export " Eduardo Valentin
2011-03-10 13:36   ` 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=4D78A0CC.1030705@stericsson.com \
    --to=maxime.coquelin-nonst@stericsson.com \
    --cc=Lee.Jones@linaro.org \
    --cc=Peter.De-Schrijver@nokia.com \
    --cc=a0393775@ti.com \
    --cc=andreiw@motorola.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=davidb@codeaurora.org \
    --cc=eduardo.valentin@nokia.com \
    --cc=jonas.aberg@stericsson.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linus.walleij@linaro.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@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).