From: "Mark A. Greer" <mgreer@mvista.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] mpc5200 device tree bindings refinement
Date: Fri, 9 Feb 2007 10:50:29 -0700 [thread overview]
Message-ID: <20070209175029.GB23362@mag.az.mvista.com> (raw)
In-Reply-To: <20070209173149.GA23362@mag.az.mvista.com>
On Fri, Feb 09, 2007 at 10:31:49AM -0700, Mark A. Greer wrote:
> On Fri, Feb 09, 2007 at 12:30:09AM -0700, Grant Likely wrote:
>
> Hi Grant,
>
> > Much needed refinement of mpc5200 device tree binding specifications.
> >
> > Short list:
>
> <snip>
>
> > - Specify reqiured 'cell-index' property to identify between multiple SOC
> > devices of the same type. (Useful for arbitrating shared register access)
>
> <snip>
>
> > +Important child node properties
> > +name type description
> > +---- ---- -----------
> > +cell-index int When multiple devices are present, is the
> > + index of the device in the hardware (ie. There
> > + are 6 PSC on the 5200 numbered PSC1 to PSC6)
> > + PSC1 has 'cell-index = <0>'
> > + PSC4 has 'cell-index = <3>'
> > +
>
> Dale Farnsworth and I have the exact same problem with the Marvell
> bridges (e.g., 2 MPSC ctlrs use different bits in the same reg).
Hrm, as I reread this, I may have misunderstood the purpose of cell-index. :(
next prev parent reply other threads:[~2007-02-09 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 7:30 [RFC] mpc5200 device tree bindings refinement Grant Likely
2007-02-09 17:31 ` Mark A. Greer
2007-02-09 17:50 ` Mark A. Greer [this message]
2007-02-09 18:38 ` Grant Likely
[not found] ` <9696D7A991D0824DBA8DFAC74A9C5FA3029428E1@az33exm25.fsl.freescale.net>
[not found] ` <20070212205731.GC2729@mag.az.mvista.com>
2007-02-13 15:37 ` Grant Likely
2007-02-13 21:41 ` Benjamin Herrenschmidt
2007-02-13 22:25 ` Mark A. Greer
2007-02-12 20:34 ` Yoder Stuart-B08248
2007-02-12 20:44 ` Grant Likely
2007-02-12 21:07 ` Yoder Stuart-B08248
2007-02-12 21:55 ` Grant Likely
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=20070209175029.GB23362@mag.az.mvista.com \
--to=mgreer@mvista.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.