From: Christopher Bostic <cbostic@linux.vnet.ibm.com>
To: joel@jms.id.au, jk@ozlabs.org
Cc: Christopher Bostic <cbostic@linux.vnet.ibm.com>,
openbmc@lists.ozlabs.org
Subject: [PATCH linux dev-4.10 v2 1/3] dt-bindings: fsi: Add optional property no-scan-on-init
Date: Thu, 3 Aug 2017 22:26:20 -0500 [thread overview]
Message-ID: <20170804032622.88674-2-cbostic@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170804032622.88674-1-cbostic@linux.vnet.ibm.com>
Add an optional FSI master property 'no-scan-on-init. This
can be specified to indicate that a master should not be
automatically scanned at init time. This is required in cases
where a scan could interfere with another FSI master on the same
bus.
Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>
---
Documentation/devicetree/bindings/fsi/fsi.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/fsi/fsi.txt b/Documentation/devicetree/bindings/fsi/fsi.txt
index 4eaf488..ab516c6 100644
--- a/Documentation/devicetree/bindings/fsi/fsi.txt
+++ b/Documentation/devicetree/bindings/fsi/fsi.txt
@@ -56,6 +56,13 @@ addresses (link index and slave ID), and no size:
#address-cells = <2>;
#size-cells = <0>;
+An optional boolean property can be added to indicate that a particular master
+should not scan for connected devices at initialization time. This is
+necessary in cases where a scan could cause arbitration issues with other
+masters that may be present on the bus.
+
+ no-scan-on-init;
+
FSI slaves
----------
--
1.8.2.2
next prev parent reply other threads:[~2017-08-04 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 3:26 [PATCH linux dev-4.10 v2 0/3] Add FSI master scan conditional Christopher Bostic
2017-08-04 3:26 ` Christopher Bostic [this message]
2017-08-04 3:26 ` [PATCH linux dev-4.10 v2 2/3] ARM: dts: fsi: Add optional master property no-scan-on-init Christopher Bostic
2017-08-04 3:26 ` [PATCH linux dev-4.10 v2 3/3] fsi: core: Add check for " Christopher Bostic
2017-08-04 3:33 ` Jeremy Kerr
2017-08-08 13:02 ` Joel Stanley
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=20170804032622.88674-2-cbostic@linux.vnet.ibm.com \
--to=cbostic@linux.vnet.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--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.