linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add of_platform_device_scan().
Date: Wed, 04 Oct 2006 11:32:20 -0500	[thread overview]
Message-ID: <4523E214.5060404@freescale.com> (raw)
In-Reply-To: <200610040118.09416.arnd@arndb.de>

Arnd Bergmann wrote:
> I think it would be much more helpful to have working probing of all
> SOC buses during bootup.

I agree; I avoided doing that for now because I was uneasy about 
duplicating device nodes for SOC devices covered under the non-OF 
platform bus via code in sysdev/fsl_soc.c.  It probably won't cause any 
real problems unless a single device matches drivers on both buses (in 
which case the of_device driver would probably be calling 
of_platform_device_scan() anyway), but still...

What I'd really like (long-term, of course) is if platform_device and 
of_device were merged, with device tree support (or at least a means of 
passing on properties that *could* come from a device tree without 
special glue code that knows about each property) in arch-neutral code; 
the mechanism for discovering devices ideally shouldn't depend on the 
CPU's instruction set.

> +	for (child = NULL; (child = of_get_next_child(root, child)); ) {
> +		if (strcmp(child->type, "spider") == 0) {
> +			ret = of_soc_device_create(child, NULL);
> +			if (ret)
> +				goto out3;
> +		}
> +	}

Why only spider?

-Scott

  reply	other threads:[~2006-10-04 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 22:56 [PATCH] Add of_platform_device_scan() Scott Wood
2006-10-03 23:18 ` Arnd Bergmann
2006-10-04 16:32   ` Scott Wood [this message]
2006-10-04 16:37     ` Arnd Bergmann
2006-10-04 19:33       ` Scott Wood

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=4523E214.5060404@freescale.com \
    --to=scottwood@freescale.com \
    --cc=arnd@arndb.de \
    --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 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).