From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
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 16:19:18 +0000 [thread overview]
Message-ID: <20110310161917.GD27206@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201103101711.59544.arnd@arndb.de>
On Thu, Mar 10, 2011 at 05:11:59PM +0100, Arnd Bergmann wrote:
> On Thursday 10 March 2011, Mark Brown wrote:
> > 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.
If you're doing that things like power domains tend to be a lot more
interesting since you can do something meaningful with them in software.
The non-visible buses aren't reliably documented anyway and the first
procesor datasheet I just pulled up had a whole bunch of devices that
span multiple buses anyway :)
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv1 1/2] Export SoC info through sysfs
Date: Thu, 10 Mar 2011 16:19:18 +0000 [thread overview]
Message-ID: <20110310161917.GD27206@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201103101711.59544.arnd@arndb.de>
On Thu, Mar 10, 2011 at 05:11:59PM +0100, Arnd Bergmann wrote:
> On Thursday 10 March 2011, Mark Brown wrote:
> > 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.
If you're doing that things like power domains tend to be a lot more
interesting since you can do something meaningful with them in software.
The non-visible buses aren't reliably documented anyway and the first
procesor datasheet I just pulled up had a whole bunch of devices that
span multiple buses anyway :)
next prev parent reply other threads:[~2011-03-10 16:19 UTC|newest]
Thread overview: 66+ 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 ` Maxime Coquelin
2011-03-09 16:59 ` Maxime Coquelin
2011-03-09 16:59 ` [RFC PATCHv1 1/2] " Maxime Coquelin
2011-03-09 16:59 ` Maxime Coquelin
2011-03-09 16:59 ` Maxime Coquelin
2011-03-09 17:39 ` Jamie Iles
2011-03-09 17:39 ` Jamie Iles
2011-03-10 9:45 ` Maxime Coquelin
2011-03-10 9:45 ` Maxime Coquelin
2011-03-09 17:47 ` Mark Brown
2011-03-09 17:47 ` Mark Brown
2011-03-10 9:58 ` Maxime Coquelin
2011-03-10 9:58 ` Maxime Coquelin
2011-03-10 13:18 ` Mark Brown
2011-03-10 13:18 ` Mark Brown
2011-03-10 13:16 ` Maxime Coquelin
2011-03-10 13:16 ` Maxime Coquelin
2011-03-09 19:58 ` Arnd Bergmann
2011-03-09 19:58 ` Arnd Bergmann
2011-03-10 12:56 ` Maxime Coquelin
2011-03-10 12:56 ` Maxime Coquelin
2011-03-10 13:25 ` Linus Walleij
2011-03-10 13:25 ` Linus Walleij
2011-03-10 14:08 ` Mark Brown
2011-03-10 14:08 ` Mark Brown
2011-03-10 14:29 ` Arnd Bergmann
2011-03-10 14:29 ` Arnd Bergmann
2011-03-10 14:44 ` Mark Brown
2011-03-10 14:44 ` Mark Brown
2011-03-10 15:02 ` Arnd Bergmann
2011-03-10 15:02 ` Arnd Bergmann
2011-03-10 15:10 ` Russell King - ARM Linux
2011-03-10 15:10 ` Russell King - ARM Linux
2011-03-10 15:17 ` Linus Walleij
2011-03-10 15:17 ` Linus Walleij
2011-03-10 15:21 ` Helmut Raiger
2011-03-10 15:20 ` Mark Brown
2011-03-10 15:20 ` Mark Brown
2011-03-10 16:11 ` Arnd Bergmann
2011-03-10 16:11 ` Arnd Bergmann
2011-03-10 16:19 ` Mark Brown [this message]
2011-03-10 16:19 ` Mark Brown
2011-03-10 16:54 ` Arnd Bergmann
2011-03-10 16:54 ` Arnd Bergmann
2011-03-10 14:23 ` Arnd Bergmann
2011-03-10 14:23 ` Arnd Bergmann
2011-03-10 16:05 ` Linus Walleij
2011-03-10 16:05 ` Linus Walleij
2011-03-10 16:32 ` Arnd Bergmann
2011-03-10 16:32 ` Arnd Bergmann
2011-03-10 17:08 ` Linus Walleij
2011-03-10 17:08 ` Linus Walleij
2011-03-11 16:14 ` Arnd Bergmann
2011-03-11 16:14 ` Arnd Bergmann
2011-03-09 20:38 ` Ryan Mallon
2011-03-09 20:38 ` Ryan Mallon
2011-03-09 16:59 ` [RFC PATCHv1 2/2] ux500: Export U8500 " Maxime Coquelin
2011-03-09 16:59 ` Maxime Coquelin
2011-03-09 16:59 ` Maxime Coquelin
2011-03-09 20:02 ` Arnd Bergmann
2011-03-09 20:02 ` Arnd Bergmann
2011-03-10 13:05 ` [RFC PATCHv1 0/2] Export " Eduardo Valentin
2011-03-10 13:05 ` Eduardo Valentin
2011-03-10 13:36 ` Maxime Coquelin
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=20110310161917.GD27206@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Lee.Jones@linaro.org \
--cc=Peter.De-Schrijver@nokia.com \
--cc=a0393775@ti.com \
--cc=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.