All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Eddie James <eajames@linux.vnet.ibm.com>
Subject: Re: [PATCH linux dev-4.10] ARM: dts: aspeed: Add devices under FSI CFAM
Date: Tue, 6 Jun 2017 15:18:03 +0930	[thread overview]
Message-ID: <CACPK8Xd+afTCFLNGfwa-=Y7OtgtaXohE4g9uTo3P22Ef_GYoxA@mail.gmail.com> (raw)
In-Reply-To: <6cc0e085-0867-4128-c815-4ff74da1d5d7@ozlabs.org>

On Tue, Jun 6, 2017 at 3:16 PM, Jeremy Kerr <jk@ozlabs.org> wrote:
> Hi Joel,
>
>> This describes the SBE FIFO and OCC device that are attached via the FSI
>> bus.
>>
>> As this layout is common to all existing p9 machines, we add them via a
>> dtsi.  This dtsi requires the 'fsi' label be present.
>
> Sounds like a good idea, no need to replicate the p9 FSI topology in
> each BMC's device tree.
>
>> -     gpio-fsi {
>> +     fsi: gpio-fsi {
>>               compatible = "fsi-master-gpio", "fsi-master";
>> -
>> -             status = "okay";
>> +             #address-cells = <2>;
>> +             #size-cells = <0>;
>
> We might want to keep #address-cells and #size-cells in the common
> include, but then we're splitting properties (ie. compatible) between
> the two files. I'm happy either way though.

Ok. I will leave it as is for now, but as we extend the FSI dtsi we
may want to revisit.

> Acked-by: Jeremy Kerr <jk@ozlabs.org>

Thank you for taking a look!

Cheers,

Joel

      reply	other threads:[~2017-06-06  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  7:43 [PATCH linux dev-4.10] ARM: dts: aspeed: Add devices under FSI CFAM Joel Stanley
2017-06-05  8:25 ` Andrew Jeffery
2017-06-05  8:33 ` Lei YU
2017-06-06  5:46 ` Jeremy Kerr
2017-06-06  5:48   ` Joel Stanley [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='CACPK8Xd+afTCFLNGfwa-=Y7OtgtaXohE4g9uTo3P22Ef_GYoxA@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=eajames@linux.vnet.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=openbmc@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 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.