All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Christian Krafft <krafft@de.ibm.com>
Subject: Re: [patch] powerpc: add scanning of ebc bus to of_platform
Date: Sat, 9 Dec 2006 12:36:56 +0100	[thread overview]
Message-ID: <200612091236.57252.arnd@arndb.de> (raw)
In-Reply-To: <F6853CAA-5CBD-4BA8-A330-55D66AB3E853@kernel.crashing.org>

On Saturday 09 December 2006 11:04, Segher Boessenkool wrote:
> 
> > I'd like other people opinions here... But I'm tempted to remove the
> > "default" list of bus types here and have it always be passed by the
> > platform... just in case.

I think for the flat device tree, we often have only type=soc,
or compatible=soc anyway, and there is a limited number of
internal bus types we want to probe on top of that for real
OF implementations.

> That's probably best -- no sense in registering devices
> on buses that the platform doesn't know how to drive!

But the platform doesn't need how to drive them, the device driver
needs to. All the platform needs to know is the fact that it can
deal with SOC devices that are automatically probed.

I'd much prefer to have the list in the same file that drives the
devices in the first place. It's probably also good to register
them as MODULE_DEVICE_TABLE(), for documentation purposes, even
if the driver can't be built as a module yet.

	Arnd <><

  reply	other threads:[~2006-12-09 11:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 10:41 [patch] powerpc: add scanning of ebc bus to of_platform Christian Krafft
2006-12-08 22:53 ` Benjamin Herrenschmidt
2006-12-09 10:04   ` Segher Boessenkool
2006-12-09 11:36     ` Arnd Bergmann [this message]
2006-12-10 12:17       ` Segher Boessenkool
2006-12-11  2:25       ` Paul Mackerras
2006-12-11  6:56         ` Benjamin Herrenschmidt
2006-12-11 10:01           ` Arnd Bergmann

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=200612091236.57252.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=krafft@de.ibm.com \
    --cc=linuxppc-dev@ozlabs.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 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.