From: Scott Wood <scottwood@freescale.com>
To: Jain Priyanka-B32167 <Priyanka.Jain@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH][v2] powerpc/fsl-booke: Add T1040D4RDB/T1042D4RDB board support
Date: Wed, 29 Jul 2015 17:14:34 -0500 [thread overview]
Message-ID: <1438208074.2993.343.camel@freescale.com> (raw)
In-Reply-To: <BY1PR0301MB08531E965109B9F1EDB7A292EC8C0@BY1PR0301MB0853.namprd03.prod.outlook.com>
On Wed, 2015-07-29 at 04:07 -0500, Jain Priyanka-B32167 wrote:
>
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Friday, July 24, 2015 8:58 PM
> > To: Jain Priyanka-B32167
> > Cc: linuxppc-dev@lists.ozlabs.org
> > Subject: Re: [PATCH][v2] powerpc/fsl-booke: Add T1040D4RDB/T1042D4RDB
> > board support
> >
> > OK, so you're saying the i2c devices are pluggable (and I'm assuming by
> > "PEX
> > slots" you just mean that the physical slot is repurposed, not that the
> > PCI
> > express protocol is involved)? Making a non-runtime-enumerable bus be
> > pluggable seems like a bad idea, but if that's really what has been done,
> > there needs to be a device tree that represents the entire system, not
> > just
> > the motherboard. This could be done either via a dts file that
> > /include/s the
> > motherboard dts, or via firmware dtb edits. The dts for the motherboard
> > should include the mux node with a comment explaining what the situation
> > is.
> >
> [Jain Priyanka-B32167] Is the below comment looks OK?
> "Output I2C data, clock lines (SDO/SC0,SD1/SC1 , SD2/SC2, SD3/SC3) are
> going mini PCI connector slot1, mini PCI connector slot2, HDMI connector,
> PEX slot respectively
> The sub-nodes will depend upon the device that will be connected on these
> slots"
How about:
"Child nodes depend on which i2c devices are connected via the mini PCI
connector slot1, the mini PCI connector slot2, the HDMI connector, and the
PEX slot. Systems with such devices attached should provide a wrapper .dts
file that includes this one, and adds those nodes."
-Scott
next prev parent reply other threads:[~2015-07-29 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 9:30 [PATCH][v2] powerpc/fsl-booke: Add T1040D4RDB/T1042D4RDB board support Priyanka Jain
2015-07-15 17:47 ` Scott Wood
2015-07-16 9:34 ` Priyanka Jain
2015-07-16 19:35 ` Scott Wood
2015-07-17 6:17 ` Priyanka Jain
2015-07-17 17:07 ` Scott Wood
2015-07-22 10:49 ` Priyanka Jain
2015-07-24 15:28 ` Scott Wood
2015-07-29 9:07 ` Priyanka Jain
2015-07-29 22:14 ` Scott Wood [this message]
2015-07-30 4:55 ` Priyanka Jain
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=1438208074.2993.343.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Priyanka.Jain@freescale.com \
--cc=linuxppc-dev@lists.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).