From: Jeremy Kerr <jk@ozlabs.org>
To: Rob Herring <robh@kernel.org>, christopher.lee.bostic@gmail.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
benh@kernel.crashing.org, geert+renesas@glider.be,
andrew@aj.id.au, gregkh@linuxfoundation.org,
mturquette@baylibre.com, linux@armlinux.org.uk,
Chris Bostic <cbostic@us.ibm.com>,
linux-kernel@vger.kernel.org, joel@jms.id.au,
alistair@popple.id.au, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 15/18] drivers/fsi: Add documentation for GPIO based FSI master
Date: Thu, 19 Jan 2017 10:11:16 +0800 [thread overview]
Message-ID: <f0933f56-6a23-9c53-6e10-0e1ca18082e2@ozlabs.org> (raw)
In-Reply-To: <20170118215755.xoamoc2rrzhy4kyz@rob-hp-laptop>
Hi Chris,
>From this:
>> +
>> +The standard FSI master node
>> +----------------------------
>> +This node describes a FSI master implmemented fully in hardware
>> +with dedicated input/output pins required for its function (i.e.
>> +not using generic GPIO pins).
>> +Required property:
>> + compatible = "ibm,fsi-master"
and this:
>> +Example:
>> +
>> +fsi-master {
>> + compatible = "ibm,fsi-master-gpio", "ibm,fsi-master";
>
> From the description, these should be mutually exclusive.
I agree with Rob here. The intention is for "ibm,fsi-master" to be an
abstract master -- simply indicating that this node describes a master,
with no specific implementation, and "ibm,fsi-master-gpio" to be a
GPIO-based implementation. A hardware-based FSI master would have a
different compatible value, based on the hardware.
We should remove references to implementations in the "The standard FSI
master node" section, because this is independent of implementation.
>> + clk-gpios = <&gpio 0>, <&gpio 6>;
>> + data-gpios = <&gpio 1>, <&gpio 7>;
>> + enable-gpios = <&gpio 2>, <&gpio 8>;
>> + trans-gpios = <&gpio 3>, <&gpio 9>;
>> + mux-gpios = <&gpio 4>, <&gpio 10>;
Do we support multiple-link masters? This example implies a 2-link
master.
Cheers,
Jeremy
next prev parent reply other threads:[~2017-01-19 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 22:35 [PATCH v2 15/18] drivers/fsi: Add documentation for GPIO based FSI master christopher.lee.bostic
2017-01-18 21:57 ` Rob Herring
2017-01-19 2:11 ` Jeremy Kerr [this message]
[not found] ` <f0933f56-6a23-9c53-6e10-0e1ca18082e2-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
2017-02-01 17:09 ` Christopher Bostic
2017-02-01 17:17 ` Christopher Bostic
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=f0933f56-6a23-9c53-6e10-0e1ca18082e2@ozlabs.org \
--to=jk@ozlabs.org \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=cbostic@us.ibm.com \
--cc=christopher.lee.bostic@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.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).