On Thursday 10 March 2011, Mark Brown wrote:

On Thu, Mar 10, 2011 at 05:11:59PM +0100, Arnd Bergmann wrote:

quoted

On Thursday 10 March 2011, Mark Brown wrote:

quoted

quoted

You could, though the bus will just be a noop.  Typically it's more than
one bus but software basically can't tell.

quoted

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 :)

Yes, I'm aware that devices are not alwasy in a clear hierarchy and
that you have bus addressing, device driver, clock, power and interrupt
(and possibly more) trees that often don't match up.

My point is simply that we should still try to find a helpful tree
representation in these cases, even if it's not perfect. Almost anything
is better than having lots of unrelated devices in a flat directory.

	Arnd