All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
	galak@kernel.crashing.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 2/3] mpc82xx: Embedded Planet EP8248E support
Date: Tue, 18 Dec 2007 10:15:18 -0600	[thread overview]
Message-ID: <4767F216.3060408@freescale.com> (raw)
In-Reply-To: <20071218005348.GC9489@localhost.localdomain>

David Gibson wrote:
> I mean, obviously the MDIO bus is accessed via some of the
> board-control registers.  What I'm questioning is whether it makes
> sense to have a distinct node to represent the mdio bus, or whether
> the phys should just hang straight of the bcsr node.

Ah, I see.  I think it does make sense, because it's a bus; if there 
were another bus-like thing on the bcsr, there'd be conflicts over what 
the children mean.

>>>> +	soc@f0000000 {
>>>> +		#address-cells = <1>;
>>>> +		#size-cells = <1>;
>>>> +		device_type = "soc";
>>> Ditch the device_type.
>> No, it's used by the bootwrapper.  I'll get rid of it if you want to 
>> write a find_node_by_compatible() function. :-)
> 
> Well, now that libfdt is merged, there is one :-p.

OK, it just needs exporting via ops.  I'll put it on my to-do list, but 
I don't think it should hold up board support patches.

-Scott

      reply	other threads:[~2007-12-18 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 22:54 [PATCH v2 2/3] mpc82xx: Embedded Planet EP8248E support Scott Wood
2007-12-17  3:59 ` David Gibson
2007-12-17 15:18   ` Scott Wood
2007-12-18  0:53     ` David Gibson
2007-12-18 16:15       ` Scott Wood [this message]

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=4767F216.3060408@freescale.com \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --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.