public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
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>,
	Ambresh <a0393775@ti.com>,
	Saravana Kannan <skannan@codeaurora.org>,
	Jouni Hogander <jouni.hogander@nokia.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>,
	Maxime Coquelin <maxime.coquelin-nonst@stericsson.com>,
	"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,
	Daniel Walker <dwalker@codeauror>
Subject: Re: [RFC PATCHv1 1/2] Export SoC info through sysfs
Date: Thu, 10 Mar 2011 17:11:59 +0100	[thread overview]
Message-ID: <201103101711.59544.arnd@arndb.de> (raw)
In-Reply-To: <20110310152011.GH22195@opensource.wolfsonmicro.com>

On Thursday 10 March 2011, Mark Brown wrote:
> On Thu, Mar 10, 2011 at 04:02:18PM +0100, Arnd Bergmann wrote:
> 
> > I can accept that it's reasonable to put all devices under
> > /sys/devices/platform/ that are on the same top-level AHB or APB bus,
> > although I also don't see a reason against making that bus a single
> > device.
> 
> You could, though the bus will just be a noop.  Typically it's more than
> one bus but software basically can't tell.

Yes. The main reason for representing such a bus in sysfs would be
to match the SOC's block diagram with the structure in the kernel.

The cost of an extra device is roughly zero, but structure generally
helps. Another advantage is that you can associate attributes and names
with the device, and simplify naming of the children without risking
name space conflicts.

	Arnd

  reply	other threads:[~2011-03-10 16:11 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 [this message]
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=201103101711.59544.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Lee.Jones@linaro.org \
    --cc=Peter.De-Schrijver@nokia.com \
    --cc=a0393775@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=davidb@codeaurora.org \
    --cc=dwalker@codeauror \
    --cc=eduardo.valentin@nokia.com \
    --cc=jonas.aberg@stericsson.com \
    --cc=jouni.hogander@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --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