[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180130055116.17411-2-joel@jms.id.au>
Date: Tue, 30 Jan 2018 16:21:15 +1030
From: Joel Stanley <joel@....id.au>
To: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org
Cc: Christopher Bostic <cbostic@...ux.vnet.ibm.com>,
Jeremy Kerr <jk@...abs.org>,
Eddie James <eajames@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH 1/2] dt-bindings: fsi: Add optional property no-scan-on-init
From: Christopher Bostic <cbostic@...ux.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@...ux.vnet.ibm.com>
Acked-by: Jeremy Kerr <jk@...abs.org>
Signed-off-by: Joel Stanley <joel@....id.au>
---
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 4eaf488d4015..ab516c673a4b 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
----------
--
2.15.1
Powered by blists - more mailing lists