-----Original Message-----
From: Singh Sandeep-B37400
Sent: Wednesday, January 02, 2013 6:55 PM
To: devicetree-discuss@lists.ozlabs.org; linuxppc-dev@ozlabs.org
Cc: Singh Sandeep-B37400; Aggrwal Poonam-B10812
Subject: [PATCH] Added device tree binding for TDM and TDM phy
=20
This controller is available on many Freescale SOCs like MPC8315, P1020,
P1010 and P1022
=20
Signed-off-by: Sandeep Singh <redacted>
Signed-off-by: Poonam Aggrwal <redacted>
---
 .../devicetree/bindings/powerpc/fsl/fsl-tdm.txt    |   63
++++++++++++++++++++
 .../devicetree/bindings/powerpc/fsl/tdm-phy.txt    |   38 ++++++++++++
 2 files changed, 101 insertions(+), 0 deletions(-)  create mode 100644
Documentation/devicetree/bindings/powerpc/fsl/fsl-tdm.txt
 create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/tdm-
phy.txt
=20

diff --git a/Documentation/devicetree/bindings/powerpc/fsl/fsl-tdm.txt

b/Documentation/devicetree/bindings/powerpc/fsl/fsl-tdm.txt
new file mode 100644
index 0000000..ceb2ef1

--- /dev/null
+++ b/Documentation/devicetree/bindings/powerpc/fsl/fsl-tdm.txt

@@ -0,0 +1,63 @@
+TDM Device Tree Binding
+
+NOTE: The bindings described in this document are preliminary and
+subject to change.
+
+TDM (Time Division Multiplexing)
+
+Description:
+
+The TDM is full duplex serial port designed to allow various devices
+including digital signal processors (DSPs) to communicate with a
+variety of serial devices including industry standard framers, codecs,

other DSPs and microprocessors.
+
+The below properties describe the device tree bindings for Freescale
+TDM controller. This TDM controller is available on various Freescale
+Processors like MPC8315, P1020, P1022 and P1010.
+
+Required properties:
+
+- compatible
+    Value type: <string>
+    Definition: Should contain "fsl,tdm1.0".
+
+- reg
+    Definition: A standard property. The first reg specifier describes
the TDM
+    registers, and the second describes the TDM DMAC registers.
+
+- tdm_tx_clk
+    Value type: <u32 or u64>
+    Definition: This specifies the value of transmit clock. It should
not
+    exceed 50Mhz.
+
+- tdm_rx_clk
+    Value type: <u32 or u64>
+    Definition: This specifies the value of receive clock. Its value
could be
+    zero, in which case tdm will operate in shared mode. Its value
should not
+    exceed 50Mhz.
+
+- interrupts
+    Definition: Two interrupt specifiers. The first is TDM error, and
the
+    second is TDM DMAC.
+
+- phy-handle
+    Value type: <phandle>
+    Definition: Phandle of the line controller node or framer node eg.
SLIC,
+    E1/T1 etc. (Refer
+Documentation/devicetree/bindings/powerpc/fsl/tdm-phy.txt)
+
+- fsl,max-time-slots
+    Value type: <u32>
+    Definition: Maximum number of 8-bit time slots in one TDM frame.
This is
+    the maximum number which TDM hardware supports.
+
+Example:
+
+	tdm@16000 {
+		compatible =3D "fsl,tdm1.0";
+		reg =3D <0x16000 0x200 0x2c000 0x2000>;
+		tdm_tx_clk =3D <2048000>;
+		tdm_rx_clk =3D <0>;
+		interrupts =3D <16 8 62 8>;
+		phy-handle =3D <&tdm-phy>;
+		fsl,max-time-slots =3D <128>;
+	};

diff --git a/Documentation/devicetree/bindings/powerpc/fsl/tdm-phy.txt

b/Documentation/devicetree/bindings/powerpc/fsl/tdm-phy.txt
new file mode 100644
index 0000000..2563934

--- /dev/null
+++ b/Documentation/devicetree/bindings/powerpc/fsl/tdm-phy.txt

@@ -0,0 +1,38 @@
+TDM PHY Device Tree Binding
+
+NOTE: The bindings described in this document are preliminary and
+subject to change.
+
+Description:
+TDM PHY is the terminal interface of TDM subsystem. It is typically a
+line control device like E1/T1 framer or SLIC. A TDM device can have
+multiple TDM PHYs.
+
+Required properties:
+
+- compatible
+    Value type: <string>
+    Definition: Should contain generic compatibility like "tdm-phy-slic"

or
+    "tdm-phy-e1" or "tdm-phy-t1".
+
+- max-num-ports
+    Value type: <u32>
+    Definition: Defines the maximum number of ports supported by the
SLIC
+    device. Only required if the device is SLIC. For E1/T1 devices the
number
+    of ports are predefined i.e. (24 in case of T1 and 32 in case of
E1).
+
+Apart from the above, there may be other properties required because of
+the bus/interface this device is connected on. It could be SPI/local
bus, etc.
+
+Example:
+
+	tdm-phy@0 {
+		compatible =3D "zarlink,le88266","tdm-phy-slic";
+		reg =3D <0>;
+		max-num-ports =3D <4>;
+		spi-max-frequency =3D <8000000>;
+	};
+
+In the above example properties "reg" and "spi-max-frequency" are SPI
+specific as the SLIC device is connected on SPI interface. These
+properties might vary depending on the specific interface the device is
using.
--
1.7.6.GIT