devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
To: Eddie James
	<eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	openbmc-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH RFC] Documentation/devicetree: Add specification for FSI busses
Date: Fri, 5 May 2017 09:35:48 +0800	[thread overview]
Message-ID: <dff34fc5-bd04-4053-af4e-da12d3a824ef@ozlabs.org> (raw)
In-Reply-To: <eb310c6a-0b41-aecd-2ae5-025a8f64b152-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

Hi Eddie,

> I have no problem with this as an example, but it isn't exactly how the
> tree will look under the p8/p9 fsi-attached i2c master. We will instead
> need a list of ports on the master. Then you could put actual devices
> (eeproms, etc) under the ports if desired.

Yes, this was intended as a fairly simple example. That's a good point
though, and I'll change the compatible string there so that I'm not
implying that it's representing the actual FSI I2c device that we're
working on.

Thanks for the review.

Cheers,


Jeremy
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-05-05  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  5:55 [PATCH RFC] Documentation/devicetree: Add specification for FSI busses Jeremy Kerr
     [not found] ` <1493704508-27119-1-git-send-email-jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
2017-05-02  6:19   ` Joel Stanley
     [not found]     ` <CACPK8Xf2regdT4Y-TW4nOc1qYwDcH=zYPRqdjTqL9yvZH49bRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-02  6:25       ` Jeremy Kerr
2017-05-03  2:36   ` Brad Bishop
2017-05-04 21:02   ` Eddie James
     [not found]     ` <eb310c6a-0b41-aecd-2ae5-025a8f64b152-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-05  1:35       ` Jeremy Kerr [this message]
2017-05-08 14:42   ` Rob Herring
2017-05-09  1:02     ` Jeremy Kerr

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=dff34fc5-bd04-4053-af4e-da12d3a824ef@ozlabs.org \
    --to=jk-mnsaurcq41sdnm+yrofe0a@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=openbmc-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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).