Signed-off-by: Josh Cartwright <joshc@xxxxxxxxxxxxxx>
---
I'm introducing this as an RFC, because there are set of assumptions
made in this binding spec, that currently hold true for the supported
controller/addressing scheme for the Snapdragon 800 series, but don't
necessarily hold true for SPMI in general.
1. No use of Group Slave Identifiers (GSIDs)
(SPMI allows for a slave to belong to zero or more groups specified
by GSID, however this feature isn't currently implemented)
2. No specification of Master Identifier (MID)
(A "system integrator" allocates to each master a 2-bit MID, this
currently isn't being specified, as it isn't needed by software for
the PMIC Arb; not sure if this is of use to other SPMI controllers)
3. Single SPMI master per controller
Effectively, only a subset of possible SPMI configurations are specified
in this document.
So, if it's considered necessary to provide a generic SPMI binding
specification, is it acceptable to only define a subset at this time,
expanding only when necessary, or shall I expand the definition to at
least address 1 & 2, even though they are of no use in the current
implementation?
Documentation/devicetree/bindings/spmi/spmi.txt | 36 +++++++++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spmi/spmi.txt
diff --git a/Documentation/devicetree/bindings/spmi/spmi.txt b/Documentation/devicetree/bindings/spmi/spmi.txt
new file mode 100644
index 0000000..a01b064
--- /dev/null
+++ b/Documentation/devicetree/bindings/spmi/spmi.txt
@@ -0,0 +1,36 @@
+System Power Management Interface (SPMI) Controller
+
+This document defines a generic set of bindings for use by SPMI controllers. A
+controller is modelled in device tree as a node with zero or more child nodes,
+each representing a unique slave on the bus.
+
+Required properties:
+- #address-cells : must be set to 1
+- #size-cells : must be set to 0
+
+Child nodes:
+
+An SPMI controller node can contain zero or more children. Each child must
+have a reg property defining its 4-bit Unique Slave Identifier (USID) on the
+SPMI bus. This is the ID that has been "statically assigned by the system
+integrator", as per the SPMI spec.
+
+Each child node represents a slave device on the bus.
+
+ controller@.. {
+ compatible = "...";
+ reg = <...>;
+
+ #address-cells = <1>;
+ #size-cells <0>;
+
+ child@0 {
+ compatible = "...";
+ reg = <0>;
+ };
+
+ child@7 {
+ compatible = "...";
+ reg = <7>;
+ };
+ };
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
