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: Fri, 17 Jul 2015 12:07:01 -0500 [thread overview]
Message-ID: <1437152821.2993.191.camel@freescale.com> (raw)
In-Reply-To: <BY1PR0301MB08536BC13A64047CB7062442EC980@BY1PR0301MB0853.namprd03.prod.outlook.com>
On Fri, 2015-07-17 at 01:17 -0500, Jain Priyanka-B32167 wrote:
>
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Friday, July 17, 2015 1:06 AM
> > To: Jain Priyanka-B32167
> > Cc: linuxppc-dev@lists.ozlabs.org
> > Subject: Re: [PATCH][v2] powerpc/fsl-booke: Add T1040D4RDB/T1042D4RDB
> > board support
> >
> > > > + i2c@118100{
> > > > + mux@77{
> > > > + compatible = "nxp,pca9546";
> > > > + reg = <0x77>;
> > > > + #address-cells = <1>;
> > > > + #size-cells = <0>;
> > > > + };
> > > > + };
> > >
> > > A mux with no nodes under it (and yet it has #address-cells/#size-
> > > cells)?
> > > What is it multiplexing?
> > > [Priyanka]: PCA9546 is i2c mux device , to which other i2c devices
> > > (up-to 8
> > > ) can be further connected on output channels On T104xD4RDB, channel
> > > 0, 1, 3 line are connected to PEX device, Channel 2 to hdmi interface
> > > (initialization is done in u-boot only), other channels are grounded.
> > > So, as such Linux is not using the second level I2C devices connected
> > > on this MUX device. So, I have not shown next level hierarchy.
> > > Should I replace 'mux' with some other name? . Please suggest.
> >
> > The device tree describes the hardware, not just what Linux uses... but
> > what
> > I don't understand is why you describe the mux at all if you're not going
> > to
> > describe what goes underneath it.
> >
> [Jain Priyanka-B32167] : Is below looks OK?
> i2c@118100{
> + i2c@77{
> + compatible = "nxp,pca9546";
> + reg = <0x77>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + };
> + };
Where in my above comment did it appear that I was complaining about the node
name?
-Scott
next prev parent reply other threads:[~2015-07-17 17:07 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 [this message]
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
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=1437152821.2993.191.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).